Captive Portal Problems
-
Let me start by saying hello to all. I have been running Psfense since first of 2013 with the set it and forget it and has worked like a champ up until about a couple months ago and it is first inline from ISP and behind it is a server with Unifi loaded and then goes across property to 128 ubnt AP's so this is what happened the internet went down and found that the pfsense box with CP turned on would drop internet but when cut off the internet worked fine, cut it on the internet went down and so on so I loaded the 2.2.6 version a couple nights ago on a different server to set in place and have everything working but CP the login page and when I turn CP on with the new version the internet stays up unlike the old. I connect to the access point and pull up a webpage and the login page comes up and then type in the password and it hangs every time and times out with my device and others. I log into the server by HTTPS and if I cut CP off and on when I'm working on it remotely then it drops off after 4 cutoff and on's of CP I have to reboot pfsense to get back into it by HTTPS but I can always ping the IP address of it at anytime. Has anyone had this problem or know what I might be over looking? I'm using the standard dhcp server on pfsense and not radius. Any suggestions would be greatly appreciated if I have given enough info. Thanks
-
This is an easy one.
The "enter" key on your keyboard is broken.
-
No if it was the enter key broken it would never time out.
-
You're going to have to give more information than "drops internet"
Captive portal clients have to be able to resolve DNS so the browser makes a connection on x.x.x.x:80 so there's something to intercept to display the portal page.
What happens with the portal on if you enter http://10.10.10.10 in a browser?
Can you bring up the portal using the proper :8XXX address and port?
-
You're going to have to give more information than "drops internet"
…..Whooo.
So you read the entire one-liner … ?
-
maybe this could help:
https://forum.pfsense.org/index.php?topic=105558.0
Let me start by saying hello to all. I have been running Psfense since first of 2013 with the set it and forget it and has worked like a champ up until about a couple months ago and it is first inline from ISP and behind it is a server with Unifi loaded and then goes across property to 128 ubnt AP's so this is what happened the internet went down and found that the pfsense box with CP turned on would drop internet but when cut off the internet worked fine, cut it on the internet went down and so on so I loaded the 2.2.6 version a couple nights ago on a different server to set in place and have everything working but CP the login page and when I turn CP on with the new version the internet stays up unlike the old. I connect to the access point and pull up a webpage and the login page comes up and then type in the password and it hangs every time and times out with my device and others. I log into the server by HTTPS and if I cut CP off and on when I'm working on it remotely then it drops off after 4 cutoff and on's of CP I have to reboot pfsense to get back into it by HTTPS but I can always ping the IP address of it at anytime. Has anyone had this problem or know what I might be over looking? I'm using the standard dhcp server on pfsense and not radius. Any suggestions would be greatly appreciated if I have given enough info. Thanks
-
Derelick
I can get to portal page since I down graded to 2.2.4 from 2.2.6 with no problems. Once the portal page is up I type in the password and it hangs up and times out I just can't get it past the portal page for some reason. I have it set to use password only to authenticate and then it should force them to our company webpage.
-
I have it set to use password only to authenticate and then it should force them to our company webpage.
What "password only" setting is this?
How about you set it completely as the default without any custom stuff, get it working with "no login required" then when you customize and it breaks you can blame yourself instead of the portal.
-
…. I have it set to use password only to authenticate and then it should ....
What about detailing your setup ?
Your 'password only' is new to me.edit : Direlict asked the same thing - same moment.
-
Okay I did set CP up to start off by using the default pfsense and page popped up and put in username and password and hung up the same way it is now just by using the password only through our custom page. I am use to Untangle and can set it up with no problems in which we use on our Corp network. The Pfsense box may have something that isnt setup right by all means and it can be blamed at me so everyone can get that out of the system I am just asking if anyone would no why it hangs because I'm thinking it is a DHCP resolver/Forwarder or something on that end because CP page hits the screen pretty quick once you connect to AP's. I am also using the DHPC server on Pfsense.
-
If you do not get an address it's DHCP - nothing to do with captive portal
If you cannot resolve names, this might be because you are not passing through necessary name servers in captive portal. hosts need to be able to resolve names if you want browsers going to www.domain.com to bring up the portal.
I have probably 8000-15000 different devices going through Captive Portal every week. It works fine if configured correctly.
You are going to have to systematically go through the steps necessary for CP to function and find the specific failure before we (or at least I) can help you.
-
If you do not get an address it's DHCP - nothing to do with captive portal
If you cannot resolve names, this might be because you are not passing through necessary name servers in captive portal. hosts need to be able to resolve names if you want browsers going to www.domain.com to bring up the portal.
I have probably 8000-15000 different devices going through Captive Portal every week. It works fine if configured correctly.
You are going to have to systematically go through the steps necessary for CP to function and find the specific failure before we (or at least I) can help you.
Thanks Derelict I have found the problem and it was the Wan and the Lan had some checks that should not have been checked and it was the bottom 2 that refuses bogons and the other above it. I unchecked them and then all went well quick and hope it helps someone else if they have the same problem. I can now type in password only on the custom page and no more hanging and timing out off to the world web. Thanks for your patience with me even though I know I didn't explain very well but like I told yawl I'm totally new to pfsense. I did go back and use the default pfsense portal page like you ask me to and was still no good until I unchecked them boxes.
