Captive Portal turned on but not working

ahtonks

I have problem, I was turn on Captivate Portal on VLAN but it allows all users to internet without asking any username or password.
I Use Local User Manager, I have defined login and error page, I have enabled DHCP and DNS forwarding.
Did somebody give me advice where I found solution.

Thank you.

cconk01

I have the same issue but with a radius server. I upgraded to 1.2.1 and it hasnt worked sense. I have tried disableing captive portal, re-enabling it, using local authentication, and tried openeing up the firewall rules to allow captive portal out with no fw rules. Im a little lost at this point too…

jewps

I can confirm this issue as well. I'm still using 1.2.1-RC something…

I've got a feeling it'll work without VLANS but I can't test it right now.

mrguitar

Same problem here.
:(

…I really don't want to down-grade.

grover77777

Same problem here. Have been using this fine in production on v1.2 with several VLANS.

After upgrading to v1.2.1, CP stopped working/forcing users to authenticate.

Users on that VLAN interface with the Captive Portal are able to use the network without authenticating. This does not prevent them, however, from logging in by manually visiting the CP login page.

cconk01

Anyone know if 1.2.2 fixes this issue? I didn't see anything about it on the fixes page…

mrguitar

Still not working 1.2.2.

smith02

http://forum.pfsense.org/index.php/topic,13526.0.html

cmb

Works for me, but the only VLAN install I have handy and can experiment with is on 2.0. I would expect it to work the same though, as the only difference related to CP between 1.2 and 1.2.1/1.2.2 is the FreeBSD version change. I know CP works on 1.2.1/1.2.2 without VLANs.

cconk01

Thanks for the help,
Peter

cmb

There is something going on with ipfw and VLANs, which is leaving CP and VLANs inoperable. I checked out an affected system, and it isn't going to be straight forward to figure out. The traffic is matching ipfw rules on a different VLAN interface for some reason. All the underlying configuration is completely correct, so there seems to be some sort of bad interaction between ipfw and VLANs in FreeBSD 7.0. I won't have time to resolve it immediately, but it's on my todo list for sometime in the next week.

cmb

Someone who can replicate this - please try a 1.2.3 snapshot from here:
http://snapshots.pfsense.org/FreeBSD7/RELENG_1_2/

And report back on whether you can still duplicate this. Odd thing is, there are installs with VLANs and CP on 1.2.2 that do work fine.

1.2.3 is currently FreeBSD 7.1, and I'm curious if that makes any difference. 1.2.2 uses the same CP as 2.0, and it works fine in 2.0. The only significant difference there is 2.0 has been FreeBSD 7.1 for a while and 1.2.2 is 7.0.

mrguitar

…just upgraded and when I click the captive portal section in the gui I get this:

Parse error: syntax error, unexpected '[', expecting T_VARIABLE or '$' in /usr/local/www/services_captiveportal.php on line 515

Gertjan

@mrguitar:

…just upgraded and when I click the captive portal section in the gui I get this:

Parse error: syntax error, unexpected '[', expecting T_VARIABLE or '$' in /usr/local/www/services_captiveportal.php on line 515
[/quote]

Same here.
The error on line 86 (index.php) disappeared - this one is new.
(Just upgraded to 1.2.3)

Edit : Humm, open /usr/local/www/services_captiveportal.php in any descent editor like vi and goto line 515 - change this

….….

for

….g['product_name']?>….

:)

mrguitar

Thanks Gertjan,

I added the 'g' variable and the page loads now. However I'm into "business hours" so testing is a little difficult. I should have something to test in a couple of hours. One thing I've noticed is that I'm running the CP on a vlan, and the setup page has a link to view the current CP page. That link is pointing to LANIP:8000 shouldn't it be VLANIP:8000?

The current setting would make sense for a test page, but it doesn't load.

Again, I should be able to report something soon.
Thanks,

cmb

That problem with product_name is fixed now.

Gertjan

Yep => https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/9c1e225932e60f71b3e28170016e9afa7048871e ;)

mrguitar

OK I finally had time to test this and the CP doesn't work w/ VLANs. :(
Everything appears to be identical to 1.2.2.

Slam

VLAN's & CP are working for me with "1.2.3-PRERELEASE-TESTING-VERSION built on Thu Feb 19 21:52:48 EST 2009".

Slam

glued2

Slam, are you using Authentication on your CP? (if so what type)?

I've been trying to get this working for a little while with mixed success - but my success seems to vary depending on authentication type…

As I've never had CP working and am fairly new to pfSense there is every chance its something on my network, or something I'd doing causing my issues, but its nice to hear it is working for someone - I'll upgrade asap.