Any static routing experts here?

Question

Have a setup involving 3 routers and various workstations as follows
Ont Cat5 -> Actiontec wan port.  Actiontec subnet 192.168.1
Actiontec lan port -> Netgear wndr3200 wan port (192.168.1.253).  Netgear seubnet 192.168.0
Actiontec lan port -> Dlink dir655             wan port (192.168.1.254). Dlink subnet 192.168.3
Have user devices on all 3 subnets and the can all talk to the internet fine.  In addition can access the Actiontec admin from any device on the Netgear or Dlink subnets.
Would like to be able to access the Netgear and Dlink subnets from devices on Actiontec subnet.  I know this involes building static routes on all the routers and have done this but still can't access so presume either my static routes are incorrect or more likely there is something I have to in the router firewalls.  I lean more to the router firewalls as I am guessing they are blocking the inbound traffic.
Anybody have any hints as to how this is done?
Solved!
Go to Solution.

Answer 1

You'd generally have a static route pointed to the (WAN) address of the next router in the chain.
Your outside router (Actiontec) would have
static route 192.168.0.0/24 with the nexthop 192.168.1.253.
static route 192.168.3.0/24 with the nexthop 192.168.1.254.
Your Dlink and netgear shouldn't need any static routes needed (since they are, generally speaking, default routing to the wan port). The problem you're running into is that they're also NATing the address.
So when you receive a packet from 192.168.3.2 (connected to the DLINK) on 192.168.1.2 (connected to the ACTIONTEC) the receiving device sees src:192.168.1.254 dst:192.168.1.2 most likely. When you're sending a packet to 192.168.3.2, with a nexthop of 192.168.1.254, that natting part isn't going to work like you expect (it's expecting a packet to 192.168.1.254 with a specific port, which it will then port-forward to 192.168.3.2 on the port you tell it to, whether it's the same port or not, based on port forwarding rules built on the dlink).
Does that help at all? Unless you can turn natting off, you need to be doing port-based stuff with port forwarding, in the setup you're describing, IMO.
Paul