Actions
Regression #13818
open
OpenVPN fails to start when a related static route already exists
Status:
New
Priority:
Low
Assignee:
-
Category:
OpenVPN
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
Affected Architecture:
Description
Tested on 23.01.b.20221230.0600.
- Configure an OpenVPN client in the GUI (tested with non-DCO); verify it's started/connected.
- Configure a static route for the tunnel network via the OpenVPN gateway; e.g.
172.16.1.0/24 via ovpnc2. - Stop the OpenVPN client service; verify that the route still exists in the routing table (it may take a moment to be re-added via
system_staticroutes_configure()). - Start the OpenVPN client service.
Results:
The OpenVPN client service fails to start, showing the following in the logs:
Jan 1 10:54:54 openvpn 79361 TUN/TAP device /dev/tun2 opened Jan 1 10:54:54 openvpn 79361 /sbin/ifconfig ovpnc2 172.16.1.0/24 mtu 1500 up Jan 1 10:54:54 openvpn 79361 FreeBSD ifconfig failed: external program exited with error status: 1 Jan 1 10:54:54 openvpn 79361 Exiting due to fatal error
This setup worked previously in 22.05.
Updated by
Updated by Kris Phillips over 2 years ago
Tested on 23.01 BETA for Dec 30. Can confirm this is the case.
Updated by Jim Pingle over 2 years ago
- Priority changed from Normal to Low
Static routes for non-DCO OpenVPN should always be managed by OpenVPN itself, a dynamic routing protocol, or policy routing.
Managing them in System > Routing has always been problematic and if it worked, was likely by luck.
There is probably room for improvement here but it's not a blocker, IMO.
Updated by Jim Pingle over 2 years ago
- Subject changed from OpenVPN fails to start when a related static route already exists. to OpenVPN fails to start when a related static route already exists
Actions