You have to do this in two steps.
First step, you make your own submission, which reloads the same page, and launches the php code where you store your info.
Then, once this is done, you just show the CP form and have javascript autoclick on the submit button.
See my captive portal code in thread, my code does this more or less with the Login function.

Thanks for your replies, but I didn't want to have general discussion about IPv6 sense and non-sense. Fact is that IPv6 is upcoming more and more and Pfsense should be ready in all areas. We have a hotel with captive portal for our guests. CP isn't ready and it doesn't support for IPv6 traffic. In this year we will get a full dual stack (IPv4/IPv6) from our provider. Sometime in the future our guest will ask about IPv6 support. IPv4 addresses will by more and more rare so that some day a part of the internet won't support IPv4 anymore.

The question is still: Is planned that CP will support IPv6 in the future?

Captive portal can't be used in that manner. It authenticates the user or machine, then their access is determined by firewall rules the same as without CP.

Depends how your authentication works.
If it is the local user manager, go here : Status => Captive portal.
To see who logged in the past (and gave their sessions removed) : go see the captive portal log.

I watched a few videos and was going to start configuring the radius server. I found out my modems allow bridging so thats another option I guess. Thanks a bunch.

So it looks like for some reason Google DNS is not working from this location at all.  I disabled DNS resolver and enabled DNS Forwarder and changed DNS under general to Comcast instead of google and all working.  :o

@Derelict:

Two choices:

Let connections to https sites hang and make your users have to connect to an http site to get the portal page.

Intercept https connections, display your portal page, and deal with all the ramifications of being an https man-in-the-middle with certificate errors, browser protections, installing your certificate as trusted for your user's bank because they clicked the wrong thing, HSTS, pinned certificates, etc.

Third choice:

Disable captive portal. Let the users connect and go.

Thanks I too option 1 I added https://google.fr and it works.

I am interested in this solution, but….
:-[

@CallFromUSA:

….
Is there a place where connected users are shown?

For the last 8 years, it was here : (see image).

You need to have "Authentication method" set to "Local User Manager / Vouchers"
You need to declare a user "my_cp_user" with password  (System => User manager) and
Make this user member of the group "captive portal visitors". This group should be assigned to this "right" : "User - Services: Captive Portal login Indicates whether the user is able to login on the captive portal."

Status-Captive-Portal.png
Status-Captive-Portal.png_thumb

@Claylol:

I think, probably its a conflict of my school dns or dhcp ?? not sure, i think the configuration is ok.

Don't think.
Be sure ;)
Check it.

When a client connects to the "pfSense Captive Portal network" it should obtain an IP from pFsense (and from no one else).
You can check so with your device (the IP, gateway and preferred DNS)
You can see the lease showing up in pfSense.
You can see the DHCP server log in pfSense showing the device asking for an IP.

@Claylol:

Now im trying to put 1 Access Point and try it with my Phone.

Be aware that your AP should be AP - remove any DHCP server activities - shut down any router mode functions.
It should be a "transparent radio to wire" device.

@Gertjan:

So people do not mess around with "my_cp_user" and "my_cp_user_password", think about this html magic :

wow thanks even better.

@limona21:

I see there was an updated 2 days ago. That fixed the issue. Very nice :)

yea i also got the 2.3.1 update but today .

try this :

https://sourceforge.net/projects/captiveportalplus/

but i did not test it.

Update,

no more crashes since change to permanent -rw last week. Occured at almost each saving process before the change. So I think it is solved.
Thanks a lot for your help!

If problem reoccures, I'll give an update. But don't think so ;)

You should have a discussion with your AP  :D
It behaving like a router now. It shouldn't.
What also often happens if the AP has a "WAN" network plug : it's been hooked up to pfSense with this port. That's very wrong. Use a normal 'switched' port (there are normally a couple of them on the AP).
You should also switch off DHCP server in the AP.
It should behave like a transparent device for communication.

@mfaridi:

@Gertjan:

@mfaridi:

…..if they use DHCP , they can not access to Temp server and webserver , because IP of temp server and print server and web server is static .

Since when system with a static IP can't be reached by a system which obtained an IP by DHCP ??
You really should detail about your network setup.

I re-read you message several times. I can't understand your problem, and probably I'm not the only one.

Thanks,
My problem is this
in our network each computer has IP like this 192.168.0.1.25 and each computer do not use DHCP for get IP , network administrator set IP for each computer , and they do not want use DHCP , because we have web server , temp server and print server and vmwate server .and IPs of these server can not change.
So I have PFsense with Load balance and Failover and multiwan and squid .
squid has transparent mode.
So I want run Captive portal . Captive portal need DHCP .
what I must do when Captive portal need DHCP for work and computers in our network has IP like this
Computer 1 : 192.168.0.25
Computer 2: 192.168.0.26
.
.
.
computer 100: 192.168.0.125

Incredible.
All this proofs to you that you NEED to use DHCP IP assignment for all your client devices - and you shouldn't use static IP assignment (except maybe servers).
When a device obtains an IP, it also obtains (among other) an IP for a DNS server, which should be pfSense.
Use the DNS server on pfSense ( ServicesDNS => ResolverGeneral => Settings ) to make host overrides, so you can assigns names to servers with static IP's.
Now, your clients could use these names. Always.

Btw : my intranet (LAN) servers also use DHCP (not static), but I instructed my DHCP server (also pfSense) that it should always give the same IP to these servers.

Do not take me wrong, but I think you miss some (basic) network management knowledge ;)