pfSense 2.2 will actually be gaining a "global MAC ban" tab in CP that will redirect certain users to a special CP page if their MAC is "banned" – that might get you partway there, but the code does not exist yet (it's sponsored, in the queue to be added)

I had upgraded to 2.0.3-RELEASE, but the issue still exists. Same log found in system log and portal auth log. Jul 29 14:17:09 php[16361]: : The command '/sbin/ipfw pipe 20001 delete' returned exit code '1', the output was 'ipfw: rule 1: setsockopt(IP_DUMMYNET_DEL): Invalid argument' Jul 29 14:17:09 php[16361]: : The command '/sbin/ipfw pipe 20000 delete' returned exit code '1', the output was 'ipfw: rule 1: setsockopt(IP_DUMMYNET_DEL): Invalid argument' Jul 29 14:17:09 php[16361]: : The command '/sbin/ipfw pipe 20001 delete' returned exit code '1', the output was 'ipfw: rule 1: setsockopt(IP_DUMMYNET_DEL): Invalid argument' Jul 29 14:17:09 php[16361]: : The command '/sbin/ipfw pipe 20000 delete' returned exit code '1', the output was 'ipfw: rule 1: setsockopt(IP_DUMMYNET_DEL): Invalid argument' Jul 29 14:17:09 php[16361]: : The command '/sbin/ipfw pipe 20001 delete' returned exit code '1', the output was 'ipfw: rule 1: setsockopt(IP_DUMMYNET_DEL): Invalid argument' Jul 29 14:17:09 php[16361]: : The command '/sbin/ipfw pipe 20000 delete' returned exit code '1', the output was 'ipfw: rule 1: setsockopt(IP_DUMMYNET_DEL): Invalid argument' Jul 29 14:17:09 php[16361]: : The command '/sbin/ipfw pipe 20001 delete' returned exit code '1', the output was 'ipfw: rule 1: setsockopt(IP_DUMMYNET_DEL): Invalid argument'

@sdtelecom: Try to set the Maximum Concurrent Connections to 1. hope this helps This didnt helps. Minimum of value is 4, max 100.

Ok, Anyway it works now, that's the important thing.. ;D

Theoretically it's the same handling, but it works with 2.1 In 2.0.2 and 2.0.3 the last activity date isn't reseted nor updated always. So pfsense logouts useres just after login. I use an external Radius server for authorization.

Got it, thanks wallabybob is working  ;D

Replying to my own post: Turned out that indeed the layer 2 filtering was turned off! The culprit is: net.link.ether.ipfw!!! Once turned on:                         sysctl net.link.ether.ipfw=1 Everything just started working! The question is: Do I need to put this is /etc/sysctl.conf? /wai-sun

@rhy7s: Have you considered Gargoyle Router instead? You could set up a fairly hands-off quota and throttle system. No, I need a captive portal to control and log access by user account, regardless of what computer or device they're using. Right now Zeroshell seems to be working, so I don't want to upset things.  If Zeroshell's rudimentary logging becomes a problem then I'll revisit other solutions like pfSense.

The place I used one, it was attached directly to a windows PC. It could not attach to pfSense. What you'd normally do is export a roll of vouchers from pfSense to a CSV file and them import it into windows somehow (e.g. LO Calc, Excel, etc) and then print them to the printer from there in a batch, and then have them hand out the slips as needed. If you want "on demand" printing where the vouchers are not printed until they're requested, that's a lot harder. It would involve a program on the front desk PC that could trigger the printing of just one voucher at a time from the roll. Possible, but not as simple as pre-printing them. Someone else here may have better advice for that.

I had the same problem here. output of pkg_info | grep mysql is: mysql-client-5.5.21 Multithreaded SQL database (client) mysql-server-5.5.21 Multithreaded SQL database (server) After running: touch /etc/php_dynamodules/mysql /etc/rc.php_ini_setupphp -m | grep mysql mysql mysqlnd /etc/rc.restart_webgui No result. But when I restart the webconfigurator bij the menu (option 11)  phpinfo() gives me a positive I guess a bug

An alternative to this is to use an IP address of the NTP server instead of its hostname :) or Make sure that your NTP server hostname is resolvable by your DNS server. it should boot faster.

@Nachtfalke: Or adjust the DHCP lease times. But the lease time should not be lower than the hard timeout set on CP. Ok I will try this. My hard time is 30 minutes. I gave lease time 2000 seconds.

I'm not sure what the relation is between both code dumps? Can you give us some more information? Can you see that the actual post request is done``` ($.post('captiveportal-x.php', $("#testform").serialize());) To see this you need to change the return of function 'mycall' instead of 'false'