Update: It looks like a firmware update for the adapters may fix this problem.

So it's been about 6 weeks since anything happened and we had a crash today. Just replying to add 2 pieces of information in case anyone comes across this post in the future. Today we rebooted the VM host for the first time in 8 weeks after pushing some Microsoft updates. Second, I tried to reboot from shell and it hung on stopping ntopng. I think the reboot is anecdotal/coincidental.

@SteveITS I just read them more carefully now, thanks!
That leaves node exporter then.

@stephenw10 Factory reset modem seems to have cleared up the link issue. ISP claims nightly outage is scheduled service

Hmm, well if that is the case you might be able to set the NIC to just link at 1G only and be able to remove the switch.

Yup AFAIK it only affected that one card.

Nice. Yes 32 decimal is 0x20 in hex so 5G only.

@tomasenskede

Root cause identified and resolved!

The issue was related to the Digitus Media converter, which didn't support mixed speeds. I had a 10 Gbps connection on one side and a 2.5 Gbps connection on the WAN side of pfSense.

However, after replacing the media converter with a switch that had both 10 Gbps and 2.5 Gbps ports, the collisions and errors ceased.

Case closed, and now my WAN data flows without any errors!

Can you QOS the backup traffic?
Can you force the backup through a port set to a lower speed?

@jmcmillen It shouldn't do anything :) but per other posts some people say it solves link negotiation issues, or issues where the ISP router reboots and pfSense sees the NIC disconnect/reconnect and restarts packages.

I'd try another patch just to rule it out. I know it doesn't always make sense but...

@invoker Also: https://www.netgate.com/training/pfsense-fundamentals-and-advanced-application

Screenshot 2023-10-04 at 6.34.52 PM.png

2100-SG no go

:(

I assume 192.168.20.1 is the pfSense LAN IP? It would only send an ARP request for 1.1.1.1 there if it thinks it has an IP in the same subnet as that. So at least when it was sending that ARP request it must have had a bad route present somehow.

The interrupts are expected and shouldn't be a huge issue at that rate. You could just be seeing some saturation. Check Status > Monitoring for the traffic on WAN and LAN. Is it hitting the available bandwidth?
You may need some shaping prioritise remote desktop.

Steve

@darkcorner said in pfsense 2.7 menu stuck with NUT crash:

I wouldn't even know where to configure console protection with a password. So the answer is, no, there shouldn't be.

It's a checkbox in System / Advanced / Admin Access.

Screenshot 2023-10-03 at 07.56.17.png

It's quite likely something you set and didn't think too much about at the time. It's in a bunch of pfSense HowTos.

@michmoor said in Simple question about KEA DHCP:

@jimp Based on notes in the ticket is it expected to arrive for 23.09?

That's the plan, but as stated there it is working for IPv4 and not IPv6, so it may not be 100% in 23.09. Keep an eye on the Redmine to know for sure.

@Cabledude TAC ticket opened.

@Gertjan Thank you.

The requirements are Port 587, Auth method is Plain, with STARTTLS

@SteveITS I've just tried it again, without Enable SMTP over SSL/TLS or Validate the SSL/TLS certificate presented by the server enabled, and it worked...

I thought I'd tried that earlier and it failed, not sure what I've tried now, been messing about with it for so long :)

But thanks everyone, all good now.