cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1678
Views
0
Helpful
3
Replies

RV016 traffic routing

lucas.harms
Level 1
Level 1

I have a RV016 with an internal address of 192.168.1.1.  Also on the 192.168.1.0 network is a gateway server that the rest of my clients sit behind.  The clients are on a 172.16.3.0/24 network.  All of the gateway server does is forward the packets.  It does not NAT.  There is a static route to 172.16.3.0 on the RV016.

So my question is how do I get traffic from 172.16.3.0 to route through the RV016?  Computers on the subnet can ping the RV016 and get a reply so I know the gateway server is forwarding the packets between the two subnets just fine and that the static route on the RV016 works.  Any traffic that tries to go beyond the RV016 never makes it.  It just disappears at the RV016.  I have checked all of the ACLs and they should let all internal traffic through.  Anyone have suggestions?

1 Accepted Solution

Accepted Solutions

Te-Kai Liu
Level 7
Level 7

Which firmware is your RV016 on?

If it runs on firmware 4.0.3.03-tm, you need an additional access rule created to pass traffic from the 172-subnet.

Page 3 of the firmware release note has more information.

http://www.cisco.com/en/US/docs/routers/csbr/rv0xx/release/RV0xx_RN_v4-0-3-3.pdf

View solution in original post

3 Replies 3

Te-Kai Liu
Level 7
Level 7

Which firmware is your RV016 on?

If it runs on firmware 4.0.3.03-tm, you need an additional access rule created to pass traffic from the 172-subnet.

Page 3 of the firmware release note has more information.

http://www.cisco.com/en/US/docs/routers/csbr/rv0xx/release/RV0xx_RN_v4-0-3-3.pdf

I tried that earlier and it did not work.  After clicking the "restore to default" button, I was able to add a rule for the 172 subnet and it worked then.

While trying to troubleshoot, I enabled the deny policy events log and noticed something odd.  Some traffic gets denied no matter what the rules are.  It even gets denied with the firewall turned off.  Is there any way to find out what is causing this?  All it reports is a policy violation with the IP and ports.  There has not been a consistent IP or port that seems to cause it.  Appears to be random.

Lucas, the logging issue you mentioned is a known issue to be fixed.