I'm trying to link two Cisco routers with a static route and I haven't been able to get it working as expected.

Here is the basic setup:

  • Router 1 - WRV210 - - connected to cable modem
  • Router 2 - RV120W -

I already have several machines on Router 1 that are working and I want to setup Router 2 with a few other machines on the different subnet.

Here is what I've configured:

  • Connected the WAN port on Router 2 to a LAN port on Router 1
  • Configured Router 1 to give to Router 2 via DHCP
  • Configured Router 1 with a static route ( mask to using the LAN & Wireless interface
  • Disabled the firewall on Router 2 (since it is covered by Router 1)
  • Configured Router 2 to "Router" mode instead of "NAT" mode
  • Configured Router 2 with a static route ( mask to using the WAN interface

From the research I've done I think that should be enough but things aren't working exactly as expected:

  • Router 2 can ping and (a machine on router 1)
  • A machine on Router 2 can ping and (a machine on router 1) ping and (a machine on router 1)
  • Router 1 can NOT ping or (a machine on router 2)
  • A machine on Router 1 can NOT ping or (a machine on router 2) can NOT ping or (a machine on router 2)
  • Router 1 and a machine on Router 1 can ping (Router 2 itself)

I'm confused as to why Router 1 cannot talk to the subnet. Any help would be greatly appreciated.

  • 1
    Would be much easier if you post configuration file. seems very strange to affect R2 IP by dhcp from R1...
    – radius
    Jun 2, 2010 at 10:21

2 Answers 2


Because the external interface on R2 is on the same LAN as the clients on, you'd need a route on each client on to route to via That should do the trick (assuming R2 is routing, not NAT, and has no firewall.)

If I were you, I'd throw the link between the two routers into its own administrative VLAN and then you could route through this VLAN.


Router 2 does not need a static route to, it already knows how to get to that subnet (via its interface). Router 1 does indeed need a route to, via

For 192.168.2.x clients, the gateway is For 192.168.1.x clients, the gateway is

At this point, 192.168.1.x clients don't know how to get to 192.168.2.x. Simplest but not most efficient solution: static route on every client pointing to via

  • Thanks for the reply - I tried the static route on the client machine (routing to and that doesn't seem to change anything. Jun 2, 2010 at 2:14
  • You also need to remove the " via" route on Router 2.
    – dtsomp
    Jun 2, 2010 at 7:30
  • 1
    Route on client is probably useless, default route to it should be enough as the router1 should route to router2
    – radius
    Jun 2, 2010 at 10:20
  • Could we see R2's routing table?
    – dtsomp
    Jun 3, 2010 at 15:37

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.