Ah, yes. Been a while I guess.

@stephenw10 said in [ Bug? ] 24.11 web GUI cannot enable L2TP server ( while the service is just working fine in the background ): 3487972e11dc8d096f97c2a2e5a0e86d7f179002 Hi, Thank you. Had fix it.

@stephenw10 I reported it as (possible) spam (category 'other) yesterday.

@Gblenn said in CPU pegged at 100%: I have seen a lot of complaints about 24.11 consuming a lot of CPU resources for some reason? CPU Usage - pfSense 24.11 on a 4100. edit : true, I didn't activate every bell and whistle and I'm more a log watcher guy, the dashboard isn't my thing.

@Gertjan ok thanks. I'll continue to update via my spare ssd. Not had any issues so far with previous updates. Just for clarity it's an on board x710 sfp port rather than a card.

The basic transparent setup mode should work for you, the first thing to check is that your status LED is solid white. https://www.quantumfiber.com/support/equipment/user-guides/c5500xk-smartnid.html The pfSense Wan interface is plain IPv4 DHCP: [image: 1735095744042-47870cfc-d952-42e3-89ad-82cf02c29f47-image.png] Centurylink and Quantum (at least) don't offer IPv6 connections in most areas. They do offer a very poor 6RD option to get v6 over the v4 connection.

Mmm, I'd be amazed if your ISP was using anything other than 1500.

@jra9511 said in Common rules for various interfaces in Suricata with Pfsense: When I use the suricata-update command in the console, it generates a file called suricata.rules located in var/lib/suricata, Forget everything you might have read about using Suricata via the command line when using the pfSense package. The Suricata package on pfSense is managed totally within the GUI. Do absolutely nothing via the command line. The pfSense package is highly customized and you do not use any of the Suricata upstream supplied tools with it -- that includes suricata-update. As you discovered, that utility puts the rules in the wrong location for use in pfSense. Here is a YouTube video from Lawrence Systems showing how to install and administer the Suricata package on pfSense: https://www.youtube.com/watch?app=desktop&v=S0-vsjhPDN0.

Yes, the next release will be 25.03.

@patient0 The swap journey with the correct use of labels resulted it it working as soon as I moved it to the mpcie adapter again I think I need nvmecontrol commands to format it again so I can get to the Optane memory. I have no clue how to do that, I use to use fdisk in dos 3.11 so using something outside of gpart or fdisk etc. is very new to me, I assume that the nvmecontrol has format specific commands to use to get access to the Optane memory but who knows right, fun stuff I love stuff like this, I was thinking Intel might also have a label that is specific to using the Optane for a swap, pfsense I learned has the use of swapX X=some number and the software uses it, so maybe if I use a label the Optane controller will pick it up and use it. [image: 1734970280521-screenshot-2024-12-23-at-08.11.13-resized.png]

@Gblenn Thank you That’s great advice Merry (or Happy) Christmas or Happy Holidays

Thank you, I’ll give it a try and find out.

@mer it’s on a external drive so if someone grabs it and takes it my credit card etc is not on the drive as it’s encrypted non readable. Again it’s not internally stored, FreeBSD forum recommendation was to use Eli for external usb swaps as they can be grabbed and walk off.

TIL about the System Patches package and path strips. Thanks for your help @stephenw10 . We're back in business.

My reboot issue on 24.11 has NOT been resolved! So 24.11 is unusable to me :( Netgat TAC support guys suggested it's an h/w issue and offered to wipe out my drive and try to install it clean. I tried uninstalling a bunch of packaging and it did not help. I am hesitant to wipe out my drive as I will lose my boot env snapshots. Just posting here for posterity.

@Gertjan So I used both tcpdump and radsniff to look at packet traces, but I can't see any issues. In both cases (working and non-working) the radius server sends back an Access-Accept message with the same set of fields.

@stephenw10 - Excellent! Patch worked. Glad I wasn't imagining things.

Our solution at this point : Automatically : Remove unwanted boot environnements Update the train to the stable version Check upgrade availability (pfSense-upgrade -d -c) Prefetch all packages (pkg fetch -u -d -y) So we want finally launch the upgrade (pfSense-upgrade -4 -d -y) it's faster !

@JonathanLee said in issues with dumpdev in /etc/defaults/rc.conf: sysctl debug.kdb.panic=1 [image: 1734643581954-b9160abf-7a3b-47d4-a8c5-0ace4dae0fe1-image.png] Custom solution add the cron copy the rc.dumpon to rc.dumpon.old add the new info and it works