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.
    • W Offline
      Waqar.UK @chudak
      last edited by

      @chudak

      Well, I might re-install Pfblocker and Suricata over the weekend.
      But keeping it simple just works.

      chudakC 1 Reply Last reply Reply Quote 0
      • chudakC Offline
        chudak @Waqar.UK
        last edited by

        @waqar-uk said in To 2.5.1 or not ? that is the question :):

        @chudak

        Well, I might re-install Pfblocker and Suricata over the weekend.
        But keeping it simple just works.

        pfBlockerNG was giving me a lot of grief lately and reinstall did not help, hope for next point update.

        W 1 Reply Last reply Reply Quote 0
        • W Offline
          Waqar.UK @chudak
          last edited by

          @chudak

          Yes I agree!!

          I luckily put a tick box where "do not keep settings on un-install".
          So all previous un modified by add on packages raw Pfsense is all I will use for the next few days.

          chudakC 1 Reply Last reply Reply Quote 0
          • chudakC Offline
            chudak @Waqar.UK
            last edited by

            @waqar-uk

            I do the same, but kinda counter-playing now to do a fresh pfBlockerNG install, still don't have guts to wipe out all old settings

            S 1 Reply Last reply Reply Quote 0
            • S Offline
              SteveITS Rebel Alliance @chudak
              last edited by SteveITS

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

              Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
              When upgrading, allow 10-15 minutes to reboot, or more depending on packages, and device or disk speed.
              Upvote ๐Ÿ‘ helpful posts!

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

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

                Was encouraged buy quick feedback and went for it too :)

                My updated was fast and smooth.

                But I still see a minor unbound oddness, when after reboot DNS did not seem to be resolving well, even tho no apparent error and service shows as green. Unbound restart fixed this.

                I notice the same on version 2.5.0. I haven't upgrade to 2.5.1 yet. But I use Watchdog now, so it helps after a reboot most of the time :)

                --- 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
                • G Offline
                  gkovachev
                  last edited by

                  My setup is 2x WANs, 1x LAN. After upgrade from 2.5 to 2.5.1 port forwarding stoped working on non default WAN2.
                  The strange thing is that in 2.5 in my setup, port forwardings on both WANs were working just fine.

                  In 21.02.2/2.5.1 New Features and Changes there is a fix:
                  Fixed: State matching problem with reponses to packets arriving on non-default WANs #11436
                  which in my case did the opposite :) Broke working setup.

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