Found the following which appears to do exactly what I want but I am not sure how to implement it. http://freeradius.org/radiusd/man/rlm_counter.html

Have you tried just unchecked the enable box, and then checking it again? That should force the fields to be enabled, though I don't see how they would be locked in the disabled mode either. Like Ermal, I haven't been able to replicate that.

Hello Jim, I look forward to the updated book. I will touch base with Jos in a few days to get the new version. We are running a customized version of pfSense 1.2.3 so it will be a while before we can upgrade to 2.0.  So we will need to settle for the above for now.  The only draw back I see is that src LAN_NET gets replaced with any in all rules.  I still have not been able to unscramble exactly why this allows the captive portal LAN subnets to work. There is some interaction between pf and ipfw that I am not quite getting… However, the bottom line is that for whatever reason changing that one line in filters.inc causes subnets to work with captive portal. Thanks for help and advise here and in other postings. take care. --luis

Thanks for the prompt Replies guys.  I appreciate it!

What is that option for on the captive portal settings page if it wasn't intended to be used?

When you tested it, did you manually go directly to the captive portal page or did you get redirected there when trying to access something else?  When you go there manually, it redirects to itself when you log in.

Probably 3 possibilities here and I doubt if applying a firmware update does anything as it's almost guaranteed either your config has been changed, or it's completely unrelated to your firewall. You used a weak password, didn't restrict management access, and someone on that network cracked/guessed it and changed the redirect URL or something else in your config to do that someone on the network is doing bad things to MITM your users, ARP poisoning or similar. you're redirecting to a URL that's been defaced, that tag line is common on defaced websites. Attaching a copy of your config, and a packet capture of all traffic from an affected machine while it's accessing captive portal and getting redirected would tell more. You can email those two files to me off-forum if you don't want to make them public (cmb at pfsense dot org, include a link to this thread).

Can guide me to create RADIUS Server?

In our setup, we had to use the pfsense LAN IP as the gateway IP for the clients. Once i did that then things started working for us. We also put in the FW rules for any:any for all traffic. Its in a test lab so security of it isn't a problem for us right now. However, we seem to be having an issue where occasionally the captive login doesn't show up initially and once we stop and start the captive service that seems to 'fix' it. What is the manual URL you are using to force the page to appear?

Thanks for the reply.  The answer was right in the program instructions and it works great.  I then got caught up in other projects so my apologizes for the delay in acknowledging your assistance.

I believe that has been fixed in 2.0.

Redirect is not working at all. I have tried both. Accessing manually, coz i changed login page and normal "connect to WiFi and wait what happens" Maybe i can try adding nat rule manually. Not sure how to forward to backloop interface, but i will try asking Mrs. Google, maybe she knows…..

It is usually stable, but from time to time there are localized issues as changes are made and other things are addressed. Hoping for a release by the end of the year but the real answer is always "when it's ready".