From the radius.inc and captive portals index.php file it looks like the following should work (Nomadix attributes): [Vendor = 3309  (Nomadix)] ATTRIBUTE      Nomadix-Bw-Up ATTRIBUTE      Nomadix-Bw-Down Imagine you would add these to your radius radreply table, e.g. insert into radgroupreply (groupname, attribute, op, value) values (“slowspeed”, “Nomadix-Bw-Down”, “:=”, “1024″); not 100% sure on this though - would be good for someone to confirm this.

thank you sir. sir, may also ask a minor clarification with the "concurrency" you've just mentioned, is this means that this will "only" work if I had put "checked" on "Disable concurrent logins"? oh, how if I would like to stop using it or remove it from running? how will I do it? /* no pruning for fixed mac address entry */ if (portal_mac_fixed($cpdb[$i][3])) based on your code, what do you mean "fixed mac address", is this the Pass-through entries? -cruzades still researching/learning how to use cron job :)

You can make your own page and upload it to the pfSense. If you put the IP/MAC of the server on which the page is on the passthrough list, then it shouldn't be much of a problem to load it into the page on the pfSense.

@LostInIgnorance: I had a problem like this a bunch of times.  If you end up changing the IP of the interface where the captive portal is running on, it tends to think it is still using the old IP.  I never did figure out what caused it, but even after reboot or disabling and re-enabling the captive portal, the IP wouldn't change.  I know there is a place through shell to edit the address manually, but I never did find it.  Easiest thing that I had found being a newbie, just start from scratch, setup all the IPs, then enable the captive portal again. Thank you for your answer. I also think if i do a factory defaults reset it will work then but it's a bit tough for me to do that now. If somebody knows how to edit the address of the captive portal manually from the shell please share :) I found a some config files but are not the right ones for editing manually the portal ip : lighty-CaptivePortal.conf and lighty-webConfigurator.conf

could set hardtimeout to 60 min, but they can just log back in.

That just means RADIUS didn't respond those times, which probably corresponds with your server rebooting. Looks like it picked back up just fine after the server was back up. At least that's what I've always seen on my IAS server, and the setups I've done for a number of other companies.

just play around with squid and squidguard :)

Ah, excellent idea. What edits would I have to make to the default code in order for that to happen? I can't code my way out of a paper bag.

@rhy7s: I'm looking around at the moment trying to figure out a RADIUS solution to allow data-based voucher access for the pfSense captive portal. Something I was wondering was whether I would have issues with the various wireless bridges I have deployed. In the ARP table multiple IPs share the same bridge MAC address Then your bridge isn't bridging, it's messing with MACs where it shouldn't be. That won't work if that's how it shows up.

If they'll let you use RADIUS accounting and cut the users off via re-authentication, yes.

Not yet implemented.

This is a feature request and i advice you to go through the pfSense customer support with detailed description or just post in redmine.pfsense.org to be taken in consideration when someone is pleased to implement it.

Thanks - I will give that ago. I have made the changes remotely and will try to get someone to check the jukebox later. Thanks!

Yes, a few more features (like Vouchers) but what works now in 1.2.3 will continue to work in 2.0. http://doc.pfsense.org/index.php/2.0_New_Features_and_Changes#Captive_Portal

alright, i found the root cause. it's due to our radius server does not respond to it.

thank for the reply, that sounds good i will try release 2 of pfs, i have to find my way using radius server then.

I'm not sure anyone has this working all the way. You might have more luck searching for the phrase "single sign-on" instead of auto login.

There isn't a way to let users manage their own passwords in pfSense right now. You could setup a FreeRADIUS server, point the CP authentication at it, and find a web-based GUI for FreeRADIUS that includes a mechanism that lets the user change their own password.