In the network shown below, the Netgear router has a LAN interface address of 192.168.1.1 and its DHCP assigns addresses starting at 1.201.
The Linksys router's LAN interface address is 192.168.0.1 and its DHCP assigns addresses starting at 0.101. Its WAN interface is attached to the Netgear router at a static address of 192.168.1.10.
The problem is that computers on the .1.201 subnet cannot reach computers on the .0.101 subnet, even after disabling NAT and SPI firewall on the Linksys router, and adding a static route at the Netgear router as follows:
Destination IP: 192.168.0.0 Mask: 255.255.255.0 Gateway IP: 192.168.1.10
A tracert gets as far as 192.168.1.10 (192.168.0.1) then dies.
I wondered if the problem might be the return trip, but the existing route table at the Linksys router shown below already has an entry for 192.168.1.0 as follows, and won't let me add another route (complains about invalid static route):
Destination IP: 192.168.1.0 Mask: 255.255.255.0 Gateway: 0.0.0.0 Interface: WAN
Computers on the .0.101 subnet can reach computers on the .1.201 subnet - it is the reverse which is the problem.
Incidentally, the Netgear router is connected to the internet via its WAN port, and all computers on both networks can reach the internet.
My ultimate goal is to limit access from .1.201 to .0.101 to certain computers only, via static route(s).
Network diagram at http://flymike.dreamhosters.com/Static%20Route%20Problem.jpg