Tom Hosiawa ([EMAIL PROTECTED]) scribbled: > > What is the output of ifconfig? Are you running both nic's > > simultaneously? > > > > It sounds like TCP is working (guarantees trans/rcv), while UDP/ICMP is > > not (no guarantee). Although I forget if mail is UDP or TCP. > > > > When I run multiple nic's at work, I have (luckily) always had to keep > > them on separate subnets. Makes this stuff a lot easier. If nothing > > turns up I would suggest getting one working with the other totally not > > present. Then get the other working on a different subnet. eg: > > > > eth0 192.168.1.x netmask 255.255.255.0 # 10/100 > > eth1 192.168.2.y netmask 255.255.255.0 # wireless > > > > HTH, > > > > Cooper. > > Yeah I'm running both nic's simultaneously, but use the wireless > connection most of the time. > > ifconfig results: > eth0 Link encap:Ethernet HWaddr 00:08:0D:8A:6A:0A > inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0 > UP BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:174 errors:0 dropped:0 overruns:0 frame:0 > TX packets:281 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:20182 (19.7 Kb) TX bytes:39817 (38.8 Kb) > Interrupt:11 Base address:0xdf40 Memory:fceff000-fceff038 > > eth1 Link encap:Ethernet HWaddr 00:06:25:2B:1A:54 > inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:6543 errors:2348 dropped:2348 overruns:0 frame:0 > TX packets:5961 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:3456252 (3.2 Mb) TX bytes:1049310 (1.0 Mb) > Interrupt:3 Base address:0x100 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:6223 errors:0 dropped:0 overruns:0 frame:0 > TX packets:6223 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:328508 (320.8 Kb) TX bytes:328508 (320.8 Kb)
Okay, I've worked myself through three solutions only to realize I was wrong, hopefully this is the right one. It's been a long day. :) Remove the gateway parameter (gateway="eth1/192.168.1.1) from each of your iface's. Restart both devices, and check 'route -n'. Ensure the default gateway is still the last entry present: 0.0.0.0 192.168.1.1 0.0.0.0 UG 1 0 0 eth1 If not, add it manually with: # route add default gw 192.168.1.1 Hopefully this will work. If not, you will soon become intimate with traceroute, tcpdump, ifconfig, and route. Your other option is to only activate one device at a time on the same subnet from the same machine. If you want to give it try: # ifconfig eth0 down I think the problem lies in having two paths with which to reach the GW. TCP connections catch this error because they have to handshake and guarantee data xmt/rcv. UDP/ICMP are fire and forget. So if those packets hit an error, they're lost. If anyone is sitting out there chuckling, please fill us in. routing tables et al are still a little voodoo magic to me. *8v) Cooper. -- [EMAIL PROTECTED] mailing list
