Thanks.
I took a look at it, and found a few of anomalies.
First, it looks like there's a disagreement between the server and Router 1 about what is the actual LAN's mask. The server thinks the network 172.16.254.0's mask is 255.255.255.0, but Router1 says 255.255.255.248.
I also noticed a that Router 1 doesn't know the existence of the WAN (10.1.1.0), so any traffic not intended for LAN is route to the Internet (the default route). I would add this route on Router 1:
Code:
route add -net 10.1.1.0 netmask 255.255.255.0 gw 172.16.254.252 dev eth1
Note that the above command is using Ubuntu/Debian's syntax and options. It may be slightly different on the Routers (also I'm assuming eth0 goes to Internet and eth1 to the LAN).
Router 2 is kind of a puzzle to me. The subnetwork routes are OK: it knows where to go for the LAN and WAN. However its default route is oddly pointing to a machine inside the WAN (10.1.1.2). From what I understood, WAN's way to the rest of the world should be Router 1.
If that's correct, I would replace that route with this one (Router 2):
Code:
route add -net default netmask 255.255.255.0 gw 172.16.254.254 dev eth1
I hope that helps. Tell us what you think and how it goes.
Regards.
Bookmarks