PfSense boot hangs at "starting captive portal" for quite some time
-
This pfSense installation has been working great for 4 years or so, and is still working great. The firewall stays up for quite some time and rarely reboots, but when I do need to reboot it, I notice that on the console boot screen it shows "Starting captive portal" for quite some time. Everything else is very fast to start services, but Captive Portal takes a good 10-15 minutes to start up. If I'm watching the hard drive activity light, it's not working very hard, but blinking at a steady beat every .5 to .75 of a second or so.
There's 2 wireless networks on this network; one internal network simply using WPA2 with a PSK on one VLAN, and an open network on another VLAN using pfSense's Captive Portal. The only thing I'm suspicious of is on the Captive Portal VLAN, I have pfSense set to save the MAC addresses of anyone who's accepted the terms of use page, so they don't need to accept more than once on a device. The MAC addresses don't expire, and they've never been cleared. There's less than 1000 of them in the list, I'd assume.
Just wanted to see if this was normal or not for it to take this long. Thanks in advance for any insight!
-
….
Just wanted to see if this was normal or not for it to take this long. Thanks in advance for any insight!What about saving your config first, and then you empty that list.
Reboot.
Check if this related to the boot time.
Then re - import config. -
What about saving your config first, and then you empty that list.
Reboot.
Check if this related to the boot time.
Then re - import config.That's an idea, yes. But I'd like to avoid doing that. I'm moreso just curious what it's doing during this time, if it's normal, and if a newer version of pfSense still takes as long to start Captive Portal.
