Destination Host Unreachable

danka · 12-31-2004, 05:40 AM

Hi,

I have faced big trouble setting up my network card, but at least now I can bring up eth0. However, it seems I can't ping any computer on my LAN. I have looked at some similar posts, but I can't get their solutions really solve my problem..

Have a look at the following:

Code:

$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:80:AD:A8:53:CD
          inet addr:192.168.0.180  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::280:adff:fea8:53cd/64 Scope:Link
          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:423 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:11 Base address:0x1000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:416 errors:0 dropped:0 overruns:0 frame:0
          TX packets:416 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:43162 (42.1 Kb)  TX bytes:43162 (42.1 Kb)

The interface is up and the IP address is set correctly. The 'route' command shows the following:

Code:

$ 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
0.0.0.0         192.168.0.1     0.0.0.0         UG    0      0        0 eth0

But when I try to ping my router/gateway, it is for some reason unreachable:

Code:

$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
From 192.168.0.180 icmp_seq=1 Destination Host Unreachable
From 192.168.0.180 icmp_seq=3 Destination Host Unreachable
From 192.168.0.180 icmp_seq=4 Destination Host Unreachable
From 192.168.0.180 icmp_seq=5 Destination Host Unreachable
From 192.168.0.180 icmp_seq=6 Destination Host Unreachable
From 192.168.0.180 icmp_seq=7 Destination Host Unreachable

--- 192.168.0.1 ping statistics ---
9 packets transmitted, 0 received, +6 errors, 100% packet loss, time 7999ms, pipe 4

It should be mentioned that I can ping myself (192.168.0.180) correctly.

Any ideas?

/Daniel

qazzaq · 12-31-2004, 06:46 AM

are you running some sort of firewall (ipfilter) on your box?

danka · 12-31-2004, 06:52 AM

No, no firewall is installed.

qazzaq · 12-31-2004, 06:55 AM

The icmp 'Destination Host Unreachable' reply comes from your local interface, so the icmp echo request never enters your cable. Are you sure your cable is properly connected, and that you are using the right cable?

Darin · 12-31-2004, 09:32 AM

Destination Host Unreachable

In plain English, means that your system found what it thinks is the right network but could not find the other system on that network.

-A subtle slip up could be that the computer you want to reach has a different netmask and/or broadcast address, although the ones you have set, from your ifconfig, are the defaults for that IP range so it's not likely.

-The most common problem here would be no connection between you and the other system, as qazzaq eluded to. Check to make sure all the cables are pluged in and the linklights on the ports are lit up. You could also see if there is a faulty cable by replacing one, sometimes a miswired or iffy cable will give you link lights but won't transmit data.

-It's also possible that a misconfiguration was made. If the other system has that IP address, make sure there is not a router between the two systems (plugging them both into ports on an Internet sharing router does not usually mean that the router is between them unless one is on the input, or "Internet" port)

-If there are other systems on your network, can you ping those? What is at the 192.168.0.1 address i.e. a router or another computer and if there are other systems on your network, can they ping that device?

-What type of network card are you using (if unsure then post the relevant output from, as root, lspci and lsmod)? It's rare, but it can happen that some network cards will load their drivers without obvious errors and still not reach other computers on the network.

-Usually, but not always, a firewall preventing pings will give you a different error such as, "Connection Refused By Host."

louis_m_c · 12-31-2004, 03:27 PM

Be sure these files have the following values or add this to your /etc/rc.local

echo 0 > /proc/sys/net/ipv4/icmp_echo_ignore_all
echo 0 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts

also try adding this route:

route add 255.255.255.255 eth0

danka · 01-01-2005, 04:34 PM

qazzaq:
I think you're absolutely right that the signal never enters the cable, the problem is why. It is connected correctly. The cable and the network card work perfectly under Windows, and previous versions of Linux. My latest working distribution was Fedora Core 1. In both FC2 and FC3, eth0 can not even be activated. Now, I use Mandrake 10.1, and there eth0 can be activated. But, now I have this problem.

Darin:
- The netmask and broadcast addresses are correct.

- Cables are plugged, as described above.

- I am trying to ping a router directly connected to my computer. The router is pingable when booted in Windows, and also from other computers.

- I can't ping anyone (but myself), nor can anyone ping me.

- Below is the listing of lspci and lsmod. Previous distributions have always autodetected the module "tulip", but Mandrake detects "de2104x". It doesn't matter, though. No matter the module the behaviour is the same.

Code:

$ lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 03)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 22)
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 10)
00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 10)
00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 10)
00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30)
00:08.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 0a)
00:08.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 0a)
00:0d.0 Multimedia video controller: Brooktree Corporation Bt848 Video Capture (rev 11)
00:0f.0 Ethernet controller: Digital Equipment Corporation DECchip 21041 [Tulip Pass 3] (rev 11)
00:11.0 VGA compatible controller: 3Dfx Interactive, Inc. Voodoo 3 (rev 01)

$ lsmod
Module                  Size  Used by
de2104x                18208  0
nfsd                  189408  8
exportfs                4736  1 nfsd
lockd                  58344  2 nfsd
sunrpc                127652  2 nfsd,lockd
md5                     3584  1
ipv6                  230916  8
rfcomm                 32348  0
l2cap                  19876  5 rfcomm
bluetooth              39076  4 rfcomm,l2cap
snd-seq-midi            6624  0
snd-emu10k1-synth       6656  0
snd-emux-synth         34976  1 snd-emu10k1-synth
snd-seq-virmidi         5632  1 snd-emux-synth
snd-seq-midi-emul       7200  1 snd-emux-synth
snd-seq-oss            31232  0
snd-seq-midi-event      6080  3 snd-seq-midi,snd-seq-virmidi,snd-seq-oss
snd-seq                47440  8 snd-seq-midi,snd-emux-synth,snd-seq-virmidi,snd-seq-midi-emul,snd-seq-oss,snd-seq-midi-event
snd-pcm-oss            49480  0
snd-mixer-oss          17376  3 snd-pcm-oss
snd-emu10k1            90728  3 snd-emu10k1-synth
snd-rawmidi            19300  3 snd-seq-midi,snd-seq-virmidi,snd-emu10k1
snd-pcm                81800  2 snd-pcm-oss,snd-emu10k1
snd-timer              20356  2 snd-seq,snd-pcm
snd-seq-device          6344  7 snd-seq-midi,snd-emu10k1-synth,snd-emux-synth,snd-seq-oss,snd-seq,snd-emu10k1,snd-rawmidi
snd-ac97-codec         69392  1 snd-emu10k1
snd-page-alloc          7400  2 snd-emu10k1,snd-pcm
snd-util-mem            3232  2 snd-emux-synth,snd-emu10k1
snd-hwdep               6916  2 snd-emux-synth,snd-emu10k1
snd                    45988  13 snd-emux-synth,snd-seq-virmidi,snd-seq-oss,snd-seq,snd-pcm-oss,snd-mixer-oss,snd-emu10k1,snd-rawmidi,snd-pcm,snd-timer,snd-seq-device,snd-ac97-codec,snd-hwdep
lp                      9548  0
parport_pc             30976  1
parport                33896  2 lp,parport_pc
af_packet              16072  0
floppy                 55088  0
nls_cp850               4480  1
vfat                   11168  1
fat                    39776  1 vfat
ide-cd                 37280  0
cdrom                  37724  1 ide-cd
loop                   12520  0
nls_iso8859-1           3680  2
ntfs                  147964  1
supermount             34804  1
via-agp                 7360  1
agpgart                27752  1 via-agp
tuner                  18320  0
tvaudio                20588  0
bttv                  145676  0
video-buf              16868  1 bttv
i2c-algo-bit            8712  1 bttv
v4l2-common             4896  1 bttv
btcx-risc               3816  1 bttv
i2c-core               19060  4 tuner,tvaudio,bttv,i2c-algo-bit
videodev                7168  1 bttv
soundcore               7008  4 snd,bttv
sd_mod                 19232  2
usb-storage            65504  1
scsi_mod              104044  2 sd_mod,usb-storage
usblp                  10592  0
uhci-hcd               28752  0
usbcore               103172  5 usb-storage,usblp,uhci-hcd
ext3                  120680  2
jbd                    49080  1 ext3

luis_m_c:
- Those files do have the specified values.
- Adding that route does unfortunately not help.

Thank you for taking your time. I'm still quite confused. I'm getting to think there is a driver problem. Perhaps I should buy a new network card better supported by Linux (although it has been (still is?) quite well supported). It is quite old, but does work..

louis_m_c · 01-01-2005, 04:48 PM

Can you ping 127.0.0.1 ?

Look on the Mandrake site to be sure the ethernet card you are using is compatible.

If it is, try the wizard to setup your internet once again. The wizard should work great when you have a simple network configuration.
If it is still not working, try another card like a 3com / smc / etc. (anyways they are cheap).

danka · 01-01-2005, 05:29 PM

Yes, I can ping 127.0.0.1

I have used the wizard many times over and over again in different combinations, but nothing really works.

The card has been supported for many, many years before by the Linux community. Why stop now?

But, perhaps you're right. The easiest way to get rid of this trouble might be to buy a new card.