Project

General

Profile

Actions
Copy link

Bug #13363

closed

Pfsense 2.6.0 Buggy and Should have Remained in Development Branch (one bug report inside). Usage issues as well

Added by Dragon Master almost 3 years ago. Updated almost 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Configuration Backend
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.6.0
Affected Architecture:

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.

https://imgur.com/zxB2GyM.png

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.

Actions
Copy link
 #2

Updated by Jim Pingle almost 3 years ago

  • Status changed from New to Rejected

First, most of those are not bugs, but known limitations. Like the gateway thing -- you set it to auto, it's doing auto. If you don't like what auto does, make your own group.

Second, stick to the forum until definite bugs can be identified or features vetted.

One item per issue. These are all unrelated and have no bearing on each other and do not belong on a single Redmine issue.

But do not open a new one without first discussing your items on the forum. Starting a post isn't enough, there isn't any discussion there yet.

Actions
Copy link

Also available in: Atom PDF