Thanks that works. Post is resolved :)

@YQ:

…..
Not really. They specifically use nas identifiers to identify hotspots. (did a search on their site using google's "site:" parameter)

Of course they use the NAS.
And the IP …. and who knows what more.
I have the technical doc from these guys http://www.passman-hotels.com/ (a portal operator in France) and their AP's are using VPN's.
Or maybe they use a Radius server build for their own needs. I can't tell (and they won't tell me ^^).

@j4nus:

Is there a way to specify the zone id ?
The zone id 80 (in place 2) would be a good match, so the captive portal would run on tcp/8080 which is usually allowed (at least to connect a proxy).

Using "8080" (http), it can be done.
The dumb solution : create a portal zone. You'll see the port number increments. Continue creating until you reached '8080' for your http.
Now, wipe all preceding zones.
Or:
The smart one : create a zone. Test drive it. Stop captive portal. Edit your config.xml (the captive portal is easy to find, change the ID (which will be added to 8000)). Save. Start portal. Check.

Thanks jimp! Will look into that.

EDIT: Will FreeRADIUS do the trick? I see you can assign users a VLAN…

Wow, thanks for the quick reply and fix :)

Ohh i am a new to it soo i need some help. it would be great if some can help ok i need my log out page to display some things one is username of the logined in account second is the mac address third how much data the user used
im am doing in a vmware soo till now no issue i dont know coding so hope you guys can help me out i modified a templet so dont think i designed it .. i have a issue in firefox also i need it to display it not like a pop up in firefox showing this network  requires you to login can any one help me out whit this too will test with chrome also hope it show without any issue

Untitledq.jpg
Untitledq.jpg_thumb

thanks a lot for your help
Excuse me for my english

It's retrieved here https://github.com/pfsense/pfsense/blob/master/src/usr/local/captiveportal/index.php#L39
Up to you to 'hard code' it ;)

Does this show you :
[2.3.4-RELEASE][admin@pfsense.brit-hotel-fumel.net]/root: ps ax | grep 'prune'
15442  -  Is      0:00.00 /usr/local/bin/minicron 60 /var/run/cp_prunedb_cpzone1.pid /etc/rc.prunecaptiveportal cpzone1
15733  -  S        0:01.28 minicron: helper /etc/rc.prunecaptiveportal cpzone1 (minicron)
79162  0  S+      0:00.00 grep prune
(show here what it show you, do not say : yes - don't paste images of what you see, copy-paste the lines)

[2.3.4-RELEASE][root@LAN-GW.lan]/etc: ps ax | grep prune
31149  -  Is      0:00.00 /usr/local/bin/minicron 60 /var/run/cp_prunedb_client.pid /etc/rc.prunecaptiveportal client
31312  -  I      0:00.18 minicron: helper /etc/rc.prunecaptiveportal asiakkaat (minicron)
31143  0  S+      0:00.00 grep prune

So as you can see it is running. And i guess my problem really is that the DHCP lease time is less than captive portal idle timeout. Confusing that CP idle timeout is in minutes and DHCP lease in seconds.

But yeah, im ok with vi, ssh and cli. But not good with coding, so the php is too complex for me.

I used a portal idle timeout to great effect at a hotel. I only wanted them to be bothered by the portal once - even on a multi-day stay. I used an 18-hour idle timeout and a shorter DHCP lease time. I just made sure that the dhcp pool was large enough to accommodate the device churn through the property so the same lease was always available to give back to a device until they were long gone. As soon as the device left the property for 18 hours, the dhcp lease and the portal entry were both history.

I was thinking about the same thing. Only once bothered, perhaps every 24 hours.
I guess i just have to change the netmask to something larger first.

Thanks alot. I'll see how the tweaking of DHCP and idle timeout affects :)

We are authenticating users against a radius server that connects to AD - as 99% of our users have accounts.  The rest we assign vouchers on a per-case basis.

We have enabled "Enable Pass-through MAC automatic additions" and "Enable Pass-through MAC automatic addition with username" so they only have to authenticate once and then we have their username associated with their device.  The issue arises when we have more than 9000 separate device/username pairs in the db.  I know there are some php files that may help in pruning the mac auth table, just not sure which ones they are and what parameters to pass to them.

In the past, I've just been deleting the mac auth table once a year (just before fall semester - we are a University) and then everyone has to re-authenticate.  But with the growing number of devices everyone has, we are easily exceeding 9000 records within a year.

Btw : I think that you never filled in what so ever, but our 'intelligent' browser will auto-fill some entries - check always everything before you validate a page.

I didn't try to mess with cookies and stuff like that - just changed from my loved Firefox to Microsoft Edge… and it worked.
There should be something wrong.

So I decided to show all my steps just in case.

STEP 1 - CREATE CAPTIVE PORTAL ZONE >>> X - Enable Captive Portal

INTERFACES - OPT1
AUTHENTICATION METHOD - X LOCAL USER MANAGER/VOUCHERS
Click SAVE - OK

STEP 2 - ACTIVATE VOUCHERS Click over EDIT CREATED CAPTIVE PORTAL
Click over VOUCHERS

Enable    X - Enable the creation, generation and activation of rolls with vouchers
Click SAVE - OK

STEP 3 - CREATE AND GENERATE A VOUCHER ROLL Click over VOUCHER ROLLS
Click over ADD

Roll # - 0 (zero)
Minutes per ticket - 10 (minutes only)
Count - 5 (vouchers code)
Click SAVE - OK - Voucher created - a new roll line appear at screen
Click GENERATE - a button besides - asked for where to save a .csv file with vouchers codes - OK

STEP 4 - CUSTOMIZE CAPTIVE PORTAL PAGE Click over EDIT CREATED CAPTIVE PORTAL

Created a custom file VOUCHER.HTML to only ask voucher code

ENTER YOU VOUCHER

<form method="post" action="$PORTAL_ACTION$">
        <======= DELETED THIS LINE FROM SAMPLE
    <======= DELETED THIS LINE FROM SAMPLE

</form>

===============
Look down for HTML Page Contents / Portal page contents
Click over SEARCH and load voucher.html

Click SAVE - OK

5 - TEST It worked fine

Thanks to all the community again !!!

Hi,

You should tell us more, much more about your setup.

Right now, I default to : your setup is wrong. You should correct it.
Captive portal works fine for me for years now.

@mostafa.adel:

only open when i am write any ip on URL like 8.8.8.8

This looks and smells like a DNS problem (DNS is the thing that translates domain names like pfsense.com to 2610:160:11:1000::18 (or the old fashoined IPv4, I guess it still exists).
So, the ….. /  ..... continue to read here : https://forum.pfsense.org/index.php?topic=130521.msg723896#msg723896

@chek69:

You checked you firewall ?

well, as he said,

… My start page, or any other page, opens immediately ....

traffic (http https and - important - dns) works ….
The default pfSense rule " let everything go out " should be in place. And the same firewall rule would be enough to make the portal work.
I'm presuming of course, this still is a typical case of "My firewall doesn't work and I'm NOT showing you my firewall rules so you could NOT see why it doesn't work …"

I connect a device to the LAN network

Detail the connection please - is this by wire ? Or Wifi, and thus an AP is involved …

Or : Others are uploading their own 'portal page' without knowing that "html" is not a human language, the slightest error will take everything down ... (the built in page works great).

Help exists for many years already. This page will cover 99 % of all problem case : https://doc.pfsense.org/index.php/Captive_Portal_Troubleshooting

Can you give us more informations

In your Captive Portal configuration, you 'll find Concurrent user logins = If enabled only the most recent login per username will be active. Subsequent logins will cause machines previously logged in with the same username to be disconnected.

Every wifi device that joins your network takes a DHCP lease whether they go through your portal or not.

The pool size needs to be sized to accommodate your device churn and your lease times and your portal timeouts, hard or idle.

hello ,
tough able to login into the pfsense webconsole using  the ldap user by giving it the webcfg privileges , it just works.