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

Forum Discussion

Dauterive's avatar
Dauterive
Aspirant
Jul 28, 2023

Bug Report. Send to developers!

Hello all. I setup a openvpn server on my computer. It worked great until I changed routers. My previous router was Asus AC1900. New router is RAX54. The issue seems to be that "static routes don't allow WAN access". As noted by someone else already 4 months ago here.

 

On RAX54, I ensure that the computer running the server has a reserved (local) ip address and that the static route points to it with a 'hop count' of 2.

 

To test my connection I set up a virtualbox machine on the same computer as the server. I connect from the virtualmachine to the openvpn server, running on the host, using loopback interface. Inside virtualmachine, pings to local addresses (eg 192.168.1.x) are ok. Pings to internet (eg 8.8.8.8) fail! (Good on AC1900) Traceroute shows the last hit is the router (192.168.1.1). This is the exact scenario that was already detailed in the linked post. 

 

I understand that the router has openvpn server built-in, however it is not customizable (eg. encryption protocol, compression, etc.) and lacks the fine grain control I have when running my own server.

 

Obviously the router is the issue, so please send to developers this report as it is a very important issue to me and I may have to change routers if not resolved. Firmware version: (latest) V1.0.12.120_2.0.83

 

What might be of note is that when adding a static route there is a checkbox that says "private"; on the details of this checkbox it says "select private to limit access to LAN only". If I had to make an educated guess as to what is wrong, the programming for that checkbox is broken and it acts like it is always on even though it is not checked.

 

3 Replies


  • Dauterive wrote:

    Hello all. I setup a openvpn server on my computer. It worked great until I changed routers. My previous router was Asus AC1900. New router is RAX54. The issue seems to be that "static routes don't allow WAN access". As noted by someone else already 4 months ago here.

     

    On RAX54, I ensure that the computer running the server has a reserved (local) ip address and that the static route points to it with a 'hop count' of 2.

     

    To test my connection I set up a virtualbox machine on the same computer as the server. I connect from the virtualmachine to the openvpn server, running on the host, using loopback interface. Inside virtualmachine, pings to local addresses (eg 192.168.1.x) are ok. Pings to internet (eg 8.8.8.8) fail! (Good on AC1900) Traceroute shows the last hit is the router (192.168.1.1). This is the exact scenario that was already detailed in the linked post. 

     

    I understand that the router has openvpn server built-in, however it is not customizable (eg. encryption protocol, compression, etc.) and lacks the fine grain control I have when running my own server.

     

    Obviously the router is the issue, so please send to developers this report as it is a very important issue to me and I may have to change routers if not resolved. Firmware version: (latest) V1.0.12.120_2.0.83

    You sure you have the latest? 

    https://community.netgear.com/t5/Nighthawk-with-WiFi-6-AX-and/New-RAX35-38-40-42-43-45-50-54-Firmware-Version-1-0-15-128-Hot/td-p/2314558/jump-to/first-unread-message

     

     

    What might be of note is that when adding a static route there is a checkbox that says "private"; on the details of this checkbox it says "select private to limit access to LAN only". If I had to make an educated guess as to what is wrong, the programming for that checkbox is broken and it acts like it is always on even though it is not checked.

     


     

    • Dauterive's avatar
      Dauterive
      Aspirant

      I manually updated because the router kept telling me there was no update. Now on  V1.0.15.128_2.0.89 it is still same problem.