RV042 Router to Connect Two Subnets

I have two subnets:


I want to be able for clients on one subnet to be able to talk to clients on the other.

In between I'm placing a Cisco RV042 router.

I'm in a little over my head and could really use some help.

If anyone has experiencing doing this sort of thing with an RV042, please chime in.
Who is Participating?
Fred MarshallConnect With a Mentor PrincipalCommented:
The routing "rules" may not be so stringent when there are private addresses on both sides.

Assuming that is the subnet with the internet gateway on it, start by assigning an available IP address in the subnet on the WAN1 interface as a static address entry.  Include the gateway address being used on and the DNS address being used on

On the LAN side, assign an available IP address on the subnet.  You will use this address as the gateway for the subnet IF you are getting internet service from the side.

Note that the "internet" side is on the WAN side.  It won't work switched around.

Make sure the Mode is Router and not Gateway.  This means "no NAT".

I believe this is all you need to do.
Look at the routing table.  It should show that goes to 10.0.0.yyy where yyy is the address of the WAN1 port.  It should show that goes to 10.0.1.zzz where zzz is the address of the LAN side.

If for some reason the routing table doesn't show these then add them.

Then, if there is another device as internet gateway on the side, you add a route there that says goes to 10.1.0.zzz.
And, on the gateway on the side, you add a route that says goes to 10.0.0.yyy.
These last two gateway routes assure that return packets (which will hit the gateway first) will be forwarded to the inter-LAN router.
Thomas GrassiConnect With a Mentor Systems AdministratorCommented:
When you use private addressing, packets are non-routable. That is the whole point; they do not 'escape into the wild,' of the internet. How to overcome that obstacle? You need to assign default routes so a packet striking the router going to an IP address ending in .0.x hits the router, the router knows which port to send it to. When you have assigned the default route, you have to assign that default route to every interface that isn't the default interface for that subnet. Ditto for the .1.x side. You need to assign an appropriate IP address to each interface so it is part of the assigned subnet: http://www.cisco.com/en/US/docs/ios/12_1/iproute/command/reference/1rdipadr.html#wp1017863 You have to turn on routing: http://www.cisco.com/en/US/docs/ios/12_1/iproute/command/reference/1rdipadr.html#wp1020435 Very helpful to your cause is to see the status of the Ip interface: http://www.cisco.com/en/US/docs/ios/12_1/iproute/command/reference/1rdipadr.html#wp1020814 

Let us know how you make out.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.