Re: Debian Sarge Routing
On Sat, 02 Oct 2004 11:12:46 +1000
"Peter A. Cole" <peteracole@bigpond.com> wrote:
> Hi all,
>
> I'm trying to get very basic routing happening between two locally connected subnets on Debian Sarge.
>
> I'm doing some disaster recovery planning at work which requires me to test some replication with two subnets connected by an IPSec tunnel, but for my testing I'm just routing between the two using VMWare.
>
> Anyway, in my Debian virtual machine, I have 2 NIC's configured as shown below, with IP forwarding turned on.
>
> /etc/network/options:
>
> ip_forward=yes
> spoofprotect=yes
> syncookies=no
>
> /etc/network/interfaces:
>
> auto lo
> iface lo inet loopback
>
> auto eth0
> iface eth0 inet static
> address 172.16.1.1
> netmask 255.255.255.0
> network 172.16.1.0
> broadcast 172.16.1.255
>
> auto eth1
> iface eth1 inet static
> address 172.16.2.1
> netmask 255.255.255.0
> network 172.16.2.0
> broadcast 172.16.2.255
>
> On both of the other virutal machines, they are set up with the appropriate gateway address of 172.16.1.1 and 172.16.2.1.
>
> >From the machine on 172.16.1.10, I can ping 172.16.1.1 and 172.16.2.1, but I cannot ping the machine on 172.16.2.10.
>
> >From the machine on 172.16.2.10, I can ping 172.16.2.1, but not 172.16.1.1 or the other machine on 172.16.1.10.
>
> Am I doing something wrong here by just enabling IP forwarding to allow the routing to occur? Or do I need something like Quagga for this to work?
>
> Regards,
>
> Pete
>
Sorry, I forgot to also mention that I had run these two commands which produced exactly the same results as above:
route add -net 172.16.2.0 netmask 255.255.255.0 gw 172.16.2.1
route add -net 172.16.1.0 netmask 255.255.255.0 gw 172.16.1.1
Pete
Reply to: