Bug #3808
closed
Disabled OpenVPN tunnel cause network port disappear after reboot
0%
Description
Disabled OpenVPN tunnel cause network port disappear after reboot.
To reproduce the issue:
- Create an OpenVPN tunnel
- Create an interface and assign OpenVPN network port
- Disable OpenVPN tunnel
At this stage, in interface the OpenVPN network port is still assigned
- Reboot pfSense
- The network port is now missing and the interface is shown as assigned to the first network interface
Pressing save on the assign interface screen before enable/disable OpenVPN tunnel will mess up the configuration
This issue is present in 2.1.4 and 2.2
Updated by Chris Buechler over 10 years ago
- Priority changed from Normal to Very Low
not sure this can really be considered a bug, it's more like "I yanked a NIC out of my system and now my interface assignments are wrong." Uh, yeah, of course they are. Don't do that, or make sure to re-assign if you do.
Updated by Damien Flament over 10 years ago
Well if you are running out of physical interface you can't re-assign. The only solution is to enable the tunnel (or delete the interface or the tunnel). Deleting interface will delete associated firewall rules, enable the tunnel is not always desirable especially if you are working remotely.
Updated by Marcos M almost 4 years ago
- Status changed from New to Resolved
Tested on 2.4.5p1
This has been resolved. The ovpnsX network port stays assigned to the proper interface after a reboot.