[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Network routing



According to Nils Rennebarth:
> On Mon, May 25, 1998 at 09:08:44PM +0200, Martin Str|mberg wrote:
> > Hello.
> > 
> > I'm running Debian 1.something. I've some trouble with my network
> > setup.
> > 
> > First a picture on my network:
> > 
> > -----------------  eth0  -----------------   eth1  -----------------
> > I  192.168.1.2  I <----> I  192.168.0.1  I  <----> I  192.168.0.2  I
> > -----------------        I  192.168.1.1  I         -----------------
> >                          -----------------
> > 
> > Now on 192.168.1.2 I run "/usr/sbin/traceroute 192.168.0.2":
> > traceroute to 192.168.0.2 (192.168.0.2), 30 hops max, 40 byte packets
> >  1  * * *
> >  2  * * *
> >  3  * * *
> > [The other 27 are just the same.]
> > 
> > On 192.168.1.2 "/sbin/route -n" reports:
> > Kernel IP routing table
> > Destination     Gateway         Genmask         Flags Metric Ref Use Iface
> > 192.168.1.0     0.0.0.0         255.255.255.0   U     0      0     3 eth0
> > 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0     2 lo
> > 0.0.0.0         192.168.1.1     0.0.0.0         UG    1      0   872 eth0
> > 
> > On 192.168.0.1/192.168.1.1 "/sbin/route -n" reports:
> > Kernel IP routing table
> > Destination     Gateway         Genmask         Flags Metric Ref Use Iface
> > 192.168.1.0     0.0.0.0         255.255.255.0   U     0      0     4 eth0
> > 192.168.0.0     0.0.0.0         255.255.255.0   U     0      0     0 eth1
> > 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0     6 lo
> This is strange, because up to now, everything is ok, and traceroute should
> at least proceed from 1.2 to 1.1
> 
> - what does ping 192.168.1.1 give when issued on 192.168.1.2 ?

kant:~> ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=0.2 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.2 ms


> - Are you sure, IP-Forwarding is enabled on 192.168.1.1 ? You need to
>   compile a custom kernel for this, the debian ones don't have it enabled.

It seems it's not compiled in (found out by checking the .config file;
if it was the right file I found). Can this be verified in some other
way? Like "cat /proc/net/something"?

> - The routes on 192.168.0.2 need to be
>   ifconfig eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255
>   route add -net 192.168.0.0
>   route add default gw 192.168.0.1

They are.

> - what does ping 192.168.0.1 give when issued on 192.168.0.2 ?

skrot:~> ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=3.6 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=3.4 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=3.4 ms

--- 192.168.0.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 3.4/3.4/3.6 ms


To conclude it seems I need to enable IP-Forwarding in the kernel.


Thanks,

							MartinS


--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org


Reply to: