Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Bug in Pfsense x64 version 2.6.0

    Scheduled Pinned Locked Moved General pfSense Questions
    10 Posts 4 Posters 1.1k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      Ryu945
      last edited by

      You can't disable OpenVPN interfaces after updating from 2.5.2 to 2.6.0 . It forces you to delete the interface before you can turn them off.

      1 Reply Last reply Reply Quote 0
      • J
        Jarhead
        last edited by

        @ryu945 Not a bug, by design.
        a lot of complaints already.

        R 1 Reply Last reply Reply Quote 0
        • R
          Ryu945 @Jarhead
          last edited by

          @jarhead It is such an annoying design decision that I already wish there was an easy way to go back to 2.5.2 without having to completely reinstall Pfsense.

          1 Reply Last reply Reply Quote 0
          • Cool_CoronaC
            Cool_Corona
            last edited by

            There are so many things that just doesnt play well in 2.6.0 compared to 2.5.2

            Its hopeless and slow in a production environment.

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              Because it was broken in 2.5.2. Disabling an assigned interface leaves the firewall in an invalid state. Unpredictable things may happen and that's the last thing you want from a firewall.

              Cool_CoronaC 1 Reply Last reply Reply Quote 0
              • Cool_CoronaC
                Cool_Corona @stephenw10
                last edited by

                @stephenw10 But you should be able to disable it and let it stay there.

                Not deleting it and then disable something that doesnt exist.

                R 1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  The OpenVPN config does still exist and can be disabled after it's been unassigned.

                  I agree though it might be nice to have it automatically disable the assigned interface when you disable the tunnel config for example. Doing that safely may well be a lot more involved though. Forcing the user to unassign it first is the safest option.

                  Steve

                  1 Reply Last reply Reply Quote 0
                  • R
                    Ryu945 @Cool_Corona
                    last edited by Ryu945

                    @cool_corona @stephenw10 Problem is that disabling the interface doesn't let you turn off OpenVPN either. Nothing short of deleting the interface allows you to turn off OpenVPN. This can lead to broken NAT rules if you don't fix your rules when you recreate the VPN. Sometimes the rules fix themself when you recreate the interface and sometimes you have to manually fixed all the rules for that interface.

                    It has been possible to turn off OpenVPN servers since 1.x.x days at least and not having this adds a lot more work in figuring things out.

                    1 Reply Last reply Reply Quote 0
                    • stephenw10S
                      stephenw10 Netgate Administrator
                      last edited by

                      That's only true is you assign the server as an interface and that's usually not required for a server.

                      For an OpenVPN client where you need to policy route across it that is often the case though.

                      R 1 Reply Last reply Reply Quote 0
                      • R
                        Ryu945 @stephenw10
                        last edited by

                        @stephenw10 I mostly use it for clients. I haven't had to change a server OpenVPN client in awhile. There needs to be an easier way to turn on and off OpenVPN clients.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.