NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

TeamT's avatar
TeamT
Star
Jan 09, 2021

R6220 - Static Routes issues

I have established a VPN-tunnel (OpenVPN tun) to our summer house for LAN to LAN communication (two subnets). A static route is needed in the routers in both ends for the router to understand how to route traffic to the other subnet. I have identified two issues that I am convinced are bugs in the R6220 firmware.

 

Issue 1:

The static route is ignored after reboot or WAN interface restart (e.g. disconnect/connect the WAN cable). The static route can easilly be activated again by edit/save of the static route.

Traceroute before and after restart can be used to verify this issue.

The issue is also reported in this post https://community.netgear.com/t5/General-WiFi-Routers-Non/R6220-loosing-static-route/td-p/1493836

 

Issue 2:

Outgoing routing is working fine but response to incoming traffic is not routed back. You would expect the router to redirect the traffic in accordance with the static route (or in worst case route it to the VPN-tunnel). This issue is verified by Wireshark. Worth mentioning is that the issue is resolved by replacing the router by another brand.

 

My personal advise is to select another router if you need static routes.

 

2 Replies

  • > Outgoing routing is working fine but response to incoming traffic is
    > not routed back. You would expect the router to redirect the traffic in
    > accordance with the static route (or in worst case route it to the
    > VPN-tunnel). [...]

     

       I would?  Every static route I've ever seen has a destination, not a
    source.  It's a one-way instruction.  I'd expect routing in the other
    direction to be the responsibility of the fellow at the other end.

     

       Of course, with my weak psychic powers, I can't see any of your
    addresses or routes, so what do I know?

     

    > My personal advise is to select another router if you need static
    > routes.

     

       Might be good advice.  Your "Issue 1" suggests that.  I don't know
    what "Issue 2" is supposed to tell me.

    • TeamT's avatar
      TeamT
      Star

      antinode wrote:

      > Outgoing routing is working fine but response to incoming traffic is
      > not routed back. You would expect the router to redirect the traffic in
      > accordance with the static route (or in worst case route it to the
      > VPN-tunnel). [...]

       

         I would?  Every static route I've ever seen has a destination, not a
      source.  It's a one-way instruction.  I'd expect routing in the other
      direction to be the responsibility of the fellow at the other end.

       

         Of course, with my weak psychic powers, I can't see any of your
      addresses or routes, so what do I know?

       

      > My personal advise is to select another router if you need static
      > routes.

       

         Might be good advice.  Your "Issue 1" suggests that.  I don't know
      what "Issue 2" is supposed to tell me.


      The other end is behaving as expected. The response to incomming traffic need the static route for the response to find its way back. The router is responsible for a redirect or routing based on the configured static route. Wireshark tells me that the response are sent to the routers MAC address but no redirect is sent from the router nor is the packet routed to the VPN-tunnel.