Newsgroups: comp.os.linux.setup Date: Tue, 26 Nov 2002 23:43:17 -0500
> I was happy, when I succesfully installed the new Elitegroup k7s5a > mainboard on my computer and got no error messages about the NIC. > The other NIC (on board) was also successfully installed and my laptop can > communicate with its linux box. > But when I try to get connection to my ISP > (telnet login.isp.address), I got error message (host unreachable). > > I don't know where to start finding the wrong configuration. > Here are some outputs: > ------------------------------------------------------ > # dmesg |grep "eth0" > divert: allocating divert_blk for eth0 > eth0: Realtek RTL8201 PHY transceiver found at address 1. > eth0: Using transceiver found at address 1 as default > eth0: SiS 900 PCI Fast Ethernet at 0xd400, IRQ 10, 00:07:95:32:2e:41. > eth0: Media Link On 100mbps full-duplex > # dmesg |grep "eth1" > divert: allocating divert_blk for eth1 > eth1: Digital DS21143 Tulip rev 65 at 0xd0908c00, 00:60:F5:A0:14:A1, IRQ 10.
I'm suspicious of this NIC. I've never seen a "divert" message before.
> # route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 > 134.174.63.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo > 0.0.0.0 134.174.63.1 0.0.0.0 UG 0 0 0 eth1
Your default route goes through eth1 to your gateway at 134.174.63.1 Can you ping 134.174.63.1?
> # ifconfig > eth0 Link encap:Ethernet HWaddr 00:07:95:32:2E:41 inet > addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX > bytes:168 (168.0 b) > Interrupt:10 Base address:0xd400
eth0 looks OK, sort of. You've sent 4 packets, and it's not encountered any errors. However, you've not received _any_ packets, which is somewhat suspicious.
> eth1 Link encap:Ethernet HWaddr 00:60:F5:A0:14:A1 > inet addr:134.174.63.134 Bcast:134.174.63.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:114 dropped:0 overruns:0 carrier:114 > collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX > bytes:0 (0.0 b) > Interrupt:10 Base address:0x8c00
eth1 looks to have problems. you've not been able to send or receive _any_ packets. all 114 packets that you've tried to send had carrier errors. It looks like your eth1 isn't properly configured for your lan speed, or some other problem is causing it to lose it's 'carrier'.
> 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:69 errors:0 dropped:0 overruns:0 frame:0 > TX packets:69 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:6852 (6.6 Kb) TX bytes:6852 (6.6 Kb)
As expected, lo is OK.
> # depmod -a (no output) > # lsmod > Module Size Used by Not tainted > videodev 8288 2 (autoclean) [bttv] > i2c-algo-bit 8840 1 (autoclean) [bttv] > i2c-core 19268 0 (autoclean) [tuner bttv i2c-algo-bit] > sr_mod 18168 0 (autoclean) > i810_audio 25224 1 (autoclean) > ac97_codec 13416 0 (autoclean) [i810_audio] > soundcore 6532 2 (autoclean) [i810_audio] > autofs 13348 0 (autoclean) (unused) > tulip 43552 1
OK, so a driver for eth1 is loaded. It might be the wrong driver, though. Have you tried the de4x5 driver? From the driver source, it looks like de4x5.o might be better suited to your eth1 NIC than tulip.o
> sis900 16908 1
The driver for eth0 is loaded. The sis900 driver seems to be the correct one for the RTL8201 NIC.
> iptable_filter 2412 0 (autoclean) (unused) > ip_tables 14936 1 [iptable_filter] > ide-scsi 10512 0 scsi_mod 107240 2 [sr_mod > ide-scsi] > ide-cd 33608 1 cdrom 33696 0 [sr_mod > ide-cd] > ohci1394 20108 0 (unused) > ieee1394 46892 0 [ohci1394] > nls_iso8859-1 3516 4 (autoclean) > nls_cp437 5148 3 (autoclean) > mousedev 5524 1 keybdev 2976 0 (unused) > hid 22244 0 (unused) > input 5920 0 [mousedev keybdev hid] > usb-ohci 21320 0 (unused) > usbcore 77024 1 [hid usb-ohci] > # cat /etc/resolv.conf > search hm.bochum.de > nameserver 134.174.63.2 > nameserver 134.174.32.40 > nameserver 134.174.222.4 > # cat /var/log/messages |grep error (no output) > ------------------------------------------------------ > Again: I have to connect through 'telnet login.isp.address' to get > internet working.
How do you mean "get internet working"? How does telnetting to your isp "get internet working"?
Try a few things:
Lew Pitcher
> >> There is no default route here. Packets destined for network addresses > >> other than the two specified will have no place to go. > > Correction: the default route has been defined, and it sends packets out > via eth1 > >>> 0.0.0.0 134.174.63.1 0.0.0.0 UG 0 0 0 eth1 > ------- ------------ -- ---- > \-default route \- uses gateway IP \-Up/Gateway \-eth1
Yep, absolutely right. I didn't know that IP addr 0.0.0.0 indicated the default route; every version of "route" I've ever used explicitly indicated a "default" entry. Sorry for the misinformation.
Steve Martin