Captive Portal Bug

ariel.chiong

Anyone experienced after rebooting the machine, Captive portals User session doesnt work? from the user view it says that it is already connected but theres no connection. I need to force disconnect all users in Status > Captive Portal for users to reconnect.

pfsense details below:
2.4.4-RELEASE-p3 (amd64)
built on Wed May 15 18:53:44 EDT 2019
FreeBSD 11.2-RELEASE-p10

issue was also found in previous version.

Gertjan

Yep.
A very known issue - and it has a lot of coverage on the forum.
A temporary solution, called a patch (to be used with the Patch package) was proposed last year.

edit : the most easy solution is : do ot edit captive portal settings while user are connected.
Like : do not repair the engine of your car while it's running ^^
If you have to, stop it first (disconnect manually all users).

These are the patch settings :

You don't have to enter the "Patch contents", it will be read in automatically.
Use the URL : https://github.com/pfsense/pfsense/compare/RELENG_2_4_4...Augustin-FL:fix-reconfig-for-2-4-4.diff
Give it some title.
Save.
Do a Fetch.
Do a Test - it should mark that the patch can be applied cleanly.
Do a Apply - you'll be seeing a "Patch applied succesfully".

Btw : I'm on 2.4.5-RC (amd64) - latest version from yesterday/today - and it works.

wazim4u

@Gertjan said in Captive Portal Bug:

Btw : I'm on 2.4.5-RC (amd64) - latest version from yesterday/today - and it works

@Gertjan do you mean this patch works for 2.4.5-RC or does 2.4.5-RC no need to patch.

Gertjan

See https://forum.netgate.com/topic/149005/2-4-5-snapshots-are-live/18

2.4.5 RC and the upcoming 2.4.5 Release will/still have this "issue".

viktor_g

@Gertjan is there any bugreport?

Gertjan

There was one .... more then one probably.
I'll hunt them down, and report back.

Btw : this is a bug of course. Easy to circumvent, it doesn't bother me, but plain broken.

viktor_g

https://redmine.pfsense.org/issues/8616

Gertjan

That's the one - or actually one of the two solution proposed.
It's merged again 2.5.0 so it will haunt the 2.4.5.x series for long time, except if it can get backported.