Captive Portal troubles



  • ??? Well, I have an access point connected to an opt interface of the pfsense box..  When testing the captive portal I connect via the wireless, have an IP address assigned by teh pfsense dhcp server ok.  However, the captive portal html page will not load.  Regardless of what url i put in the broser just times out after a short time.  Any sugestions?  I created a firewall rule to allow me to access the WAP's WEBGUI from the lan, and that works fine.  Anything else i need to do to get the portal to server HTML tho?  Thanks for any sugestions.  I tried rebooting the pfsense box but with no luck.

    Thanks :)  DAn



  • @TOBoiDan:

    ??? Well, I have an access point connected to an opt interface of the pfsense box..  When testing the captive portal I connect via the wireless, have an IP address assigned by teh pfsense dhcp server ok.  However, the captive portal html page will not load.  Regardless of what url i put in the broser just times out after a short time.  Any sugestions?  I created a firewall rule to allow me to access the WAP's WEBGUI from the lan, and that works fine.  Anything else i need to do to get the portal to server HTML tho?  Thanks for any sugestions.  I tried rebooting the pfsense box but with no luck.

    Thanks :)  DAn

    Make sure DNS is entered in System -> General



  • @sullrich:

    Make sure DNS is entered in System -> General

    I've tried manually entering the DNS addresses or allowing the PPPoE setting to specify them and it still times out without loading the html uploaded on the portal setup page….  Do i need to create and special firewall rules to allow hosts on the opt interface to load the file with the captive portal page? I originally tried with no user created HTML and the default page didn't load either..?



  • Also make sure you are using the firewall's dns forwarder as the ip.  It hands this out by default but you can override dns on some clients.

    Also allow the client to surf out in the firewall rules for the interface.

    Final thing is to reboot the firewall if all else fails as one final test.



  • @sullrich:

    Also make sure you are using the firewall's dns forwarder as the ip.  It hands this out by default but you can override dns on some clients.

    Also allow the client to surf out in the firewall rules for the interface.

    Final thing is to reboot the firewall if all else fails as one final test.

    This thing is driving me nuts lol  >:(
    The network config on the client shows only the DNS Forwareder address.  I have added a rule allowing http traffic to and from the Captive interface.  Failing that I rebooted the box once again.  I flushed the dns resolver on my laptop and connected to the WAP on the captive protal, which conected and receives a DHCP config just fine. Any url just times out still without displaying teh captive protal's html that was uploaded..  :'(





  • @sullrich:

    Make sure you are on the latest version:

    http://www.pfsense.com/~sullrich/1.0-BETA1-TESTING-SNAPSHOT-2-8-06/

    Updated firmware, still no change….



  • I have no idea what you are doing wrong but I just tested it here.  Works fine.

    Take a look at http://www.pfsense.org/mirror.php?section=tutorials/cp_config/radius_win2k3.htm if you haven't seen it already.



  • @sullrich:

    I have no idea what you are doing wrong but I just tested it here.  Works fine.

    Take a look at http://www.pfsense.org/mirror.php?section=tutorials/cp_config/radius_win2k3.htm if you haven't seen it already.

    ???  I watched the turtorial before i tried to set it up the first time. I had it working on monowall a while back, which is why i'm sure why it dun work now (despite a different box).    Attached is my config.xml with usernames, passwords and the like parsed out of it if its of any use.

    Thanks for your help :)

    config.txt



  • if i look trouw youre config i see as system dns ( the one from youre isp)
    <dnsserver>192.168.1.1</dnsserver>

    and then by dhcp server again 192.168.1.1
    so you have for wan and lan the dnsserver 192.168.1.1
    try chancing the system dns server to a real dnsserver from youre isp



  • :D  finally got it working…  created a firewall rule to permit dns traffic... seems to work ok now :)  Thanks to everyone for their sugestions  :-*


Locked