RV082 creating a route for all internet traffic

Well i made a little progress.  I added route
Destination IP: 0.0.0.0
Destination Subnet:0.0.0.0
Default Gateway 192.168.1.1
Hop Count ??

I can see the data trying to go now but if i do a ping from either side i see TTL expired in transit.
It wants a Hop Count between 1-15 i have tried every number 1-15 and get the same TTL expired in transit.

Any ideas out there?

Is there a default route on RV042 that says the following?

Destination IP: 0.0.0.0
Destination Subnet:0.0.0.0
Default Gateway: [your ISP's gateway address]

Otherwise, the traffic from RV082 would get routed to RV042, then have nowhere to go.

Also, what are you pinging?  For instance, my firewalls ignore all ping requests on all IP adresses (WANs and LAN).  So, it might not indicate a problem.

Yes on the RV042 router there is the 0.0.0.0 route and internet on the RV042 works just fine.

The ping i tried was from my computer connected to the RV042 to a computer on the RV082vlan8.  I got TTL expired in transit.  If i dont have the 0.0.0.0 route listed below in the RV082 the pings go through just fine but as soon as i added the below route into the RV082 it stops being able to communicate between the 2.
Destination IP: 0.0.0.0
Destination Subnet:0.0.0.0
Default Gateway 192.168.1.1
Hop Count ??

I am assuming that the internet is on the WAN side of the RV042.

On the RV082 - change the destination subnet to destination host 192.168.1.1 & check & if they see the internet from the RV082 computers.

If you want to to ping from computer to computer across the routers you will need some additional routes added in.
Let us know if this works.

Ok if i do not have the 0.0.0.0 route in there Lan to Lan pinging works perfectly NO issues so RV042 can see all vlan devices on RV082 i have those routes in there.  Say if i make a route in the RV082
4.4.4.0
255.255.255.0
192.168.10.1
Then i can ping WAN DNS servers at 4.2.2.1 and 4.2.2.2 just fine.  BUT if i add the all WAN IP
0.0.0.0
0.0.0.0
192.168.10.1
That causes all RV042 to RV082 Vlan traffic to get TTL expires.

0.0.0.0
0.0.0.0
192.168.10.1  <--where is the "10." network?  You only mentioned "1." and "2."

This is a default route.  Meaning, if no other routes are listed for the destination IP address, use this one.  So, it should be last.

Is this what your network looks like?
network-two-LANs.jpg

ops i meant 192.168.1.1
Your diagram is almost correct except on the RV082 there are 2 Vlans.  
Vlan1 is a LAN 192.168.1.2 / Vlan8 is LAN 192.168.2.2  There is no WAN connection on the RV082.

Why is VLAN1 using the same address range as LAN1?
You have nothing plugged into the RV082's WAN port?
Does that mean you are using a patch cable from RV042 LAN port to RV082 LAN port?

In that case, why not just leave all the VLAN routing on one router...no need to use two devices.  Or, am I missing something?

the devices are physically about a quarter mile apart in different buildings.  They are 2 completely separate networks that use the same WAN connection. They also have devices on each network they share but they have separate dhcp servers hence the vlans to keep the broadcast traffic separate.  

Here is what i got for a current layout.
layout.jpg

OK.  This is what I would do:

Delete the top 2 routes in each router.  They are "routing" to the same subnet as the source subnet and are unneeded in your design.  This is handled automatically.

On the RV042:
no additional routes needed.

On the RV082 add 1 route:
destination : 0.0.0.0
mask: 0.0.0.0
next hop: 192.168.1.1

That should do it.  Let us know.

One note:
It is those top 2 routes that are bouncing the pings back and forth until the ttl expires.  Getting rid of them is going to clean up the ttl problem and let the routing work correctly.

Well got it kind of figured out thought i am not sure why the solution works. There is a 4th field that i mentioned about HOP Count. The values are below are what they are but i needed to add another Route.
Routing Table:
Destination IP       Subnet Mask          Default Gateway     HOP Count
192.168.2.0      255.255.255.0       192.168.2.2             0
192.168.2.0      255.255.255.0              *                              50
0.0.0.0            0.0.0.0                    192.168.1.1            15
ADDED:
192.168.2.0      255.255.255.0       192.168.2.2             3

From what i gather the "Hops" are the number of devices it does through. The first entry is with Hops 0 is auto generated by the router i couldnt change its value but as soon as i added the entry with the Hops of 3 everything came online and is working the way i was planning to have it!

Ok now i have ran into another issue.  I am about ready to kick these cisco's to the curb.  The issue i have now is in the I need to forward a WAN port to a IP on the 192.168.0.x network but when i go into port forwarding there is only options for 192.168.1.x forwarding....

This is the first time you mentioned the 192.168.0.x network.  It's really hard to follow (& diagnose) what you are trying to do when the topology keeps changing.

I think I have a solution that will be much simpler and easier to administer.  Check out the graphic & let us know what you think.

RV042-RV082.jpg