there is no change to the code. I just manually put <radiussession_timeout>1</radiussession_timeout> under <captiveportal>in /cf/conf/conf.xml. in m0n0wall there is a option (checkbox) in captive portal configuration. Not remember the exact word, but it something like 'use session_timeout returned by radius'. The checkbox option was taken out in pfsense last time coz the feature not working. hope this help..</captiveportal>

Yes it is just for local users

Make sure you are using the latest snapshot, there has been some changes to CP when using multiwans.

his scripts are for a freeradius version that uses a mysql database the pfsense freeradius version uses files for its user database and the pfsense php don't have mysql suport thats is why you get those errors

It's possible but was not a design goal for 1.2.

I am running pfSense as a multi WAN load balacing router with no firewall or any other feature. Will this speed limiting per IP address work in this situation? Just a note.  I had to run decent hardware to keep up with the stress of load balancing: Athlon XP 2400+ 512 MB DDR 333Mhz 4 x 100MBit NICs 40GB HD (just cus)

You using 1.2b1? If not, try it.

thanks bro

U need to email Jonathan DeGruve or Lee Sharp (Sorry is name spelled incorectly) Just use the mono-dev list I spoke to them before but they told me that DNS can be spoofed hacked etc, there fore it is not secure :-( I like DNS for radius though

some domains like google, paypal, microsoft, yahoo (well big once) have more then 1 IP so u have to add them all in. For me ist big problem espesially pay pal with pool of 20 IPs that pereodicaly changing

Is there a reason you set the leases to only be two hours?  I would make them 8 at least, and just increase the number of addresses, that should solve your problem the default lease is two hours, but if i make it to 8 hours wouldn't it still be a problem if it's caused by the dhcp server lease ?

Hi, Didn't you set the HTTPS Captive portal page ? In this case, the URL is https://10.0.1.1:8001 and not 8000. Just in case.

I think I spoke too soon.  In doing some testing again today, I have found that my mods build the lighttpd files correctly but the redirect no longer works, which is the same behavior I saw before.  Infinitely frustrating.  Back to the code I guess.

1.0.1-SNAPSHOT-03-27-2007  seems to have solved my ssl failure. For the last 2 days, everything was fine. I keep crossing my fingers, Thansk for your help, Benoit.

I have done a massive reconfigure of the network! Added VLans and confirmed that all is in WDS mode! I added servers and new subnets and I will fire up the capture portal tonight and give it a test! Client >>> CP Server >>> routing to new subnet with Squid Server >>> Squid to PFSense Router and out the door! We shall see I will post the results….

Thanks for the response. I will definitely give pfsense a try then.  It seems as though it is what I have been looking for.  Now all I got to do is find the time to try it out hehe.

@hoba: squid won't work with captive portal currently. It has been discussed somewhere else. Please search. when I had one own server and so when I didn't use carp I used captive portal and squid and all works fine …  But I 'm going to search