Just keep in mind that CNA might not support 'javascript'.

When the portal page doesn't come up it is almost always: HTTPS set as browser's home page (go to a regular http site - just type 10.10.10.10 in the browser or something) DNS (usually static DNS servers in the client even though they're DHCP) Find out what port your portal is on and try connecting directly to that.  (eg http://192.168.10.1:8002)

in this moment we have connected 11596 users , not all this users is online simultaneously.

Thanks.  That still doesn't make it entirely clear that your port 8000/8001 portal is going to be changed to 8002/8003, etc.

Hello Gertjan! Thanks for the reply. with squid non transparent I am sure downloading continues after disconnecting via CP. In transparent squid everything is ok. I am using pfsense 2.0.3 only because in this version I can use non transparent squid with CP login option as using non transport squid I can block https traffic and also able to cache https traffic.

@ermal: You are sure this is still true on 2.2? Not sure if MAC passthrough is still slow when new users join and there are already thousands in the list, but just allowing them through, the database appears to be cleared on reboot.

When you upload a customised CP login page it does get backed up as part of the XML config file (I've done it so I know it works). The pictures ought to be included as well, assuming you uploaded them via the 'file upload' section of the captive portal configuration pages.

Solved my issue. https://forum.pfsense.org/index.php?topic=85695.msg481877#msg481877

Yes but its easier for me to add a whole subnet in captiveportal.inc since I have no control what IPs the servers will get. I only supply a pre configured pfsense.

The symptom is the same, the crash is quite a bit different from the looks of your crash report. 2.2 release is now out, upgrading to it is your next best step.

I have those problems too.  I don't believe the timeout is long enough before iOS gives up on the Wi-Fi and goes back to cell.

It is impossible infeasible to successfully captive portal HTTPS connections unless you control all your prospective client devices and can pre-install trusted root certificates.  It is better to just drop TCP/443 traffic until the portal session has been negotiated via TCP/80.

thank you cmb!!! i plug the WAN to LAN and set it same subnet. now i can start the voucher sell. :D

thanx ill try that

Ok, did a little digging and this does what I need it to do. Sort of: https://forum.pfsense.org/index.php?topic=63531.0 Ideally it would still be useful to implement bandwidth restrictions only when usage reaches a certain threshold. I suspect there is nothing in the traffic shaping rules which will do this, but thought someone might like to prove me wrong.

Not to mention https://doc.pfsense.org/index.php/Using_Captive_Portal_with_FreeRADIUS#Amount_of_Bandwidth