Edubuntu routing question -- from external to internal (fwd)

David Van Assche dvanassche at gmail.com
Tue Nov 20 19:19:59 GMT 2007


Take a look here, this should add total routing, though masquerading
with something like shorewall will make it even more transparent:

https://wiki.ubuntu.com/ThinClientHowtoNAT

On Nov 20, 2007 8:07 PM, Gavin McCullagh <gmccullagh at gmail.com> wrote:
> Hi,
>
> On Tue, 20 Nov 2007, Tom Wolfe wrote:
>
> > I'm trying to allow access from the eth1 subnet (external) to the eth0
> > subnet (ineternal/Thin Client)
> >
> > I have a route set up on the external network
> > (192.168.192.0/255.255.252.0) as follows:
> >
> > route add -net 192.168.100.0 netmask 255.255.255.0 gw 192.168.192.18
>
> So this route is installed on each machine in the external network.  That
> sounds fine.
>
> > The Edubuntu/Gutsy server is 192.168.192.18 on eth1 as you might gather.
> >
> > pinging 192.168.100.254 (the Edubuntu server on eth0) from the 192.168.192.0
> > subnet gets no reply
>
> You need to tell the edubuntu that it should forward packets between
> networks (ie act as a router) or it will just ignore them.  This is
> generally done using
>
>         echo 1 > /proc/sys/net/ipv4/ip_forward
>
> which you should try first.
>
> However, you're asking it to route packets between two private network
> ranges which linux may not be keen on (as it breaks some network rules).
> One usually uses an iptables NAT rule in this instance but you may be able
> to get away without it, I'm not certain off the top of my head.
>
> Gavin
>
>
>
> --
> edubuntu-users mailing list
> edubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
>



More information about the edubuntu-users mailing list