[SOLVED] Ethernet connection problem

Grungi Ankhfire · Post by **Grungi Ankhfire** » Sun Jun 12, 2005 5:45 pm

Hi there,

I've been trying to get some code to run on my ps2 (using ps2link, ps2client and a network adapter). My computer runs Gentoo Linux, and has 2 ethernet cards installed and working (tested them both). One of these is connected to a router, and the other one directly to the ps2's network adapter.

So far, I couldn't even ping the ps2, even if the IP for my ethernet card (the one connected to the ps2 of course) is 192.168.0.1 (wich is the default gateway used by ps2link). But I've managed to get things working by plugging my ps2 in the router directly, and using a modified IPCONFIG.DAT to set the IP of the router. The thing is, the router is in another room, and I can't leave it there everytime I want to send something to it...

So, did I miss something ? Dis I do something wrong ? Hope you guys can help me... :s

(Note : As I am from Belgium, I apologize in advance for any english mistake I could make...)

urchin · Post by **urchin** » Sun Jun 12, 2005 6:07 pm

I have a similar setup, but with a wireless connection to my router and a direct ethernet connection to the PS2. The helpful chaps on IRC helped point me in the right direction and now everything works great.

My wireless connection has IP 192.168.0.100 and the router is 192.168.0.1. My ethernet port is 192.168.1.11 and the ps2 is 192.168.1.10

In IPCONFIG.DAT, I have "192.168.1.10 255.255.255.0 192.168.1.1" - note that despite specifying a gateway IP the lack of router in this direct setup is not a problem! One thing you may need to change is the routing order (otherwise your computer will try to send all your internet traffic to the PS2 :) On the mac this can be done through the networking GUI - you'll need to play around with the "route" command on linux...

Grungi Ankhfire · Post by **Grungi Ankhfire** » Sun Jun 12, 2005 6:51 pm

Ok, just to be sure : do the two connections (to the router and to the ps2) have to be on the same network (for you 192.168.*.*) and use different subnetworks ? Because, to be more specific, my current setup is as follow :

Router IP : 10.0.0.2
Connection to the router via IP 10.0.0.4
Connection to the ps2 : 192.168.0.1 (also tried to change it to 192.168.0.11, but to no avail...)
PS2 IP : 192.168.0.10

So do I have to change the ps2 IP to something more like 10.0.1.* and set up my second ethernet card to use an IP on the same subnetwork or is it completely irrelevant ?

Anyway, thanks already ^^

urchin · Post by **urchin** » Sun Jun 12, 2005 7:09 pm

No, they can be on totally different networks.

The example I gave above was my original setup (I now have the same wireless config, but now my ps2 and laptop ethernet are on 10.0.0.*)

For your setup, I would try the following. Disable or remove the network card used for internet traffic (to eliminate routing problems)

Setup your PC with IP 192.168.0.11, subnet mask 255.255.255.0 and router/gateway 192.168.0.1. In PS2 IPCONFIG.DAT put "192.168.0.10 255.255.255.0 192.168.0.1". Hopefully that should work, it does for me.

Then reintroduce the other network card and resolve any routing problems, if any (all my internet traffic was being routed to PS2 when it was connected until I reordered the routing) I went through all this pain last week, so I can symphathize with you!... :)

Grungi Ankhfire · Post by **Grungi Ankhfire** » Sun Jun 12, 2005 9:32 pm

Hmm... I did try what you suggested, and tested another thing or two.

-I did burn (yet another :p) ps2link iso with "192.168.0.10 255.255.255.0 192.168.0.1", wich is only sligthly different than the default one (wich has 255.0.0.0 for subnet mask);

-Then I turned off my first ethernet card (the router one), and, just to be sure, unplugged the network cable, and set my gateway to 192.168.0.1, and the IP of my other card to 192.168.0.11, with 255.255.255.0 for the mask;

-As I still wasn't able to even ping the ps2's IP (it gives me "Destination Host Unreachable"), I looked at other possibilities : I tried switching the config of my two cards, but it gave me no results.

Anyway, there's something wich I find quite strange : When I plug the cable I use to get to the router to either of my NIC's, the LEDs light up (that's the normal part ;) But with the ps2 cable, nothing. I do that, of course, when the ps2 is already turned on and the ps2link says "ready". And using the same cable, when I plug it directly into the router, the corresponding LED lights almost immediately. So I'm thinking that this could lead to discover where the problem lies, but it still is strange (I'm able to connect to the net no matter wich card I plug the router cable in, so I'm sure the two ethernet cards are in order...).

Any idea ?

urchin · Post by **urchin** » Sun Jun 12, 2005 9:50 pm

Firstly you are right, I can only ping the PS2 when ps2link is showing "ready", as the ps2link network drivers have not been initialised before that.

Are you using a crossover cable between the PC and PS2? (Unless like my mac, your card is autosensing and does the crossover automagically)

And if your cable is ok, a shot in the dark... is the network card set to autonegotiate? I saw this mentioned somewhere else on the forum. I've had cases before where two cards could not negotiate properly - forcing one card to 100Mb/s fixed it.

And by the way, I got through about 10 cdrs last week. The one that finally worked is now stored in a safe place :)

Grungi Ankhfire · Post by **Grungi Ankhfire** » Mon Jun 13, 2005 12:31 am

Ok, my problem is solved thanks to you !

I was using a straight cable, I assumed the one wich came with the network adapter was a crossover one ^^ But anyway, I took a network cable wich was laying around and cut it to rewire it as a crossover one. And it works ! I can now acces the ps2, it works like a charm !!

Thank you very much, urchin, you really helped me !!

And now, on to run homebrew code on my ps2 using my brand new... homebrew cable ^^

urchin · Post by **urchin** » Mon Jun 13, 2005 1:06 am

Cool, glad you got it working!...

Now welcome to the part where you install the devkit, look at the demos and wonder "how the f*ck does this thing actually work then?"... ;)