@patient0 Thank you very very much. Cheers

Well there have been numerous beta builds since then.

There are a lot of key changes in the 25.03(7) backend and we need to make it as close to bug free as possible.

I expect to see the next release in July. But that still depends on new bugs etc. There's no point releasing anything before it's ready. 😉

@stephenw10 who knows... thanks again! I was going crazy for two weeks now until I decided to reach out to this forum! i was asking coworkers and people on mastodon but all i needed to do in the end was arp-scan and see that there was a conflict with two macs on the same IP. Saddly I cannot upvote you because of my low reputation.

For future readers please give stephenw10 an upvote for me <3

Hmm, first I've heard of it. Though it's unlikely to be overwritten since it's a custom directory, no update tries to write there.

I usually out custom scripts like that in /root.

Add to what is said above,
The "swap off" will disable swap usage, see it as a flag information to the kernel.
Not like "Windows", FreeBSD (the nix systems) use a dedicated swap partition, so you cant' see it, use it , or do something else with it.
The "swap off" command just tells the kernel to start OOM processes as soon as there is not enough free RAM anymore, A process is elected to be 'terminated', using a selection criteria somewhat better as 'Russian roulette', but the result will be the same as nearly all processes are essential to the system : things will go downhill fast.
On pfSense, the process with loads of RAM (the DNS cache) is often unbound, so unbound is asked to leave, leaving you without DNS (and unbound gets yelled at again ...).

If "swap" gets used on a pfSense system, you can interpret this as a pretty solid confirmation that your system is 'to small' for the tasks you asked it to do. The solution has been identified, it's " add more RAM " .....

"swapon -a" is actually that little extra safely net, that can do the little extra more for you when needed, and its warns you that you'll need to buy more DIMMs

Urgh, yeah that's not good. It's difficult to break ZFS just by removing the power. So, yes, could be a bad drive.

Interesting. I suspect that might have been a coincidence. But, as I say, adding static ARP can make troubleshooting more difficult. If a MAC is typo'd things just fail silently.

Yeah I'd guess it's random errors in the link occasionally corrupting a UDP packet. It depends what rate you're actually seeing but I probably wouldn't be worried if it's not continuous.

@stephenw10 ok I got to solve the problem changing my source of the route table URD from 0.0.0.0/0 to my subnet from my spoke subscription 10.20.0.0 from that is working the test vm with internet. now I will test performance to connect a cluster ks8 from each spoke. thanks for the support .
9cae0646-7797-4c9f-bf54-d0af9349fbdb-image.png

@phloggu said in pfSense 2.8: WebGUI unusable (due to cat and tail many logfiles in the background):

The widget shows 10 lines, I had 99 logfiles at a size of 80MB each, non-compressed,

The log files are 'PHP' parsed ... PHP is a 'one-core' process, great for building web pages, extremely bad when it has to deal with 'huge' text files. It will takes 'ages' - and / or usage all PHP memory (512 Mbytes max).

If you really want to store/keep/use big log files : use a remote syslogger. Then you can go wild wild huge files with your firewall being impacted because you clicked 'one something' or just logged in.

@stephenw10 doh

Thanks again mate - try this asap.

@stephenw10 I will give it a try, and give a feedback after.

It seems this was partially fixed with 2.8.0 in that current speed does change and reports some real-looking values. The max frequency is still wrong though.

But anyway you can see if tailscale is running in Status > Services.

@JimS FYI, Possibly related, I am mentioning this in case someone has the issue. After a modem replacement I had to power cycle pfsense 2.6.2 after a power failure.
I am now on 2.7.2 but have not had a power outage since so don't know if it's fixed. Could be modem timing mentioned above. In my case I could not access anything on pfsense.

I posted this March 2025:
The recent S33 modem failure and change to S34 caused pfsense 2.6 not to come back up after a power failure (3 this month so far!)I hope pfsense 2.7.2 can recover from a power failure like 2.6 did with the old modem.

2.6 always recovered until the modem change, strange but true. Trying to login to pfsense 2.6 returned the dreaded "502 Bad Gateway Nginx error". Had to power off/on. Waiting to see what happens to 2.7.2. I'm thinking possible ethernet driver issue with a different chip in the S34 than the S33, which may be fixed in 2.7.2

Ah, good result!

Also verify the server is actually resolving against pfSense and doesn't have some hard coded DNS built in.

Yup that also works:

[2.8.0-RELEASE][admin@m370.stevew.lan]/root: pppcfg pppoe0 dev: lagg0 state: session sid: 0x12 PADI retries: 0 PADR retries: 0 time: 00:00:21 sppp: phase network authproto auto authname "Test" peerproto auto [2.8.0-RELEASE][admin@m370.stevew.lan]/root: /usr/local/sbin/pfSctl -c 'interface reload opt2' OK [2.8.0-RELEASE][admin@m370.stevew.lan]/root: pppcfg pppoe0 dev: lagg0 state: session sid: 0x7 PADI retries: 0 PADR retries: 0 time: 00:00:01 sppp: phase network authproto auto authname "Test" peerproto auto

We use lots of different 10G SFP+ at work. They do certainly vary, but rarely have over heating issues as long as they are in a high end switch/router such as Juniper, Cisco, etc.

We did have quite bad over-heating issues in a TP-Link SX3008 switch. The problem was the SFP cages, so we modified the switch adding cheap self-adhesive heatsinks. Attached pictures show the main board before & after. Approx 20degC SFP temperature reduction.

2022-08-12 13.59.18 TP-Link.jpg 2022-08-13 17.32.41 TP-Link.jpg