I did sort of almost spit out my drink when I noticed you using a code base thats no longer supported. I can confirm on 2.4 TLS 1.2 is used. So update the pfsense to a newer code base and your problem is solved.

"Using https and an IP, that's just NOT possible - not logic - it's counter productive …" Huh???  An IP is no different than FQDN, you can for sure put IP as SAN in your cert so you do not get any warning.. Notice my pretty green icon, and hitting it via IP.. Notice the SAN have 2 different IPs in them and another fqdn for another interface - so I can hit it with that name or that IP and still trust the cert.. [image: SANinCert.png] [image: SANinCert.png_thumb]

Hardware event. This is not a software error. CPU 0 4 northbridge   Northbridge Watchdog error       bit57 = processor context corrupt       bit61 = error uncorrected   bus error 'generic participation, request timed out             generic error mem transaction             generic access, level generic' STATUS b200000000070f0f MCGSTATUS 4 MCGCAP 105 APICID 0 SOCKETID 0 CPUID Vendor AMD Family 15 Model 47 Nothing there sounds good, it also doesn't point to any one specific thing. Given that seems to be a >10yr old CPU, it's probably time to consider a replacement box. AMD 0F 2F K8 (rev.E)   Athlon 64  Sempron

Flixed in the latest snapshot. Thanks Luiz.

Glad to assist in finding bugs, it still sets the LAN IP though, just a little annoyance pop-up. :)

I'm stupid :D The problem is on port 3000 (Ntopng)  :D Thanks a lot Stefano

@pan_2: Hope it will be added to package. This is a wrong place to submit patches you want included. Need to go to GitHub as pull request: https://github.com/pfsense/FreeBSD-ports/tree/devel/net/pfSense-pkg-Quagga_OSPF https://www.pfsense.org/about-pfsense/#cla

You can also do stuff when it joins a specific wifi network.. So for example when you get home and your phone joins your network, the IFTTT app could do something that turns off your camera, etc. There are always multiple ways to skin the cat ;)  Sometimes people get 1 method in their heads and get stuck doing it only that way.. Which is why its always a good idea to give the details of what your actually trying to accomplish as the end goal, so that other methods of skinning that cat can be explored..

Move captive portal authentication to a RADIUS server and grant your privileged user access to create accounts in RADIUS.

PHP should eventually timeout when it hits the max execution time (~15 mins) But that said, it's a classic case of "Doctor, it huts when I do this" / "Don't do that". Don't do that.

oh my, yes, you are right: I had forgotten a recent port-forwarding. SOLVED for me. sorry for the noise  ::)

Thanks, restored config. Back in business!

Not really.  Status - Queues is about the best you can do, also Diagnostics - pfTop - Queues view.  If your shaper rules are not behaving as you expect, post them in the Traffic Shaping forum and someone will have a look.

Thanks, that did it.

Thanks Virgilio, that does actually make sense. I run into this most often when setting up DHCP reservations and I want to remove the old dynamically assigned entry.  But the extra safety does make sense.