hello guys,
I've already read the posts concerning this problem and none of them solve my problem. I've just installed Mandrake 10.1 with an intel board D945GNT. The board has an integrated card I planned to use but I got this error "Destination host unreachable". The driver supposed to work with that card didn't work (the driver e100 from intel, which was included with my distro). So I installed another card than mandrake recognized as Davicom Ethernet100/10 MBit. Everything seems ok at the driver, but I still get the same error.
I give the output of some commands I performed, in the order I executed them:
I read it could be the firewall
Code:
[root@cusipsrv root]# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
but it seems ok to me, here is the ifconfig output
Code:
[root@cusipsrv root]# ifconfig
eth0 Lien encap:Ethernet HWaddr 00:80:AD:86:69:F0
inet adr:192.168.100.10 Bcast:192.168.100.255 Masque: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:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interruption:11 Adresse de base:0x1000
lo Lien encap:Boucle locale
inet adr:127.0.0.1 Masque:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1030 errors:0 dropped:0 overruns:0 frame:0
TX packets:1030 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:96238 (93.9 Kb) TX bytes:96238 (93.9 Kb)
then i do some pings
(to my IP, everything ok)
Code:
[root@cusipsrv root]# ping 192.168.100.10
PING 192.168.100.10 (192.168.100.10) 56(84) bytes of data.
64 bytes from 192.168.100.10: icmp_seq=1 ttl=64 time=0.022 ms
64 bytes from 192.168.100.10: icmp_seq=2 ttl=64 time=0.018 ms
64 bytes from 192.168.100.10: icmp_seq=3 ttl=64 time=0.022 ms
64 bytes from 192.168.100.10: icmp_seq=4 ttl=64 time=0.022 ms
--- 192.168.100.10 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2997ms
rtt min/avg/max/mdev = 0.018/0.021/0.022/0.002 ms
(then to the router for example)
Code:
[root@cusipsrv root]# ping 192.168.100.1
PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data.
From 192.168.100.10 icmp_seq=1 Destination Host Unreachable
From 192.168.100.10 icmp_seq=2 Destination Host Unreachable
From 192.168.100.10 icmp_seq=3 Destination Host Unreachable
From 192.168.100.10 icmp_seq=6 Destination Host Unreachable
--- 192.168.100.1 ping statistics ---
8 packets transmitted, 0 received, +4 errors, 100% packet loss, time 7028ms
, pipe 3
another ifconfig
Code:
[root@cusipsrv root]# ifconfig
eth0 Lien encap:Ethernet HWaddr 00:80:AD:86:69:F0
inet adr:192.168.100.10 Bcast:192.168.100.255 Masque: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:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interruption:11 Adresse de base:0x1000
lo Lien encap:Boucle locale
inet adr:127.0.0.1 Masque:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1131 errors:0 dropped:0 overruns:0 frame:0
TX packets:1131 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:106064 (103.5 Kb) TX bytes:106064 (103.5 Kb)
As someone already showed me, there are no packets transmitted by the eth0 interface... weird, isn't it?
now the route command
Code:
[root@cusipsrv root]# route -n
Table de routage IP du noyau
Destination Passerelle Genmask Indic Metric Ref Use Iface
192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 192.168.100.1 0.0.0.0 UG 0 0 0 eth0
also performed this command grep -e eth0 /var/log/syslog
Code:
Mar 10 11:49:35 cusipsrv kernel: eth0: Davicom DM9102 at pci06:03.0, 00:80:ad:86:69:f0, irq 11.
Mar 10 11:49:34 cusipsrv network: Activation de l'interface eth0 : succeeded
Mar 10 11:49:38 cusipsrv kernel: eth0: Tx timeout - resetting
Mar 10 11:49:42 cusipsrv kernel: eth0: Tx timeout - resetting
Mar 10 11:49:46 cusipsrv kernel: eth0: Tx timeout - resetting
Mar 10 11:49:50 cusipsrv kernel: eth0: Tx timeout - resetting
Mar 10 11:49:54 cusipsrv kernel: eth0: Tx timeout - resetting
Mar 10 11:49:58 cusipsrv kernel: eth0: Tx timeout - resetting
Mar 10 11:50:02 cusipsrv kernel: eth0: Tx timeout - resetting
Mar 10 11:50:26 cusipsrv kernel: eth0: Tx timeout - resetting
Mar 10 11:50:30 cusipsrv kernel: eth0: Tx timeout - resetting
Mar 10 11:50:34 cusipsrv kernel: eth0: Tx timeout - resetting
Mar 10 11:51:30 cusipsrv kernel: eth0: Tx timeout - resetting
Mar 10 11:51:34 cusipsrv kernel: eth0: Tx timeout - resetting
Mar 10 11:51:38 cusipsrv kernel: eth0: Tx timeout - resetting
Mar 10 11:51:42 cusipsrv kernel: eth0: Tx timeout - resetting
Mar 10 11:51:46 cusipsrv kernel: eth0: Tx timeout - resetting
Mar 10 11:51:50 cusipsrv kernel: eth0: Tx timeout - resetting
Mar 10 11:52:14 cusipsrv kernel: eth0: Tx timeout - resetting
I taugh it could also be something with the card resetting every moment, but... if it's something with the card, why did I have the same problem with the other card? Any idea?
I hope you can help, thanks in advance for your time,
mundacho