route with debian sarge shows an empty table

Hello,

I have debian sarge 3.1r1 installed into a VMware virtual machine. If I
use the command

# route or
# route -n

to display the routing table, an empty table is shown. Just the table
headers are displayed. Yesterday I had some luck. I could produce an
output with

# route -A inet.

But today it is like before. I don't get a result.

I have also a SuSE 9.0 installed into a virtual machine and there
everything runs fine. route produces an output.

Any idea?


thanks + regards
Klaus Gerhardt

Klaus Gerhardt wrote:
> Hello,
>
> I have debian sarge 3.1r1 installed into a VMware virtual machine. If I
> use the command
>
> # route or
> # route -n
>
> to display the routing table, an empty table is shown. Just the table
> headers are displayed. Yesterday I had some luck. I could produce an
> output with
>
> # route -A inet.
>
> But today it is like before. I don't get a result.
>
> I have also a SuSE 9.0 installed into a virtual machine and there
> everything runs fine. route produces an output.
>
> Any idea?

Show the contents of the file

/etc/network/interfaces

of the affected Debian set-up.

Please post it verbatim, instead of an own interpretation.

--

Tauno Voipio
tauno voipio (at) iki fi

Tauno Voipio schrieb:
> Show the contents of the file
>
> /etc/network/interfaces
>
> of the affected Debian set-up.
>
> Please post it verbatim, instead of an own interpretation.
>
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
# auto eth0
# iface eth0 inet dhcp
auto eth0
iface eth0 inet static
address 192.168.102.2
netmask 255.255.255.0
network 192.168.102.0
broadcast 192.168.102.255

auto eth1
iface eth1 inet static
address 192.168.103.1
netmask 255.255.255.0
network 192.168.103.0
broadcast 192.168.103.255

# auto eth2
# iface eth2 inet dhcp

Here it is.

regards
Klaus

Klaus Gerhardt wrote:
> Tauno Voipio schrieb:
>
>> Show the contents of the file
>>
>> /etc/network/interfaces
>>
>> of the affected Debian set-up.
>>
>> Please post it verbatim, instead of an own interpretation.
>>
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> # auto eth0
> # iface eth0 inet dhcp
> auto eth0
> iface eth0 inet static
> address 192.168.102.2
> netmask 255.255.255.0
> network 192.168.102.0
> broadcast 192.168.102.255
>
> auto eth1
> iface eth1 inet static
> address 192.168.103.1
> netmask 255.255.255.0
> network 192.168.103.0
> broadcast 192.168.103.255
>
> # auto eth2
> # iface eth2 inet dhcp
>

Thanks.

This looks reasonable. It should set up routes to
192.168.102.0/24 via eth0 and 192.168.103.0/24 via eth1.

As such, no default route will be set. It probably blocks
your DNS, which may cause weird output of 'route'.

Try again with

route -n

to prevent the DNS interference.

--

Tauno Voipio
tauno voipio (at) iki fi

Tauno Voipio schrieb:
> As such, no default route will be set. It probably blocks
> your DNS, which may cause weird output of 'route'.
>
> Try again with
>
> route -n
>
> to prevent the DNS interference.
That I did already. It is the same result. There is no
DNS-Server running in that system. So there should be also
no interference from it. I installed iproute now and use "ip route
show". It works fine. But I'm still curious why route doesn't work.

regards
Klaus

Klaus Gerhardt wrote:
> Tauno Voipio schrieb:
> > As such, no default route will be set. It probably blocks
> > your DNS, which may cause weird output of 'route'.
> >
> > Try again with
> >
> > route -n
> >
> > to prevent the DNS interference.
> That I did already. It is the same result. There is no
> DNS-Server running in that system. So there should be also
> no interference from it. I installed iproute now and use "ip route
> show". It works fine. But I'm still curious why route doesn't work.
>
> regards
> Klaus

Have you found the answer to this yet? I have the
same problem in Debian Sarge. The default route
set up by the ifconfig command DOES exist and works
fine, but it doesn't show up in the route command!

Ron from Michigan schrieb:
> Have you found the answer to this yet? I have the
> same problem in Debian Sarge. The default route
> set up by the ifconfig command DOES exist and works
> fine, but it doesn't show up in the route command!
>
I haven't. I had a diskussion about the subject also on
linux.debian.user.german. But until now nobody has a clue. I think the
best is to use 'ip route show' from the package iproute instead.

Grüsse
Klaus

--
Klaus Gerhardt * Holsteinische Str. 13 * 10717 Berlin
+49 (30) 8620 1523 * k-(E-Mail Removed)
http://www.kg-it.de * http://linuxseiten.kg-it.de

Klaus Gerhardt wrote:
> Ron from Michigan schrieb:
>
>> Have you found the answer to this yet? I have the
>> same problem in Debian Sarge. The default route
>> set up by the ifconfig command DOES exist and works
>> fine, but it doesn't show up in the route command!
>>
> I haven't. I had a diskussion about the subject also on
> linux.debian.user.german. But until now nobody has a clue. I think the
> best is to use 'ip route show' from the package iproute instead.
>
> Grüsse
> Klaus
>
What does route show after running route add default gw 192.xxx.xxx.xxx?

kevin schrieb:
> What does route show after running route add default gw 192.xxx.xxx.xxx?
An empty table. The route is functioning. A ping to a host in that net
ist answered. But the table is always empty.

regards
Klaus