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.
    • M Offline
      MoonKnight @vjizzle
      last edited by

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

      @ciscox
      Hi! Your post triggered me to check if my port forwards my VPN clients were working and they are not :(. Reconnecting the VPN's and even rebooting pfSense does not fix this. Looks like port forwarding on OpenVPN interfaces is broken.

      I will try and do more testing later on. WFH so I can't break the internet for now.

      Hi, thanks for checking this up. :)

      --- 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)

      YanikY 1 Reply Last reply Reply Quote 0
      • D Offline
        Dredex @gkovachev
        last edited by Dredex

        After upgrading to 2.5.1 non default WAN is not working...
        Worked fine in 2.5.0

        1 Reply Last reply Reply Quote 0
        • fireodoF Offline
          fireodo @Bismarck
          last edited by

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

          Excellent! 😰

          Root mount waiting for: CAM
          Root mount waiting for: CAM
          Root mount waiting for: CAM
          Root mount waiting for: CAM
          Root mount waiting for: CAM
          Root mount waiting for: CAM
          Root mount waiting for: CAM
          

          I got these in dmesg too on boot since update to 2.5.0 and present in 2.5.1 too - should I worry?

          Regards,
          fireodo

          Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
          SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
          pfsense 2.8.0 CE
          Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

          BismarckB 1 Reply Last reply Reply Quote 0
          • BismarckB Offline
            Bismarck @fireodo
            last edited by

            @fireodo Only when it's stuck with this message, like in my case where I couldn't boot anymore.

            After a fresh install and config.xml recovery, the system booted again but the messages "Root mount waiting for: CAM" still apears aprox 4 - 5 times.

            dmesg | grep CAM
            Root mount waiting for: CAM usbus0 usbus1 usbus2
            Root mount waiting for: CAM usbus0 usbus1 usbus2
            Root mount waiting for: CAM usbus0 usbus2
            Root mount waiting for: CAM usbus2
            Root mount waiting for: CAM usbus2
            Root mount waiting for: CAM
            Root mount waiting for: CAM
            Root mount waiting for: CAM
            Root mount waiting for: CAM
            
            fireodoF V 2 Replies Last reply Reply Quote 0
            • fireodoF Offline
              fireodo @Bismarck
              last edited by

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

              @fireodo Only when it's stuck with this message, like in my case where I couldn't boot anymore.

              Thanks, it don't stuck here. I got that 5 times in dmesg with my SSD and after changing to HDD it comes also 5 times ... but boot is not affected.

              Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
              SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
              pfsense 2.8.0 CE
              Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

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

                After 2.5.1 my port forwards are not working.
                They were fine at 2.4.5 and 2.5.0.

                V C TAC57T 3 Replies Last reply Reply Quote 4
                • V Offline
                  vjizzle @Bismarck
                  last edited by

                  @bismarck Same here. I can see the same CAM messages but system boots fine.

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

                    @yanik Do you mean port forward on OpenVPN interfaces? That is what I am experiencing.

                    Port forwards on WAN seems to work fine here.

                    YanikY D 2 Replies Last reply Reply Quote 0
                    • 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
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.