Captive portal not redirecting to portal



  • I have installed 3 pfsense appliances with custom portal pages that work fine.

    My home setup does not work, I have researched and tried various settings.

    DNS forwarding, DNS resolver, dhcp on lan interface, 1st dns is lan ip, I may be missing something
    but when captive portal enabled, no page and no internet. Using default portal page

    Can anyone point me in the right direction

    Thanks



  • Hi,

    If you have 3 different setups, what are the differences ?

    Btw : just saying "it doesn't work" leaves us with a couple of billion possible solutions.
    I can't enter them all in one reply ;)



  • Thanks for responding

    I compared to working captive portals and all settings are the same

    Tried setting up on lan with no authentication and also local user manager using
    default portal pages, no pre or after authentication url, dns forwarder enabled, dhcp
    enabled on interface, dns 1 is pfsense 192.168.1.10

    I just don't see what could be wrong, browser just spins and no internet

    Please let me know what information you need to help ???



  • @Calling:

    …. dns 1 is pfsense 192.168.1.10

    By default, pfsense 192.168.1.1, not 10. Ok if you chose .254/Nver understood why people chose something in between.
    pfSense is your gateway to the net, right ?
    ?
    When the portal is activated, and you force a DHCP renew, does your device hook up get a IP (you can also check in the pfSense->DHCP log)
    If ths device is a PC, and you use the command
    ipconfig /all
    It has a IP ? It is in the IP range the pfsense DHCP server is using ?
    The gateway is ok ? (should be pfSense IP)
    DNS server ? (should be pfSense IP)

    What are your LAN firewall rules ?

    Did you check with https://doc.pfsense.org/index.php/Captive_Portal_Troubleshooting ?



  • I have it on 192.168.1.10 for convenience. I configure various devices on this pc
    and manufacturers like to use 192.168.1.1 as default. It allows me to plug the
    device into a switch and reach it without any configuration

    I brought up a page with portal enabled and did a dhcp renew. The logs showed
    successful and soon as i type in ipconfig /renew the portal page came up

    It did it once and I was unable to recreate?

    ip of pc is in DHCP range

    gateway entry ok

    Please see attachments, thanks














  • All this should be done on the device that want to connect to the captive portal :
    @Gertjan:

    …. and you force a DHCP renew, does your device hook up get a IP (you can also check in the pfSense->DHCP log)
    If this device is a PC, and you use the command
    ipconfig /all
    It has a IP ? It is in the IP range the pfsense DHCP server is using ?
    The gateway is ok ? (should be pfSense IP)
    DNS server ? (should be pfSense IP)

    Did you check with https://doc.pfsense.org/index.php/Captive_Portal_Troubleshooting ?

    Which of the firewall rules you mentioned above work for the captive portal ?



  • I did all the things you listed, still not working

    I have 4 dns entries in general, why does it show
    8 entries on dashboard? and does it matter the order
    they are shown as

    :)



  • @Calling:

    I did all the things you listed, still not working
    Negatif.
    My questions are not answered.

    What does a client device receive as getway, and DNS server when connecting to pfSense ?

    Did you use ans study this https://doc.pfsense.org/index.php/Captive_Portal_Troubleshooting and what were your findings ?

    What are the captive portal firewall rules (detail aliases) ?

    @Calling:

    I have 4 dns entries in general, why does it show
    8 entries on dashboard? and does it matter the order
    they are shown as

    127.0.0.1 is ok and normal.
    192.168.1.10 seems not needed to me.
    People like it that Google knows what they do, so 8.8.8.8, why not (they also install Chrome to copy their entire "internet consumption" to Google …ok, up to them ...).
    The others : well : why not.

    The DNS resolver will question the 13 "fixed" root world servers. And they will drill down my DNS requests



  • I seem to have found the problem

    I had no url redirects entered in captive portal, but I have
    secure site google as home page. I changed to http site
    and portal now works

    Thanks for your help


  • Netgate

    Testing captive portal to something like http://10.10.10.10/ eliminates both DNS and HTTPS as the issue.



  • I was unaware that testing to a certain ip would eliminate dns and https as an issue. I guess lack of knowledge on my part

    But it would seem that no matter what your home page is that the coding would still work when there is no url determined in the CP

    Just a thought


  • Netgate

    As long as it is not https and it is resolvable in DNS by the client, yes, any hostname will work.