Problem with Routing

Hello,
I hope I am here in the right place (newbie with news).
I have probably a problem with my routing. I have set a route for
192.168.0.0/16 to my networkcard but if I ping to an existing
computer on that network (192.168.0.6) it is said
"Destination Host unreachable) and the real strange thing about it, is that
these packets were send through the device lo instead of eth0
(found out by ifconfig-> tx). If I ping to the ip of the computer it self
i get pings back, but they are too routed through the loopback device.
I am running Suse 8.1. My Networkcard was recognised automatically
by the installation (rtl8139 chipset). Has anybody any idea how to
solve the problem? I haven't found anything on the Internet (mabe I
used the wrong keywords), I hope I gave every nessesary information.
Can anybody help me?
Thank you in advance,
Manuel

route:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0

ifconfig (after 12 pings to 192.168.0.6)
eth0 Link encap:Ethernet HWaddr 00:20:ED:B6:E6:0F
inet addr:192.168.0.2 Bcast:192.168.255.255 Mask:255.255.0.0
inet6 addr: fe80::220:edff:feb6:e60f/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:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:10 Base address:0xc000

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

Manuel Thiele wrote:
> Hello,
> I hope I am here in the right place (newbie with news).
> I have probably a problem with my routing. I have set a route for
> 192.168.0.0/16 to my networkcard but if I ping to an existing
> computer on that network (192.168.0.6) it is said
> "Destination Host unreachable) and the real strange thing about it, is that
> these packets were send through the device lo instead of eth0
> (found out by ifconfig-> tx). If I ping to the ip of the computer it self
> i get pings back, but they are too routed through the loopback device.
> I am running Suse 8.1. My Networkcard was recognised automatically
> by the installation (rtl8139 chipset). Has anybody any idea how to
> solve the problem? I haven't found anything on the Internet (mabe I
> used the wrong keywords), I hope I gave every nessesary information.
> Can anybody help me?
> Thank you in advance,
> Manuel
>
> route:
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 192.168.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
>
> ifconfig (after 12 pings to 192.168.0.6)
> eth0 Link encap:Ethernet HWaddr 00:20:ED:B6:E6:0F
> inet addr:192.168.0.2 Bcast:192.168.255.255 Mask:255.255.0.0
> inet6 addr: fe80::220:edff:feb6:e60f/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:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> Interrupt:10 Base address:0xc000
>
> 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:12 errors:0 dropped:0 overruns:0 frame:0
> TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:1232 (1.2 Kb) TX bytes:1232 (1.2 Kb)
>

You are missing the default route.

The data (1232 bytes) is probably DNS queries trying to
reverse-dns your target address.

Try again with

ping -n 192.168.0.6

to prevent the DNS searches.

Are you sure that the Ethernet connection is electrically up?
Check the link lights at both ends of the connection.

You can trace what happens with tcpdump or Ethereal.

HTH

Tauno Voipio
tauno voipio (at) iki fi

Hallo
I solved the problem by the kerneloption "acpi=off".
THX
Manuel

Hallo
I solved the problem by the kerneloption "acpi=off".
THX
Manuel

Hallo
I solved the problem by the kerneloption "acpi=off".
THX
Manuel