Hi, Unfortunately the problem seems to still occur. Although a lot less, I noticed something though``` em1: <intel(r) 1000="" pro="" network="" connection="" 7.6.1-k=""> port 0xe000-0xe01f mem 0xff840000-0xff85ffff,0xff820000-0xff83ffff irq 17 at device 0.1 on pci1 em1: Using an MSI interrupt em1: Ethernet address: 00:1b:78:5c:4f:99 em1: netmap queues/slots: TX 1/1024, RX 1/1024 vgapci0: <vga-compatible display=""> port 0xf140-0xf147 mem 0xff900000-0xff97ffff,0xd0000000-0xdfffffff,0xff600000-0xff6fffff irq 16 at device 2.0 on pci0 agp0: <intel g33="" svga="" controller=""> on vgapci0 agp0: aperture size is 256M, detected 7164k stolen memory vgapci0: Boot video device pcib2: <acpi pci-pci="" bridge=""> irq 16 at device 28.0 on pci0 pcib2: [GIANT-LOCKED] pcib3: <acpi pci-pci="" bridge=""> irq 17 at device 28.1 on pci0 pcib3: [GIANT-LOCKED] pci2: <acpi pci="" bus=""> on pcib3 re0: <realtek 8111="" 8168="" b="" c="" cp="" d="" dp="" e="" f="" g="" pcie="" gigabit="" ethernet=""> port 0xd000-0xd0ff mem 0xff720000-0xff720fff irq 17 at device 0.0 on pci2</realtek></acpi></acpi></acpi></intel></vga-compatible></intel(r)> Both NIC's look like they've got IRQ 17? Could this be it?

"10.10.0.0/16 does the job after all." Does the job of what - a firewall rule?  A summary route - those are really the only valid uses of such a CIDR.. Do you have 65k some hosts you need on the same network? ;) Use a more appropriate CIDR would be my suggestion.. Say a /24 or /23 if you have a lot of hosts..

You can have two dhcp pools but you cannot tell this client should select from pool A and this client should select from pool B. So all the clients you want to be in pool B give them fixed ip. But remember if any other client which was suppose to get dhcp address from Pool A, fix his ip to pool B then he'll be allowed. So to avoid this you should either use Managed switch or go for vlan. If you have all wireless devices, then setting up vlans is quite simple. Only thing then required will be device which can tag the clients. Most of the APs now a days come vlan tagging facility. If you have desktops then you have to invest in managed switch. I can help you setup vlans, incase you decide to do so.

They are stored in the xml… You could do a backup, and then pull them out and then reload them on a new system via edit of xml and restore.  I do not see a specific for just backup of them..  But with a bit of manipulation you could do it that way.. How many do you have to move?  You can also just export them in the cert manager and then import them into your new system.  That is how I did the few certs I wanted to move over from my old system when I got my sg4860.. I wanted to save my CA since had certs deployed that it had signed, etc. [image: certs-cas.png] [image: certs-cas.png_thumb]

Hi, Enter console mode. Option 8. Enter : ls -al /usr/local/sbin/ntpd You should see : -r-xr-xr-x  1 root  wheel  692424 Oct  9 00:12 /usr/local/sbin/ntpd This program, the time deamon, is part of a basic FreeBSD/pfSense setup. It isn't possible that it isn't there. I really advise you to do a clean install. True, the "Watchdog"  isn't very smart neither, trying to (re) start a program that isn't there. Not being able to check for updates could be the proof of other missing system files - or just a broken DNS setup. Don't spend more time, wipe it clean ;)

Hi, What are you captive portal settings ? What is the captive portal status pages showing ? What does the captive portal log tels us ?

I would do a clean install and then restore from your backup.

Hi, The device you use to connect to pfSEnse, did it get an IP from the DHCP server running on pfSense ?

Linux normally uses PMTUD to set packet size.  Do you see the ICMP "too big" messages?  I'm not sure about IPSec settings, as I haven't used IPSec with pfSense.  The MSS is normally used when setting up a TCP connection to tell the other end the maximum supported packet size.  It has nothing to do with any router, including pfSense.  It is PMTUD that's used to determine the maximum packet size that will fit the smallest MTU along the path.

Thanks!  I use to run this, but had yet to get it moved over to the sg-4860 once I switched to that from my vm setup. The summary emails from dshield were nice to get.  I will have set this back up soon.

@kpa: If there is a switch in between pfSense and modem then the only link state changes pfSense is going to see are the ones with the switch. Thanks. Just talked to the ISP, it seems it's actually the gateway router. They are going to replace it.

So was going to swap the firewall out today so I could bench it and test and figure out what was going on and as soon as I fired up the temp firewall, exact same model and case but version 1.1a BIOS, it did the same thing. So I suspected it was likely being caused by something plugged in and since the only thing plugged in was the Tripplite battery backup, I unplugged it, restarted it a few times and it never hung with the error until I plugged the UPS back in. So, in short the kernel is handing on the UPS during boot. Should I report this as a bug? It has to be a FreeBSD kernel bug. I plan to work around it by changing the UPS from USB to serial. The only other issue I was running into was "AutoConfigBackup service started" would seemingly hang forever. Not always, but periodically.