It's not a problem routing a private network to the internet via another
private network, but you do have to have your routes set up somewhere.
Simply connecting the interfaces and setting up the computer to route
between interfaces won't do it. If computers on the 172.17.0.0 network
point to 172.17.0.1 as their default gateway, then you'll need to add a
route to the 172.17.0.1 router that points traffic destined for the
172.18.0.0 network via 172.17.1.7. Computers on the 172.18.0.0 network
should use 172.18.0.1 as their gateway, and the box you're using for
your router should have a single default gateway, 172.17.0.1. If you
don't have access to the router, you could add the routes directly on
the computers for LAN-to-LAN, but you'll need the route on the router if
you want the 172.18 network to have Internet.
....kurt
(E-Mail Removed) wrote:
> 172.17.0.1 is the overall gateway. this means every packet with
> destination world has to pass through this. the subnet 172.17.0.0/16 is
> connected to this gateway. in addition i want to connect a second
> subnet 172.18.0.0/16 to 172.17.0.0/16. so this means: all traffic from
> 172.18.0.0/16 goes through 172.18.0.1, which is 172.17.1.7 (so not the
> overall gateway). from there it goes through the 172.17.0.1 to the
> internet.
>
> so i want to route a private network through another private network to
> the internet.
>
> regards
> moritz
>
Similar Threads
Linear Mode
