Authentication page reload



  • Hi, to me this seems so basic but for whatever reason I can not get it to work, I want to use  the captive portal for local user authentication, I have a test user setup and my network setup is this

    ISP –> PFSENSE --> SWITCH --> WAP's --> CLIENTS

    my subnet is 10.x.x.x with the gateway being 10.0.0.1, my DHCP scope is 10.0.100.1 to 10.0.255.254, I turn on the captive portal with local user authentication and when I go to browse I get presented with the page to login....cool so it's working like it should no? however when I go to login with the local user account I created it just reloads the page, no error out, just a straight reload, I've tried with a number of browsers to make sure it's not them ranging from IE9 to Opera 9, Chrome, Firefox, Safari, etc....however what is interesting is that although the captive portal page just refreshes and I can't get by it I can look at my PFSENSE gui and see that the local user is authenticated fine, it is pretty much the exact same issue as here

    http://forum.pfsense.org/index.php/topic,40196.0.html with the exact same behaviour as seen in his screencast,

    now what you guys should know is that normally I block everything on the LAN interface except specific ports to help thwart p2p traffic, however I've opened up port 8000, also just a test I went ahead and opened everything to see if it made a difference and it did not. also I've looked and looked for rouge DHCP servers as suggested in that other post and there is nothing else, and it I've also verified that I'm getting DHCP from the PFSENSE box in that I get the right domain and DNS servers passed down.

    any other suggestions on what may be effecting it? I'm on PFSENSE 2.0RC3 and up to todays build....I'm completely stumped here.

    Thanks in advance!



  • When the portal login page shows the second time can you then go directly to a site (say http://www.google.com) by typing the URL into the browser location box?

    Please post the source for your portal page. Perhaps you made a typo in a crucial element.



  • default PFSENSE captive portal page and I can not browse a page after authenticating, every page request brings me back to the captive portal login screen,

    if it's worth anything I have it enabled on my LAN interface.



  • I use captive portal on an OPTx interface. It worked fine on build 2.0-RC3-IPv6 (i386)
    built on Tue Jun 21 17:40:54 EDT 2011
    and now works fine for me on build 2.0-RC3 (i386)
    built on Wed Jul 20 01:31:15 EDT 2011

    What build are you using?



  • same just x64, OPT is really just the name, I called my LAN, I could call it OPT4 if I wanted.

    Does anyone know if you have to have both a default LAN and another OPT interface for it to authenticate properly?



  • The interface called LAN is different from other interfaces, at least in the default firewall rules. I don't know if this difference extends to captive portal, but the fact CP can be configured on LAN suggests any differences shouldn't extend to CP.

    What method of authentication are you using?

    Do you see a difference if you invoke one of the CP pass through methods e.g. allow your MAC address to pass through portal or your IP address)?



  • @wallabybob:

    The interface called LAN is different from other interfaces, at least in the default firewall rules. I don't know if this difference extends to captive portal, but the fact CP can be configured on LAN suggests any differences shouldn't extend to CP.

    What method of authentication are you using?

    Do you see a difference if you invoke one of the CP pass through methods e.g. allow your MAC address to pass through portal or your IP address)?

    I agree with the "LAN" interface statement, it should't effect it, as for the pass through methods those all work fine and allow me to browse however as we both know that more or less defaults the testing phase as I'll be automatically pushed through and not grabbed by the captive portal.



  • What authentication are you using?

    @support@optimalnetworks.c:

    as for the pass through methods those all work fine and allow me to browse however as we both know that more or less defaults the testing phase as I'll be automatically pushed through and not grabbed by the captive portal.

    Yes, I was wondering if you were seeing any other quirky behaviour.

    When you attempt to go to (say) http://www.google.com and the captive portal page appears what shows in the location bar of the browser?



  • I'm just using local user authentication which I test with Diagnostics –> Authentication and it works fine,

    as for the URL here is what shows up in the address bar;

    http://10.0.0.1:8000/index.php?redirurl=http%3A%2F%2Fgoogle.ca%2F



  • 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"


Log in to reply