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.
    • bmeeksB Offline
      bmeeks @SteveITS
      last edited by

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

      The PHP core dump on SG-3100 with some packages is not listed as a known issue but presumably still exists...

      If you use one of the three packages known to be impacted by that bug (Suricata, Snort or pfBlockerNG-devel), and having one or more of those packages running is critical for you, I would suggest not updating yet. To the best of my knowledge no work has been done on the PHP crashing issue on ARM 32-bit hardware.

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

        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
        

        2.5.1 wippend out my root partition, recovering right now...

        /edit

        Back to normal operation again, now 2.5.1 runs here fast and smooth as well. 🤓

        fireodoF 1 Reply Last reply Reply Quote 0
        • S Offline
          swampkracker
          last edited by

          Flawless upgrade from 2.5.0 to 2.5.1. Everything is working as it should.

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

            Upgrade went smooth on my pfsense CE. I am running several VPN clients tunnels with routing groups and so far all is working well.

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

              Smooth update to pfSense 2.5.1 CE

              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

              1 Reply Last reply Reply Quote 0
              • P Offline
                pietsnot56
                last edited by

                Smooth update on J3160 system.
                Only I can not start up iperf.
                why?

                provelsP 1 Reply Last reply Reply Quote 0
                • provelsP Offline
                  provels @pietsnot56
                  last edited by provels

                  @pietsnot56
                  Same here, but a quick reinstall fixed it.

                  EDIT - Whoops, stopped.

                  EDIT, EDIT... Rolled back to 2.5.0, iperf still doesn't start. So there's that... 🤷

                  Peder

                  MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
                  BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

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

                    I just updated to 2.5.1.
                    Some issues here. I have a Plex Server running on another computer. I have VPN running on that one with port-forward and policy routing. The port-forward doesn't work anymore. But the computer can still access Internet with the VPN.
                    But the only thing that doesn't work is the port-forward :(

                    Another issue is the DNS Resolver. After reboot of the firewall, i don't have access to internet. Only the computers that have static IP on the interface. I cant access any device using the dns. I have to restart unbound. After that i can access computers with the dns.

                    The DNS problems was on version 2.5.0 also but not the port-forward problem.
                    The DNS problems seems to appear when i have multiple VPN Client running. It could be some bad configuration from my side, but it has always worked on version 2.4.5. It starts on version 2.5.0.

                    So, i'm planing to move back to 2.5.0 or even 2.4.5p1 (not sure when)
                    To bad i can't run my Plex Server anymore with VPN and port-forward(so my plex server is online and accessible outside my network)

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

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

                      @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.

                      M 1 Reply Last reply Reply Quote 1
                      • 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
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.