Well..dd-wrt doesn't support it on the webgui, however it's linux, so it's probably possible. But looks like the newer firmwares doing it differently (2.4 vs 2.6 kernel). I don't feel the power in me to do it by hand… i'm sure it gets worse eventually :)
Is there any way to combine it into one login maintaining that level of encryption/security? I don't really want to be giving my wireless AP password out.
I mean it's not that big of a deal, but if I'm going to give out the AP password I mind as well just use captive portal as a bandwidth limiter instead of user login.
Thoughts?
I think you can still have WPA encryption without having to have an AP password.
Some wireless hardware support 1 or more AP's, so you can have a guest AP with the captive portal and segregate that from your LAN. So in essence it doesn't matter if you have to give out your guest AP password.
When you connect to your wireless network on your ipad it automatically brings up a splash screen to sign in. I then enter my password (my user is set by default in the splash page).
This didn't happen to me with pfsense CP, but with other CP it happens. When i attempt to navigate in safari, I became redirected to the CP page and after loggin I can navigate without problems.
this can be marked as solved, I did some further digging and what I found was that the mac address of the user that was logged in DID NOT match my laptop wireless adapter MAC address, it matched the WAP instead, so I had to use the option "DISABLE MAC FILTERING", which for me is ok as I won't be using "PASS-THROUGH MAC"
Basically, I have a guest user that has a userid of 2001. I put this script in the /etc folder as rc.password.guest and made a cron job to execute it weekly. I have added a little bit to the end of the script that emails this guest password to a distribution list, so our conference room admins have the password every week. They give it out to vendors and guests so they can use wireless in the conference rooms.
My RC3 portal also stopped working just after I upgraded from RC2, and I've been pulling out my hair (as well as my managers pulling my hair) trying to get it fixed. Turns out I just needed to add the auth_voucher as a hidden input, even though I'm not using it, and it started working again.
Thanks for the hints, I figured it was worth a try!
Captive Portal in pfSense 2.0 is enabled/disabled on individual interfaces. If your AP is a pfSense interface you can enable CP on that interface. (I use CP this way.) If your AP is external to pfSense then you can enable CP on the interface connecting to the AP.
If you have an external AP do you want to have different firewall rules for WiFi devices and wired devices? If so, its probably most convenient for them to have separate interface on pfSense.
