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.

Did u try the proxy server Squid?

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!

thank you jimp!

@knight313: I know that this is old topic but I met this issue and solved with these steps. On the interfaces WAN page unchecked  FTP Helper and changing firewall automatic outbound NAT to Manual . thanks for the reply.  FTP helper has 3 options, do i un-check all 3?

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.

hey guys, i was just gonna start a new thread with the same question but i searched this. Is this possible in 2.0?

The page looks ok though i do not think you need the two submits/forms and only one redirurl is ok if you collapse together. About radius or vouchers presently no, it cannot be done. Hopefully it will make 2.1. You can hack the code to allow this if you want.

Should be back now. https://github.com/bsdperimeter/pfsense/commit/985d6e18ebe3f2c2efe200032130e093b9b110f8

Only in 2.0 you can do that.

If you just want to be able to reach the web interface of the captive portal, its port 80.

Having the same problems on pfSense 2.0 RC3 (using the pfSense-2.0-RC3-1g-i386-20110621-1821-nanobsd.img.gz Image). Per-user-bandwith restriction set to 200kbit/s. Captive portal is loading, I login using username and password, it authenticates me (listed on status page), redirect times out. No site is loading. restriction is turned off: Redirect works like a charm. I'm not using squid, so I don't think it's the problem here.

Thanks for your reply. I'm gonna try it and tell u if it's working.

secure connection protocol or something like that. with winscp you move files between windowd and *nix like systems, like bsd linux etc

O.o it works… I don't change anything, just update pfsense and now seems it works. i'll try clean my cache and i'll try some other notebook... i confirm...now it works. i didn't do anything, just restart my AP, my router and start pfsense today, update this one to new version (2.0-RC3 (i386) -built on Thu Jul 28 23:16:13 EDT 2011 ). Nothing more. i post again the results of ifconfig and ipfw show (i don't know if could be useful) ifconfig bge0: flags=8802 <broadcast,simplex,multicast>metric 0 mtu 1500        options=8009b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,linkstat  =""  e="">ether 00:11:43:ab:3c:1e        media: Ethernet autoselect (none)        status: no carrier xl0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500        options=80009 <rxcsum,vlan_mtu,linkstate>ether 00:04:76:18:b0:32        inet 192.168.0.3 netmask 0xff000000 broadcast 192.255.255.255        inet6 fe80::204:76ff:fe18:b032%xl0 prefixlen 64 scopeid 0x2        nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (100baseTX <full-duplex>)        status: active xl1: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500        options=80009 <rxcsum,vlan_mtu,linkstate>ether 00:04:76:18:b0:2b        inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255        inet6 fe80::204:76ff:fe18:b02b%xl1 prefixlen 64 scopeid 0x3        nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (100baseTX <full-duplex>)        status: active rl0: flags=108843 <up,broadcast,running,simplex,multicast,ipfw_filter>metric 0 m                          tu 1500        options=8 <vlan_mtu>ether 00:e0:4c:39:14:6b        inet 10.59.1.8 netmask 0xffffff00 broadcast 10.59.1.255        inet6 fe80::2e0:4cff:fe39:146b%rl0 prefixlen 64 scopeid 0x4        nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (100baseTX <full-duplex>)        status: active plip0: flags=8810 <pointopoint,simplex,multicast>metric 0 mtu 1500 lo0: flags=8049 <up,loopback,running,multicast>metric 0 mtu 16384        options=3 <rxcsum,txcsum>inet 127.0.0.1 netmask 0xff000000        inet6 ::1 prefixlen 128        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6        nd6 options=3 <performnud,accept_rtadv>pflog0: flags=100 <promisc>metric 0 mtu 33200 pfsync0: flags=0<> metric 0 mtu 1460        syncpeer: 224.0.0.240 maxupd: 128 syncok: 1 enc0: flags=0<> metric 0 mtu 1536 ipfw0: flags=8801 <up,simplex,multicast>metric 0 mtu 65536 ipfw show 65291   0      0 allow pfsync from any to any 65292   0      0 allow carp from any to any 65301  14    464 allow ip from any to any layer2 mac-type 0x0806 65302   0      0 allow ip from any to any layer2 mac-type 0x888e 65303   0      0 allow ip from any to any layer2 mac-type 0x88c7 65304   0      0 allow ip from any to any layer2 mac-type 0x8863 65305   0      0 allow ip from any to any layer2 mac-type 0x8864 65306   0      0 allow ip from any to any layer2 mac-type 0x888e 65307   0      0 deny ip from any to any layer2 not mac-type 0x0800 65310 329  34233 allow ip from any to { 255.255.255.255 or 10.59.1.8 } in 65311 277 118046 allow ip from { 255.255.255.255 or 10.59.1.8 } to any out 65312   0      0 allow icmp from { 255.255.255.255 or 10.59.1.8 } to any out icmptypes 0 65313   0      0 allow icmp from any to { 255.255.255.255 or 10.59.1.8 } in icmptypes 8 65314   0      0 allow ip from table(3) to any in 65315   0      0 allow ip from any to table(4) out 65316   0      0 pipe tablearg ip from table(5) to any in 65317   0      0 pipe tablearg ip from any to table(6) out 65318   0      0 allow ip from any to table(7) in 65319   0      0 allow ip from table(8) to any out 65320   0      0 pipe tablearg ip from any to table(9) in 65321   0      0 pipe tablearg ip from table(10) to any out 65322 653  78203 allow ip from table(1) to any in 65323 685 660723 allow ip from any to table(2) out 65531 296  26923 fwd 127.0.0.1,8000 tcp from any to any in 65532 264  35405 allow tcp from any to any out 65533 472  42177 deny ip from any to any 65534   0      0 allow ip from any to any layer2 65535   0      0 allow ip from any to any</up,simplex,multicast></promisc></performnud,accept_rtadv></rxcsum,txcsum></up,loopback,running,multicast></pointopoint,simplex,multicast></full-duplex></performnud,accept_rtadv></vlan_mtu></up,broadcast,running,simplex,multicast,ipfw_filter></full-duplex></performnud,accept_rtadv></rxcsum,vlan_mtu,linkstate></up,broadcast,running,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,vlan_mtu,linkstate></up,broadcast,running,simplex,multicast></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,linkstat></broadcast,simplex,multicast> Thanks for yours help guys. Bye :)

If you stay in limits of licensing ;) Note: I'm not developer so that was only guessing.

@bucky31: Will I need to set my wireless controllers default gateway to the pfsense LAN IP address? I'm not familiar with those wireless controllers but I would guess: No if the wireless controller gets its "WAN" IP address from pfSense by DHCP. Yes if you have configured a static IP address on the wireless controller's "WAN" interface. One problem with using snapshot builds is that there might be a temporary bug introduced as part of a fix for a different. I've had good results with the official RC3 built Tue Jun 21 17:40:54 EDT 2011 and with the snapshot build in file pfSense-Full-Update-2.0-RC3-i386-20110719-2331.tgz