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

    To 2.5.1 or not ? that is the question :)

    Scheduled Pinned Locked Moved General pfSense Questions
    108 Posts 39 Posters 35.8k Views 33 Watching
    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.
    • YanikY Offline
      Yanik @vjizzle
      last edited by

      @vjizzle

      Yep, vpn port forwards.
      I can reach my server through Lan IP but cant from outside (domain).

      1 Reply Last reply Reply Quote 0
      • V Offline
        vjizzle
        last edited by

        I can see in my firewall logs that the ports I forwarded from the OpenVPN interfaces are being blocked. I can allow them using the + sign there (Easy rule option) and they do appear on the firewall rules on that specific OpenVPN interface but it still does not work.

        On that specific OpenVPN firewall tab I can see my original port forward rule is also there, beside the Easy rule I just added. But none of them are working it seems.

        YanikY M 2 Replies Last reply Reply Quote 0
        • D Offline
          Dredex @vjizzle
          last edited by

          I have dual WAN configuration and port forward only works on the default gateway.
          For me upgrading from 2.5.0 to 2.5.1 broke port forwarding on non default gateway.

          1 Reply Last reply Reply Quote 0
          • YanikY Offline
            Yanik @vjizzle
            last edited by

            @vjizzle

            my port forwards pass the firewall rule, no blocks but when i check states its "CLOSED:SYN_SENT".

            V 1 Reply Last reply Reply Quote 0
            • M Offline
              MoonKnight @vjizzle
              last edited by

              @vjizzle said in To 2.5.1 or not ? that is the question :):

              I can see in my firewall logs that the ports I forwarded from the OpenVPN interfaces are being blocked. I can allow them using the + sign there (Easy rule option) and they do appear on the firewall rules on that specific OpenVPN interface but it still does not work.

              On that specific OpenVPN firewall tab I can see my original port forward rule is also there, beside the Easy rule I just added. But none of them are working it seems.

              Yeah same her. Maybe it's time to report it. Make an bug-rapport. Can someone please add it on the bugtracker.

              --- 24.11 ---
              Intel(R) Xeon(R) CPU D-1518 @ 2.20GHz
              Kingston DDR4 2666MHz 16GB ECC
              2 x HyperX Fury SSD 120GB (ZFS-mirror)
              2 x Intel i210 (ports)
              4 x Intel i350 (ports)

              P 1 Reply Last reply Reply Quote 0
              • V Offline
                vjizzle @Yanik
                last edited by

                @yanik I can confirm the same CLOSED:SYN_SENT when I check the states. So far the 2.5 line of release is showing interesting behaviour. Every upgrade is a new adventure in squashing bugs....yay!

                YanikY 1 Reply Last reply Reply Quote 0
                • YanikY Offline
                  Yanik @vjizzle
                  last edited by

                  @vjizzle

                  while tried to decide pfsense vs opsense. I choose pfsense because of stability :D

                  V 1 Reply Last reply Reply Quote 0
                  • V Offline
                    vjizzle @Yanik
                    last edited by

                    @yanik Me too! Well let's give the dev's time to fix this. In the meantime I am planning to do a clean install of 2.5.1 and the restore my config. If that does not work I will revert back to a clean install of 2.5 and then restore my 2.5 config. I will make some time tonight to do this and I will post my updates here.

                    M YanikY 2 Replies Last reply Reply Quote 0
                    • M Offline
                      MoonKnight @vjizzle
                      last edited by MoonKnight

                      @vjizzle

                      We can continue here: https://forum.netgate.com/topic/162952/port-forwarding-on-openvpn-interfaces-is-broken-on-2-5-1

                      --- 24.11 ---
                      Intel(R) Xeon(R) CPU D-1518 @ 2.20GHz
                      Kingston DDR4 2666MHz 16GB ECC
                      2 x HyperX Fury SSD 120GB (ZFS-mirror)
                      2 x Intel i210 (ports)
                      4 x Intel i350 (ports)

                      1 Reply Last reply Reply Quote 0
                      • YanikY Offline
                        Yanik @vjizzle
                        last edited by

                        @vjizzle

                        Good luck :)..

                        Sure devs will fix this but i hope it wont take much time. at least a patch would be nice.

                        1 Reply Last reply Reply Quote 0
                        • C Offline
                          cellobita @Yanik
                          last edited by

                          @yanik Add me to the "Port forward works only on interface with default gateway, does not work for alternative wans" victims list...

                          I know, I know, "pfSense CE is free", blah, blah, blah, but it is also undeniable that pfSense CE (formerly just plain pfSense) is, today, quite far from the rock solid firewall distro of a few years back, when I used to upgrade without any trepidation.

                          Also, the fact that this very serious bug has been fixed in the commercial version, but not the free one (did no one at Netgate notice that the fix was relevant for CE also?!?!), makes me wonder...

                          Marcello Marques
                          Santos - SP - Brazil

                          V 1 Reply Last reply Reply Quote 1
                          • V Offline
                            vjizzle @cellobita
                            last edited by vjizzle

                            @cellobita wow I did not know that that port forwarding on OpenVPN was a bug for the Plus version and they fixed it! Do you have source where I can read this?

                            C 1 Reply Last reply Reply Quote 0
                            • C Offline
                              cellobita @vjizzle
                              last edited by

                              @vjizzle It was on the bugtracker for version 2.5.1 for many weeks - I was following the link below closely - and when it was fixed someone said the issue did not occur on CE; since it was a pf issue, I'm note sure how that could not affect all versions (please keep in mind that I am not a developer or software engineer, just a tech savvy guy).

                              The issue tracker has been added to a few minutes ago to note that the issue is now(?) happening on CE too.

                              https://redmine.pfsense.org/issues/11436

                              Marcello Marques
                              Santos - SP - Brazil

                              1 Reply Last reply Reply Quote 1
                              • C Offline
                                cellobita
                                last edited by

                                PS: I do fervently hope, since this is most likely the exact same issue as on the Plus version, that Netgate issues an emergency patch/version ASAP (2.5.1-p1 or something...)

                                Marcello Marques
                                Santos - SP - Brazil

                                1 Reply Last reply Reply Quote 0
                                • V Offline
                                  vjizzle
                                  last edited by

                                  Ok maybe unrelated but my pfSense suddenly stopped NAT-ing new sessions. For example my Citrix session to work was running fine but when I tried opening websites for the first time today I was not able to open them. DNS was resolving them fine. Restarting Unbound did not solve it. I had to reboot the firewall to make everything work again. Tonight I am definitely going back to 2.5 :(

                                  C 1 Reply Last reply Reply Quote 0
                                  • C Offline
                                    cellobita @vjizzle
                                    last edited by

                                    @vjizzle Good luck.

                                    I'm not the kind of consumer that Netgate wants or needs, as of 2021, so they couldn't care less about what follows, but anyway:

                                    This is the first time in over ten years - since switching all my customers from IPCop - that I'm looking closely at the alternatives for pfSense. Sad.

                                    Marcello Marques
                                    Santos - SP - Brazil

                                    D 1 Reply Last reply Reply Quote 5
                                    • D Offline
                                      Dredex @cellobita
                                      last edited by

                                      Forgot to backup on 2.5.0 and I'm stuck on 2.5.1 with this problem...
                                      I hope on a workaround until they release a fix.

                                      QinnQ 1 Reply Last reply Reply Quote 0
                                      • QinnQ Offline
                                        Qinn @Dredex
                                        last edited by Qinn

                                        @dredex If it is that important you could download 2.5.0 from
                                        https://atxfiles.pfsense.org/mirror/downloads/

                                        or

                                        https://nyifiles.pfsense.org/mirror/downloads/ Before installing I would

                                        check the hashes https://nyifiles.pfsense.org/mirror/downloads/ or find
                                        some University site that has them of course all on you own risk.

                                        Hardeware: Intel(R) Celeron(R) J4125 CPU @ 2.00GHz 102 GB mSATA SSD (ZFS)
                                        Firmware: Latest-stable-pfSense CE (amd64)
                                        Packages: pfBlockerNG devel-beta (beta tester) - Avahi - Notes - Ntopng - PIMD/udpbroadcastrelay - Service Watchdog - System Patches

                                        D 1 Reply Last reply Reply Quote 1
                                        • D Offline
                                          Dredex @Qinn
                                          last edited by

                                          @qinn Thanks but I don't have a backup config from 2.5.0

                                          1 Reply Last reply Reply Quote 0
                                          • QinnQ Offline
                                            Qinn
                                            last edited by

                                            You can use the current config from 2.5.1 never had trouble using a config file among versions.

                                            Hardeware: Intel(R) Celeron(R) J4125 CPU @ 2.00GHz 102 GB mSATA SSD (ZFS)
                                            Firmware: Latest-stable-pfSense CE (amd64)
                                            Packages: pfBlockerNG devel-beta (beta tester) - Avahi - Notes - Ntopng - PIMD/udpbroadcastrelay - Service Watchdog - System Patches

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