Enabling https FORWARDS on captive portal KILLS the CPUs on all my pfSense boxe
-
Until recently, I had NOT enabled the https forwarding. I finally had a reason to do so. I turned it on this morning on 2.3.2 and was unhappy to see that my CPU went from less than 10% to 100% in 3 hours. Rebooting only helped things briefly then it started to climb. As soon as I disabled the https forwarding all was well. Anyone else seen this?
-
Until recently, I had NOT enabled the https forwarding. I finally had a reason to do so. I turned it on this morning on 2.3.2 and was unhappy to see that my CPU went from less than 10% to 100% in 3 hours. Rebooting only helped things briefly then it started to climb. As soon as I disabled the https forwarding all was well. Anyone else seen this?
Mine isn't checked.
HTTPS Forwards | | Disable HTTPS Forwards
If this option is set, attempts to connect …is not checked
So, it is enabled.My CPU activity is low or normal https://www.test-domaine.fr/munin/brit-hotel-fumel.net/pfsense.brit-hotel-fumel.net/cpu.html
Captive portal users https://www.test-domaine.fr/munin/portalusers-day.html -
There may be a client on the network that is really, really unhappy about being forwarded and keeps trying repeatedly.
-
No. Not it. Because I have 4 boxes and they all experienced the same thing when I turned it on. The 4 boxes are in different vlans.
Irritating!
