1.2.3 RC3 Captive Portal not working..no Redirection

kapara

What do you mean by passthrough? Is that a checkbox on one of the DNS pages? Or do you mean a firewall rule of some kind?

Thanks,

Mark

htgtech

in the captive portal page there is a tab at the top "Allowed IP addresses"

click on that

in there you click add "+"

chose "to" in the direction

put the dns ip in the ip address field

add your description *dns1" or whatever you want

then click save

make sure to make one for each dns ip you have for failover purposes

kapara

Still have the same problem. No problem accessing the internet….

and I made the changes... IE

OPT1 172.20.128.0/24 with OPT1 interface 172.20.128.1

LAN 172.20.30.0/17 with LAN interface 172.20.30.1

Whenever I connect on that subnet I automatically get internet access no page redirect at all. ???

kapara

Sooooooooo fustrating….

Another interesting fact...

I cannot ping the OPT1 int ip of 172.20.128.1 unless I open a browser and go the http://172.20.128.1 and then it give me the portal page. After I log in I can ping the OPT1 int ip.

This should be an easy config...

dotdash

What are your OPT1 rules like? I have a similar setup on nano rc3 running fine. LAN is open, OPT1 is the wireless card, on a separate subnet. My OPT1 rules are:
BLOCK * OPT1 net * LAN net * * Wireless not allowed to access LAN
PASS * OPT1 net * * * * Wireless allowed out

I have nothing in the Allowed IP addresses in the CP config. Wireless clients are getting DHCP/DNS from pfSense.

danswartz

I think you can make this one rule. Make the destination !LAN?

jimp

I also have CP working fine on nano, it didn't take anything special. Not even any special allow rules for IPs.

I posted my settings in another thread.

mikesamo

same problem with squid lastest version

jimp

Has squid ever worked with Captive Portal?

I didn't think the two were compatible, but I could be wrong (I don't use CP much)

eri--

Only on 2.0 i think it will work right.
Even there i think some tweaking is needed for this..

Try on 2.0 if it does not work open a bug report on redmine.pfsense.org.

jimp

Thanks for the clarification, ermal. I suspected as much but it's nice to know for sure.