Bug #15453
closed
Assignment of OpenVPN port to an Interface shuts down OpenVPN access to Netgate 1100/2100
0%
Description
I have a Netgate 2100 that is set up with an OpenVPN server. I can readily connect to it remotely with the SparkLabs Viscosity client. When I define a VPN interface, however, in Interfaces → Interface Assignments, where it looks like this,
(see attached screenshot)
and I enable that interface, all access to the Netgate itself is blocked. This is also not a matter of having Allow firewall rules for the new interface. They do not help.
What’s more, simply disabling the new interface does not bring back access to the Netgate. I have to restore settings from a backup of the state the settings were in, before I made that change in Interfaces → Interface Assignments.
However, rebooting the appliance returns full OpenVPN functionality. It’s just that with it gone initially, I cannot reboot the appliance. I have to be local to do so.
Files
| Screenshot 2024-04-11 at 7.24.26 PM.png (17.9 KB) Screenshot 2024-04-11 at 7.24.26 PM.png | screenshot referenced above |
Updated by Jim Pingle about 1 year ago
- Project changed from pfSense Plus to pfSense
- Category changed from OpenVPN to OpenVPN
- Status changed from New to Not a Bug
- Affected Plus Version deleted (
23.09.1)
After assigning an OpenVPN interface you must edit/save the OpenVPN instance to properly reinitialize the underlying interface and OpenVPN daemon. The assignment process is known to interfere with its operation. This is covered in the documentation: https://docs.netgate.com/pfsense/en/latest/vpn/openvpn/assign.html