pfSense Plus and SG-3100
-
No, it's a real fix. See: https://reviews.freebsd.org/D28821
-
@stephenw10 said in pfSense Plus and SG-3100:
https://reviews.freebsd.org/D28821
i guess i'm just a little confused then. Is the fix going to degrade performance if we're limiting the hardware cpu cores? Do we need to reapproach our load on a 3100 with these changes?
-
No, the temporary workaround was to disable one CPU core. That is not required with the fix that is now in 21.02p1.
Steve
-
@stephenw10 Do we remove that line from the config before or after applying the patch? Want the update to go as flawless as possible.
-
@flsnowbird said in pfSense Plus and SG-3100:
@stephenw10 Do we remove that line from the config before or after applying the patch? Want the update to go as flawless as possible.
I did it before
Then did the update, then rebooted the firewall so the limitation were not in place -
Yes, you could do either but you will need to reboot after removing it since that is applied as a loader variable at boot.
Steve
-
@stephenw10 It would be nice if you could explain in any detail what the problem is/was. I just purchased an SG3100 and I got no emailed warning about any potential issue either (would be nice really).
That said I answered the upgrade survey not knowing all that was meant by the upgrade to pfsense+. If you're going to make a really good firewall product in terms of control panel / GUI and work process you should get your hands on Microsoft's ISA firewall from some time ago. I don't know why the product disappeared but it was the best gateway/firewall/router I've ever used. I looked for a reasonable replacement and found pfsense to be the next best thing but you guys still don't measure up to something from 15 or so years ago. ;0)
Now that you're on a serious commercial product path that is what I'd look from you guys.
-
@fg said in pfSense Plus and SG-3100:
explain in any detail what the problem is/was
https://www.netgate.com/blog/pfsense-obscure-bugs-and-code-wizards.html
-
@teamits Wonderful blog explanation. Been a long time since I debugged code, and I enjoyed the description of the "hunt." Kudos to the Netgate team for a superb job.
-
This same bug was in 2.5 DEVEL and I reported it to support, but was only told to revert to 2.4 stable. I guess I was just too exited about wireguard. Next big upgrade I'm waiting a few weeks before jumping on it.
