Discussion:
[SLE] Network problem: Destination Host Unreachable under SuSE-8.2
NGUYEN DAI Quy
2003-05-18 20:29:13 UTC
Permalink
Hi SuSEr!

Just installed SuSE 8.2. Yast is great! But I have problem with network.
In fact I install SuSE on my 2nd box (192.168.100.2) in which I have also RH-9 & Conectiva-9. I
have another linux box (192.168.100.1) for FW & router of ADSL line.

Under RH9 & Conectiva-9, I need config default gw is 192.168.100.1 for box 192.168.100.2 and
network works fine. But not under SuSE-8.2. By viewing the kernel module, I see that the same
kernel module was loaded in SuSE and RH9 (8139too, I use NIC Realtek RTL-8139/8139C/8139C+).

When I ping localhost or 127.0.0.1 => OK:
----------------------------------------------------------------------
[SuSE] > ping localhost
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.028 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.024 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.025 ms
64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.025 ms
64 bytes from localhost (127.0.0.1): icmp_seq=5 ttl=64 time=0.024 ms
64 bytes from localhost (127.0.0.1): icmp_seq=6 ttl=64 time=0.024 ms
64 bytes from localhost (127.0.0.1): icmp_seq=7 ttl=64 time=0.026 ms
64 bytes from localhost (127.0.0.1): icmp_seq=8 ttl=64 time=0.026 ms

--- localhost ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 6994ms
rtt min/avg/max/mdev = 0.024/0.025/0.028/0.003 ms

[SuSE] > ping 127.0.0.1
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.028 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.023 ms

--- 127.0.0.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.023/0.025/0.028/0.005 ms
------------------------------------------------------------------

But when I ping to 192.168.100.1 it does not work:
[SuSE] > ping adsl.nguyendai.org

PING adsl.nguyendai.org (192.168.100.1) 56(84) bytes of data.
From suse.nguyendai.org (192.168.100.2): icmp_seq=1 Destination Host Unreachable
From suse.nguyendai.org (192.168.100.2) icmp_seq=1 Destination Host Unreachable
From suse.nguyendai.org (192.168.100.2) icmp_seq=2 Destination Host Unreachable
From suse.nguyendai.org (192.168.100.2) icmp_seq=3 Destination Host Unreachable
From suse.nguyendai.org (192.168.100.2) icmp_seq=4 Destination Host Unreachable
From suse.nguyendai.org (192.168.100.2) icmp_seq=5 Destination Host Unreachable
From suse.nguyendai.org (192.168.100.2) icmp_seq=6 Destination Host Unreachable

--- adsl.nguyendai.org ping statistics ---
9 packets transmitted, 0 received, +7 errors, 100% packet loss, time 8028ms
, pipe 3

------------------------------------------------------------------
Output of ifconfig is:
[SuSE] > /sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 00:08:A1:34:FF:12
inet addr:192.168.100.2 Bcast:192.168.100.255 Mask:255.255.255.0
inet6 addr: fe80::208:a1ff:fe34:ff12/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:41 errors:0 dropped:0 overruns:0 frame:0
TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:2878 (2.8 Kb) TX bytes:2878 (2.8 Kb)
Interrupt:11 Base address:0x7000

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:143 errors:0 dropped:0 overruns:0 frame:0
TX packets:143 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:11076 (10.8 Kb) TX bytes:11076 (10.8 Kb)
-----------------------------------------------------------------------
[SuSE] > /sbin/route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.100.0 192.168.100.1 255.255.255.0 UG 0 0 0 eth0
192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
-----------------------------------------------------------------------
[SuSE] > cat /etc/hosts
127.0.0.1 localhost
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix
ff02::1 ipv6-allnodes
ff02::2 ipv6-allrouters
ff02::3 ipv6-allhosts

192.168.100.1 adsl.nguyendai.org adsl
192.168.100.2 suse.nguyendai.org suse
-----------------------------------------------------------------------
The IPV6 records were added into /etc/hosts by SuSE :)

I tried :
# ifconfig eth0 down
# rmmod 8139too; modprobe 8139too
# ifconfig eth0 192.168.100.2 netmask 255.255.255.0 up
# route add -net 192.168.100.0 netmask 255.255.255.0 eth0
# route add default gw 192.168.100.1 eth0

But the same error when I ping.

The config of RH9 at the same box:
[RH9] # ifconfig
eth0 Link encap:Ethernet HWaddr 00:08:A1:34:FF:12
inet addr:192.168.100.2 Bcast:192.168.100.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:128 errors:0 dropped:0 overruns:0 frame:0
TX packets:122 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:28327 (27.6 Kb) TX bytes:11154 (10.8 Kb)
Interrupt:11 Base address:0xf000

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:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:196 (196.0 b) TX bytes:196 (196.0 b)

[RH9] # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.100.1 0.0.0.0 UG 0 0 0 eth0

[RH9] # cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.100.1 adsl.nguyendai.org adsl
192.168.100.2 vnpenguin.nguyendai.org vnpenguin

I don't know how to fix this problem because I'm new to SuSE.
Could you help me please.

TIA,
Quy NGUYEN DAI
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Vince Littler
2003-05-18 21:06:46 UTC
Permalink
Post by NGUYEN DAI Quy
Hi SuSEr!
Just installed SuSE 8.2. Yast is great! But I have problem with network.
In fact I install SuSE on my 2nd box (192.168.100.2) in which I have also
RH-9 & Conectiva-9. I have another linux box (192.168.100.1) for FW &
router of ADSL line.
Under RH9 & Conectiva-9, I need config default gw is 192.168.100.1 for box
192.168.100.2 and network works fine. But not under SuSE-8.2. By viewing
the kernel module, I see that the same kernel module was loaded in SuSE and
RH9 (8139too, I use NIC Realtek RTL-8139/8139C/8139C+).
-----------------------------------------------------------------------
[SuSE] > /sbin/route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface 192.168.100.0 192.168.100.1 255.255.255.0 UG 0 0
0 eth0 192.168.100.0 0.0.0.0 255.255.255.0 U 0 0
0 eth0
-----------------------------------------------------------------------
This routing table is rubbish [ignoring the corruption in my quoting], I
assume it is for 192.168.100.2.

It says:

*** anything to 192.168.100.xxx goes via 192.168.100.1
*** anything to 192.168.100.xxx goes via eth0
Post by NGUYEN DAI Quy
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface 192.168.100.0 0.0.0.0 255.255.255.0 U 0 0
0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0
0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
0 lo 0.0.0.0 192.168.100.1 0.0.0.0 UG 0 0
0 eth0
It says

*** anything to 192.168.100.xxx goes via eth0
*** anything to 169.254.xxx.xxx [ this line looks like rubbish, but it is
almost harmless]
*** anything to localhost [127.0.0.1] goes via l0, the local interface
*** anything to anywhere not dealt with above goes via 192.168.100.1


Hope that helps


Vince Littler
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
NGUYEN DAI Quy
2003-05-18 21:20:12 UTC
Permalink
Post by Vince Littler
Post by NGUYEN DAI Quy
Hi SuSEr!
Just installed SuSE 8.2. Yast is great! But I have problem with network.
In fact I install SuSE on my 2nd box (192.168.100.2) in which I have also
RH-9 & Conectiva-9. I have another linux box (192.168.100.1) for FW &
router of ADSL line.
Under RH9 & Conectiva-9, I need config default gw is 192.168.100.1 for box
192.168.100.2 and network works fine. But not under SuSE-8.2. By viewing
the kernel module, I see that the same kernel module was loaded in SuSE and
RH9 (8139too, I use NIC Realtek RTL-8139/8139C/8139C+).
-----------------------------------------------------------------------
[SuSE] > /sbin/route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface 192.168.100.0 192.168.100.1 255.255.255.0 UG 0 0
0 eth0 192.168.100.0 0.0.0.0 255.255.255.0 U 0 0
0 eth0
-----------------------------------------------------------------------
This routing table is rubbish [ignoring the corruption in my quoting], I
assume it is for 192.168.100.2.
*** anything to 192.168.100.xxx goes via 192.168.100.1
*** anything to 192.168.100.xxx goes via eth0
Post by NGUYEN DAI Quy
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface 192.168.100.0 0.0.0.0 255.255.255.0 U 0 0
0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0
0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
0 lo 0.0.0.0 192.168.100.1 0.0.0.0 UG 0 0
0 eth0
It says
*** anything to 192.168.100.xxx goes via eth0
*** anything to 169.254.xxx.xxx [ this line looks like rubbish, but it is
almost harmless]
*** anything to localhost [127.0.0.1] goes via l0, the local interface
*** anything to anywhere not dealt with above goes via 192.168.100.1
Hope that helps
Vince Littler
Sorry, I dont understand your explanations. Could you tell me more about it please.
TIA
Q
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
NGUYEN DAI Quy
2003-05-19 04:59:34 UTC
Permalink
Hi,

Just try to play with route. Here is the router table:

vnpenguin:~ # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.100.1 0.0.0.0 UG 0 0 0 eth0

vnpenguin:~ # ifconfig
eth0 Link encap:Ethernet HWaddr 00:08:A1:34:FF:12
inet addr:192.168.100.2 Bcast:192.168.100.255 Mask:255.255.255.0
inet6 addr: fe80::208:a1ff:fe34:ff12/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29 errors:0 dropped:0 overruns:0 frame:0
TX packets:31 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:3235 (3.1 Kb) TX bytes:2878 (2.8 Kb)
Interrupt:11 Base address:0xd000

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:56 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3952 (3.8 Kb) TX bytes:3952 (3.8 Kb)

But the same error (Destination Host Unreachable) is always presented for pinging to
192.168.100.1 (the SuSE box is 192.168.100.2).

When I do dmesg, I see:
[...]
8139too Fast Ethernet driver 0.9.26
eth0: RealTek RTL8139 Fast Ethernet at 0xe486d000, 00:08:a1:34:ff:12, IRQ 11
eth0: Identified 8139 chip type 'RTL-8139C'
eth0: Setting 100mbps full-duplex based on auto-negotiated partner ability 41e1.
[...]
IPv6 v0.8 for NET4.0
IPv6 over IPv4 tunneling driver
usb.c: registered new driver hiddev
usb.c: registered new driver hid
input0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb2:2.0
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <***@suse.cz>
hid-core.c: USB HID support drivers
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux video capture interface: v1.00
eth0: no IPv6 routers present
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 00002000. (queue head)
eth0: Tx descriptor 1 is 00002000.
eth0: Tx descriptor 2 is 00002000.
eth0: Tx descriptor 3 is 00002000.
eth0: Setting 100mbps full-duplex based on auto-negotiated partner ability 41e1.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Tx queue start entry 12 dirty entry 8.
eth0: Tx descriptor 0 is 00002000. (queue head)
eth0: Tx descriptor 1 is 00002000.
eth0: Tx descriptor 2 is 00002000.
eth0: Tx descriptor 3 is 00002000.
eth0: Setting 100mbps full-duplex based on auto-negotiated partner ability 41e1.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Tx queue start entry 27 dirty entry 23.
eth0: Tx descriptor 0 is 00002000.
eth0: Tx descriptor 1 is 00002000.
eth0: Tx descriptor 2 is 00002000.
eth0: Tx descriptor 3 is 00002000. (queue head)
eth0: Setting 100mbps full-duplex based on auto-negotiated partner ability 41e1.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 00002000. (queue head)
eth0: Tx descriptor 1 is 00002000.
eth0: Tx descriptor 2 is 00002000.
eth0: Tx descriptor 3 is 00002000.
eth0: Setting 100mbps full-duplex based on auto-negotiated partner ability 41e1.
----------end----------------------------------------------------------

What does it mean the line "eth0: no IPv6 routers present" ?

I forgot to tell you that I used a Crosswired cable for connecting my 2 PCs. Is there special
option of NIC conconfiguration uder SuSE ? With Windows 2000, RH9 & Conectiva9 (under the same
PC) I done not special configuration at all and it works fine for 3 OSes.

Thank you in advance,
Regards,
Quy NGUYEN DAI
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Loading...