@mbutz89: I do not have control on what version we run in the field. Then perhaps you should advise those who have the control that they are running unsupported firewall version affected by many security issue long fixed in the versions that are supported. You are also missing tons of non-security bugfixes. https://doc.pfsense.org/index.php/Versions_of_pfSense_and_FreeBSD

If i hadn't looked at your previous posts i would have taken you for a spam bot and banned you. You really could run your post at least through some basic spell-checking… As for your problem: There is no way to prevent someone from cloning your MAC address and using it to circumvent your MAC-lock. That's mainly the reason why MAC-based ACLs are not considered useful.

This : @technobiz: …. still redirection to login page does not work. as a description of your problem will not help us to find out what you forget to mention (and we should know so we can tell you what is wrong). Tell us more if not everything about your interfaces. How you set up DNS. How you set up the portal (configure page). Start using the default built in login page - and make the portal should work. You should read : https://en.wikipedia.org/wiki/HTTP_404 Btw : you can not change  http://x.x.x.x:8002/index.php?zone to http://wireless.hotspot This : http://x.x.x.x:8002/index.php?zone is already incorrect. The "zone" parameter should contains value so pfSense knows WHAT captive zone it's handling (more then one can exist) This : "8002" is hard coded , and the first web server instance that is running to handle your first instance. When you use something like "http://wireless.hotspot" it implies "http://wireless.hotspot:80" so you will get redirected …. see instruction here https://doc.pfsense.org/index.php/Captive_Portal_Troubleshooting to see what's really going on.

2.0.x is far too old to expect anyone to assist in diagnosing. Even if you were on the latest 2.0.x release that's still 3.5+ years out of date. I seem to recall a similar problem back then that was fixed, also a long time ago. I didn't see any specific references in any of the release notes, though. From 2.3.x on it's even a completely different web server running captive portal connectivity (nginx now, was lighttpd back then) The best path forward is to upgrade.

Sweet!!!! Thank you again… I modified the line containing the regex so that it only matches lowercase a-f.... it's working like a charm... /* MACs input validation */ function freeradius_validate_macs($post, &$input_errors) { // MAC Address if (!empty($post['varmacsaddress'])) { if (!preg_match('/([a-f0-9]{2}[-]?){6}/', $post['varmacsaddress'])) { $input_errors[] = "The 'MAC Address' field must contain a valid MAC address, delimited with '-' character."; } }

Just set "No authentication" in the portal and make a button that says proceeed. No magic there.

You could run it by the Professional Services crew but I don't think we've gone so far as setting up external auth servers of that nature before.

I am sorry I know this is not a answer you are really looking for but I am just giving my 2 cents,  with pfsense I do not know of a way to view bandwidth by CP login info but if you like there is a other firewall called Untangle that can do exactly as you wish, and the good thing is you can keep pfsense as firewall and use UT in bridge mode

On mobile, are you waiting for the authentication page to appear automatically, or are you opening an http page for redirection?

@doktornotor: Alternatively, you might just use the banana.  8) hahahahaha… BANANA POWER!!!  ;D ;D

Hi, alternatively, to have logs inside pfSense with a rotation can be done as below (Method I had used long ago with pfSense 2.2.x): a) install the Syslog-ng package on pfSense b) configures Syslog-ng in Services / Syslog-ng / General as follows Enable (checked) Interface Selection: LAN Default Port: 5140 Leaving the rest unchanged and Save c) Now configure the default syslog pfSense to send logs to a remote server where the "remote server" is the same pfSense, then go to Status / System / Settings, activate Enable Remote Logging and put as ip address of the remote server to the LAN interface with the 5140 port, for example 192.168.1.1:5140, for Remote Syslog Contents choose what you want to send. Finally Save As a final result, Syslog-ng logs will be found in the pfSense filesystem, specifically in /var/syslog-ng/default.log and they can be rotated by turning the configuration of Syslog-ng

Really no good way, it's up to the client to notice.

Did you look at this page https://forum.pfsense.org/index.php?topic=108846.0 i liked it, on page 2 i placed an in my opnion beter script, in my modification only the not used vouchers are printed out.