@Gertjan okay, I will try to re run the test with multicore. Otherwise I am considering switching to a official netgate device and keep the protectli as a backup if the netgate device fails someday.

@stephenw10 Thank you...I have opened a ticket.

Depends on what you are trying to do. Mudwap supports pfSense CE only.

If it's something in pfSense it will almost certainly be logging something when the problem starts. It could be a link state change. But it could be a route or IP address change. Or if you're running something dynamic like Snort or pfBlocker it might be related to a list update for example.

@stephenw10 ok, thanks. I will try to set it up that way.

@stephenw10 I bought a pack with cameras and the NVR and as the NVRcould also provide PoE as well as the switches I set it up that way, so you’re right there is little to no benefit to adding the extra switch. In fact, it would be more beneficial to replace the oddball camera and add its replacement to the NVR!

@stephenw10 Awesome thanks!

@johnpoz said in speedtest-cli 403 forbidden error: Not exactly sure what --secure option does. speedtest-cli --help and you'll find out what it does :-) --secure Use HTTPS instead of HTTP when communicating with speedtest.net operated servers Nice weekend, fireodo

@pwood999 said in 10GB Fiber network, yes/no?: @chudak Out of curiosity what speed are you actually seeing on the 10G connection. If it's standard XGS-PON, that usually maxes out around 8.5Gbps data payload due to overheads in the PON system. If the ISP is using 25Gb PON, then they could theoretically deliver 10Gb data rates. I don't have 10GB fibber yet :) On 1GB I see ~700MBps on iPhone 13 Pro and full 1GB on wired connections

@mark77ap Wow, the cable? Well, I tried two different 6 foot CAT6 cables (one unknown brand and another Amazon basics). Both were UTP (unshielded). Maybe I'll have to try some other cable brands, or different types of cables like CAT6e or CAT7 or even some STP (shielded) cables. I'll have to swing by my work and "borrow" a few to test with I'm glad you were able to solve your dropouts with just a cable, that's great news! I hope I have the same luck!

Indeed we have seen a few reports of that but have never seen it here. If it happens again and anything is logged at that point or, even better, if you can find a way to replicate it please let us know. There have been similar issues in the past but not for quite a while.

The key line there is that the boot drive, ada0, detaches from the drive controller. That obviously stops it booting. That looks like a drive or controller failure. It could be something as simple as a bad SATA cable though.

First of all thank you for your reply @stephenw10 ! Ok - this was an odd one. We had a firewall alias for testing purposes to block updates to the ACB service. And yes - there way a typo ;-)

@stephenw10 [image: 1697051073163-3d8c8716-912f-47d5-b8da-df2548987dde-image.png]

It's this: https://redmine.pfsense.org/issues/14648 Try checking those sysctls directly. Steve

@stephenw10 Thanks got it!

If you are creating multiple rules for different ttl lengths remember to increment the sid: value for each rule.

A fresh install is always at the factory defaults anyway (unless you did a config recover during install?) so it would make no difference. Go ahead and restore your config and you should be good. The OK> prompt implies it wasn't able to get past the bootloader. And that is most commonly caused by something nuking the entire partition. Without more logs though it's hard to say what that might have been. Steve

@stephenw10 said in WOL Doesnt Seem To Be Working: Ethereal Your dating yourself with that name ;) hehehe