- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
R7000 VPN Error with pushed routing settings
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
R7000 VPN Error with pushed routing settings
What's going wrong
When I use the provided client configuration file against OpenVPN version 2.4.9 I get the following error:
Error: Invalid prefix for given prefix length. ERROR: Linux route add command failed: external program exited with error status: 2
The router is pushing the following control message, which is triggering the error:
PUSH: Received control message: 'PUSH_REPLY,route 10.1.10.0 255.255.255.0,route-delay 5,route-gateway dhcp,ping 10,ping-restart 120,route 10.1.10.1 255.255.255.0 10.1.10.1
The final command is what is triggering the error, as "route 10.1.10.1 255.255.255.0 10.1.10.1" is an invalid command. 10.1.10.1 cannot be the base for the /24.
Things attempted
I attempted to take this into my own hands by overriding the server's push by adding the following to the client configuration.
route 10.1.10.0 255.255.255.0 route-delay 5 route-gateway dhcp ping 10 ping-restart 120 route 10.1.10.0 255.255.255.0 10.1.10.1 route-nopull
This results in another, different error:
Error: Nexthop has invalid gateway. ERROR: Linux route add command failed: external program exited with error status: 2
Which has to do with the fact that my computer doesn't know how to talk directly to 10.1.10.1.
As far as I can tell, the VPN server on these routers is using TAP, and the device tap0. So I should be able to push the route-gateway via DHCP? However, perhaps pulling from the client side just isn't possible?
Because I don't have access to the server configuration directly, it is difficult to troubleshoot this problem. Does anything have any input?
• What is the difference between WiFi 6 and WiFi 7?
• Yes! WiFi 7 is backwards compatible with other Wifi devices? Learn more