The captive portal doesn't release the IP of the site for access without authentication.

[lufg25]

Good morning, I'm new here and I wanted to know if anyone has had this problem with the captive portal of pfSense 2.7.2. I did all the procedures to release the IP of a site and unfortunately it doesn't work, it worked on 2.4 and I'm having trouble updating the version because of this. Could someone help me?

[Gertjan]

@lufg25 said in The captive portal doesn't release the IP of the site for access without authentication.:

I did all the procedures to release the IP of a site

What do you mean by 'site' ?
It's a device that asks for a DHCP lease.
So, it's the device that can end the lease, and you have to do that on the same device.
Example : if it is a Microsoft Windows device :

ipconfig /release

How is your question captive portal related ?

2.4, like pfSense 2.4 ? Really ?

[lufg25]

@Gertjan
Sorry, I didn't really understand the website, it would be a web page that I built to do self-registration

[FSC830]

@lufg25 said in The captive portal doesn't release the IP of the site for access without authentication.:

@Gertjan
Sorry, I didn't really understand the website, it would be a web page that I built to do self-registration

And actually I dont understand what are you trying to do!?
Which website are you talking about? Where do you want to setup a self-registration?
Please provide more detailed information.

Regards

[Gertjan]

@FSC830

If I consider that "to do self-registration" is the clue here.

It's must be the 'self made' captive portal login page that is written in, for example PHP that requests the usual 'private' info from a portal visitor, and after storing this info in a flat text file or bit harder, in some database, and validating it (portable phone number => SMS) and mail address (mail with portal password sent to potential portal visitor) to give the portal page visitor access to the portal.

The thing is : sending SMS is not free. And every SMS gateway has its own API to access it.
Sending mail to someone that can not use the portal to get access to it's mail box is also 'complicated' (chicken and egg issue).

IMHO, no one gives his phone or mail address to have 'not really free' portal access anymore.

I've been using such a setup for several weeks. Found myself confronted with angry portal users.
It's became even illegal, or at least very complicated (where I live) to collect this kind of info.

[FSC830]

@Gertjan
Thanks for clarifying. I was guessing somewhat like this, but was not sure.
Yes, allowing access to someone using self registration could be difficult.
Beside of some law restrictions the requestor must be able to receive the access code by mail/SMS or somehow else.

My favorite would be sending the code by mail, anyhow, after an update you may need to check if all is still running.
So my pages for the voucher QR code printing need to copied to the pfSense again after every update.

Back to self registration: its a challenge, if connected to CP you are already connected to the WiFi, but without internet access (code still not entered), so how to receive the access code?
May be by building a dynamic portal page which shows the access code after entering a string, a captcha or something else, as said a challenge .

Regards