Bug #13363
closedPfsense 2.6.0 Buggy and Should have Remained in Development Branch (one bug report inside). Usage issues as well
0%
Description
1) Applying changes seems to take significantly longer. (Certain ones, I forgot which ones off the top of my head. I will probably edit this later to mention which ones.
2) Wireguard default gateway can be confused if you have multiple Gateways like WAN, OpenVPN1, Wireguard1. Wireguard will literally try to run through the OpenVPN1 gateway so Wireguard1 stops working when OpenVPN is turned off.
3) Applying configurations can fail. I was applying a DNS resolver setting when I got this.
Clicking save and apply again will not fix it. I had to alter the setting and then save and apply would work again. Then I could change them back to the desired settings. Then save and apply.
4) ( I was told this is intended and not a bug) There is no way to disable OpenVPN clients. Disabling the interface does not allow you to disable the OpenVPN client. You have to delete the interface before you can disable it.
5) After you have disabled the OpenVPN client, you can then recreate the interface. Sometimes it puts this new interface on all your NAT Outbound rules you had for this interface originally and sometimes it doesn't so you have to manually add that interface back in for ever single NAT Outbound rule on that interface. This would not happen if you didn't have to delete the interface.