Networking with Gamecube broadband adapter...

[Ichinisan]

I've been using the Phantasy Star Online backdoor to load homebrew code, including the hacked N64 emulator from the Zelda Bonus Disc. It's a lot of fun and I plan to do this a lot, using my Gamecube for several N64 games. I have a dedicated NIC for my Gamecube, and using the integrated LAN (MSI K7N2G-LISR, nforce2) for my Internet connection. My Internet connection is configured for DHCP, and my secondary NIC has a static IP address specified.

The cards are not bridged, so there should be two physically seperate networks. Is there something wrong with Windows that causes the transfer application to fail when the Internet is connected to the other NIC?

I have tried swapping the NIC configurations, just in case the transfer application was defaulting to the wrong connection. Either way, the application still fails when the Internet connection is enabled from the other NIC. The 'cube connection is sensitive to latency, which is why I chose to use a dedicated NIC and crossover cable instead of plugging it into my router. Why would Windows allow one network connection to affect another when they are not bridged?

Windows IP Configuration


Ethernet adapter NVIDIA:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

Ethernet adapter 3com:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

 

[Ichinisan]

bump

 

[Matthias99]

Sorry, I'm a little confused on the details of your setup and problem.

It sounds like you've got the GCN plugged into the 3Com NIC, and then your computer connected to the router through the onboard LAN port.

Is the problem that your computer can't talk to the GCN while the internet is plugged in? It sounds like this could be a routing issue (ie, your application is trying to send packets to your GCN through the internet instead of through the other NIC). It might be doing that because they're both on the same subnet -- try setting the NIC to, say, 192.168.2.100 as its static address. Otherwise, I'm not sure how to fix that -- gory Windows networking internals are not my strong suit.

Also, assuming your router is any good, you should get very little latency through it (1-2ms, tops) as long as you aren't pushing a ton of traffic out to the internet. So if that works, it may be a better choice.

 

[InlineFive]

Originally posted by: Matthias99
Sorry, I'm a little confused on the details of your setup and problem.

It sounds like you've got the GCN plugged into the 3Com NIC, and then your computer connected to the router through the onboard LAN port.

Is the problem that your computer can't talk to the GCN while the internet is plugged in? It sounds like this could be a routing issue (ie, your application is trying to send packets to your GCN through the internet instead of through the other NIC). It might be doing that because they're both on the same subnet -- try setting the NIC to, say, 192.168.2.100 as its static address. Otherwise, I'm not sure how to fix that -- gory Windows networking internals are not my strong suit.

Also, assuming your router is any good, you should get very little latency through it (1-2ms, tops) as long as you aren't pushing a ton of traffic out to the internet. So if that works, it may be a better choice.

Besides, plugging it into your computer won't help any because the computer would have router latency also. I would plug your GC into the router unless it needs to be plugged into the computer for uploading code.

 

[Confused]

It is due to the default gateway that is set on the "internet" connection. This will send all data by default out of that port to that address.


Confused

 

[CZroe]

I told him it was the subnet from day one. He didn't understand that a different third octet is required when using a subnet mask of 255.255.255.0 for both and not a different subnet mask for each card

We changed the router to provide 192.168.0.XXX addresses instead and it works flawlessly.