captive portal idletimeout in 25.1.12 works like a hard timeout

[nycspud]

After updating to 25.1.12 captive portal seems to be treating the idle timeout like a hard timeout.
Sessions drop after 15 minutes which I have defined in the idle timeout setting.  Hard timeout is 0 (disabled).

[franco]

Stephan tried to reproduce this but no luck. If you have more data to reproduce that would be appreciated.


Cheers,
Franco

[tuto2]

For context, I tested on 25.7 but nothing has changed on the Captive Portal side between these two versions.

[nycspud]

Hmm, ok.  That's good to know.  I'll upgrade it to 25.7 to see if it resolves the session timeout.
I did have zenarmor previously installed but removed it.  I noticed the crash indicator about being unable to open mongodb.so after updating to 25.1.12.  Maybe that has something to do with it?

I removed the php82-pecl-mongodb package via cli and the crash indicator went away.

[franco]

Different issue. I also think what Stephan meant is that 25.1.12 and 25.7 have the same CP code so your issue will likely persist.


Cheers,
Franco

[nycspud]

Yes, understood.
I was just wondering if the old zenarmour packages interfered with the update in anyway.
I had just gone from from 24.7 to 25.1 then to 25.1.11 which worked fine and then a couple of days later 25.1.12 came out which seemed to break CP. It had been a while since I upgraded this system.
I had removed ZenA prior to upgrading to 25.1.
Thanks for testing and all your hard work.

[tuto2]

Well let me know if the issue persists on 25.7, and if so, how you tested it. Setting the idle timeout to 1 minute and leaving a ping running on the client should show quick enough if there is a problem.

[nycspud]

I ended up doing a clean install of 25.7 and imported the config.
I noticed in 25.1.12 and 25.7 that the Bytes (in) and Bytes(out) is not being reported and Last Accessed is not updated.

I had to bump up idle timeout to 12 hours because I had active users but all users were bumped off after 12 hours of initial log in.

In my CP log file I did see the idle timeout kick me out about 12 hours after my initial log in session even though I was passing traffic.

2025-07-25T04:45:57-07:00 Notice captiveportal session zFdmicC0ZY8ooE/M8Cmalg== hit idletimeout
2025-07-24T16:45:56-07:00 Informational captiveportal AUTH Me (xx.xx.xx.xx) zone 0

I'll try and do more testing over the weekend with shorter time frames but it does still seem to be happening at the moment.
Let me know if there's other info you need and I'll try to get it.

I forgot to mention, my captive portal page after updating to 25.7 stopped showing the log in and password boxes and I had to revert to the default page from 25.7.
Thanks!

[franco]

> I noticed in 25.1.12 and 25.7 that the Bytes (in) and Bytes(out) is not being reported and Last Accessed is not updated.

That sounds exactly like the type of problem that would make an idle timeout behave like a hard timeout so that's worth a closer look.


Cheers,
Franco