Using CP on OPT interface with wireless AP?

danbutter

ok, I was able to hook into the router being used as an AP via the built in 4 port switch, get an IP and same results as earlier.
Also used the same crossover cable that was hooking into the AP (completely bypassing the router/AP) for the computer I hooked up with same results. Got an IP and nothing else.

What next?

jeroen234

make the dns server 192.168.11.1 or add 192.168.1.1 as a always passtrue adress on the captive portal

danbutter

the dns server was192.168.11.1 prior.
I changed it back and still nothing.
I tried adding the 192.168.1.1 as Allowed IP addresses both from and to (2 entries) to no avail again.

Any other ideas?

thanks

buraglio

If the captive portal is running on the opt interface, the The HTTPS server name needs to be the address (or resolvable DNS name) of that interface or else it will get captured and redirected to an address outside the captive network (192.168.1.1) and go nowhere.

nb

danbutter

ok, the https server name is the same as the address for the opt interface I am running the CP on now and still nothing.

I happen to have an OPT1 and OPT2 on this box and just for troubleshooting I tried to switch everything CP wise to the other (OPT2) interface with the same results.

I am to the point of starting over.
I guess I will do the reset to factory defaults when the workday is over and start from scratch.

Is there a tutorial on how to set up the CP from scratch?

Or does anyone feel like throwing one together??
I have seen the ones on doing it for radius and integrated user manager, but they both use the LAN and don't show you how to do the OPT interface.
I don't remember it being this difficult the last time I did it in monowall, but I am obviously missing something.

thanks for the help so far

buraglio

did you make sure there are no pf rules prohibiting the connection to the opt address/interface? From the cli can you see the lighthttpd instances running, check and make sure they are actually running, this should show you at least:


netstat -an |grep 800
tcp4       0      0  *.8001                 *.*                    LISTEN

Thats the ssl captive portal instance.


tcp4       0      0  *.8000                 *.*                    LISTEN

is the standard non-ssl page.

You can also do


ps -auxww |grep light
root    320  0.0  1.2  3480  3032  ??  S    Tue03PM   0:13.68 /usr/local/sbin/lighttpd -f /var/etc/lighty-webConfigurator.conf
root    409  0.0  1.0  3000  2420  ??  S    Tue03PM   0:12.12 /usr/local/sbin/lighttpd -f /var/etc/lighty-CaptivePortal-SSL.conf

to see what is running.

sullrich

Please upgrade to the latest testing snapshot. I fixed a rules issue for CP + OPT interfaces.

http://www.pfsense.com/~sullrich/1.0.1-SNAPSHOT-12-14-2006/

buraglio

Do you happpen to have a cvs link for the change? I can dig for it if you don't have it on hand. I'm curious to see what changed.

nb

danbutter

I hope to have time to update this weekend.
I will report back as soon as I do the update.

thanks

sullrich

http://cvstrac.pfsense.org/chngview?cn=15799

danbutter

Ok, I documented everything I did as I did it so that someone can hopefully tell me what I did wrong.
I did the full update to latest snapshot and then after it rebooted I did a reset to factory defaults and went through that reboot.

From there I went through the wizard and changed my time zone and password. That is all.

Then I have to login in IE since firefox won't let you get to the system menu with the default skin….some javascript error or whatever is doing the rollover and dropdown. Changed the skin to pfsense....back to firefox 2.0.

Ok then I then changed the name of the OPT1 interface to CP, changed it's IP to 192.168.11.1/24, enabled it and clicked on save.

I then went to DHCP server, clicked on the CP tab and checked enable... then put in the range from 192.168.11.55 to .60.
Not sure what to put for DNS servers or gateway, but as I have been told earlier I put 192.168.11.1 in for DNS.
Clicked save.

Go to Captive Portal, check enable choose the CP interface, click on save. No other changes.

Go to firewall > Rules click on CP tab, click on add new rule. Click on save. Hit Apply
Results in this:
Proto Source Port Destination Port Gateway
TCP * * * * *

Result is the same as before.
Went back to Services:Captive portal > Allowed IP addresses and because of advice given above added 192.168.1.1 both from and to (2 entries) and hit apply both times.

Result is same as before.

The one thing I was able to try this time since there are no users other than me on was to try the captive portal on the LAN.
It works perfectly and since I had no authentication I simply clicked on continue and off I went....as it was intended.

So what am I doing wrong here?

Oh, all this testing was done with a computer hooked directly to the pfsense box via a crossover cable and it Can get an IP in the range I put in.

Thanks for any help anyone can give me here.

hoba

@danbutter:

Then I have to login in IE since firefox won't let you get to the system menu with the default skin….some javascript error or whatever is doing the rollover and dropdown. Changed the skin to pfsense....back to firefox 2.0.

That's strange. Actually all devs use firefox for testing and developement. Something must beborked with your Firefox. Maybe some extension or setting or whatever. I'm using the webgui nearly exclusively with firefox and don't have issues. I rarely use something else just to test if it works in other browsers too.

hoba

I just tested captive portal at opt1 interface with a wrap using local user manager. Works like expected. Just a stupid idea, does your browser use a proxy?

danbutter

Not a stupid idea, but no.
I have to believe that it is a stupid issue though.

I have multiple workstations that I can use and none of them have issues with the internet or connecting to outside vpn…I just can't get the CP to work.

Does it look like I am doing anything wrong with the setup?

thanks for checking for me.

hoba

It looks ok. In general you need to use the interface IP of the captive portal enabled interface as DNS server for the redirect to work and to bring up the CP page. After authenticating at the CP page the firewallrules present for the interface will be applied. From what you did I don't see any obvious error. Maybe a reinstall would help. Is this a system that has been upgraded a lot of times already starting with a pretty old version?

danbutter

I actually tried two different systems one of which was. From back at .9xx something. But I never went past 1.0.1 with that one.
The current one I am using is using the latest snapsnot that sullrich posted. This box was a fresh install of 1.0.1.

I could burn a disc and try a new install.

Maybe tomorrow.

hoba

Please send me your config.xml to holger <dot>bauer <at>citec-ag <dot>de. Maybe some other feature like nat reflection or whatever is not playing well in the mix.</dot></at></dot>

danbutter

will do, but in the meantime I have even more weirdness to report.

Ok this box has 4 nics and therefore 2 OPT interfaces.
Just messing around I left the OPT1 that I had named CP alone. No changes at all.

I then enabled the OPT2 interface.
Gave it an IP of 192.168.33.1
went to the DHCP server put that IP as the dns and set a range from 192.168.33.22 to .55
Went to firewall > rules and this time set ANY rather than leaving it at TCP.
Plugged in the wireless and it worked!
Tried with computer and the crossover cable and it worked!

I thought great! it works, but…
I used a usb wireless adapter on my main computer. I would switch between them in network connections by disabling one and using the other one to test the wireless.

Well... when I went to switch back to the wired nic which should be LAN I got an IP from the OPT2 interface!
I tried to release and renew...same IP. I tried to use flushdns in between there...same IP.
I rebooted the machine...same IP.
I went to another PC on the network that still had a valid lease and got into the web interface and turned off the OPT2 interface...same IP.
I then turned it back on, went to the DHCP server for OPT2 and disabled it.

Now I can get an IP for the LAN as I am supposed to.

I'm starting to think my pfsense box is haunted.

sending the config in a couple mins here.

jeroen234

@danbutter:

Ok, I documented everything I did as I did it so that someone can hopefully tell me what I did wrong.

Ok then I then changed the name of the OPT1 interface to CP, changed it's IP to 192.168.11/24, enabled it and clicked on save.

Thanks for any help anyone can give me here.

i hope you meen 192.168.11.1/24

danbutter

yes, I did mean 192.168.11.1/24.

Good catch though.