Portal Captive does not have login



  • My captive portal from my LAN network is not working, configured, reconfigured and does not ask for user login or password. I made basic settings nothing of RADIUS or something advanced, when I enable it my LAN network does not browse and asks neither password nor user. What can it be ?

    Version 2.4.2



  • You mean clients do not get redirected to the captive portal?



  • Do you have DHCP enabled on LAN ?
    Do you have dns resolver/ forwarder enabled on LAN ?
    Are your clients set to pfSense as their default gateway?
    Are your clients set to send/ receive DNS requests from you pfSense?(unless of domain)



  • @jaspras:

    Do you have DHCP enabled on LAN ?
    Do you have dns resolver/ forwarder enabled on LAN ?
    Are your clients set to pfSense as their default gateway?
    Are your clients set to send/ receive DNS requests from you pfSense?(unless of domain)

    Do you have DHCP enabled on the LAN?

    Yes

    Do you have the dns resolver / dispatcher enabled on the LAN?

    Yes

    Are your clients configured for pfSense as your default gateway?

    Yes, default gateway and PFsense

    Are clients configured to send / receive DNS requests from your domain provider?

    DNS and configured in PFSENSE itself, DNS addresses and OPEN DNS 208.67.222.222



  • @AYSMAN:

    You mean clients do not get redirected to the captive portal?

    Yes, clients do not have the login screen of the capitve portal, where I can not enter the user and password to access the internet. When you disable the capitve portal they normally navigate


  • Netgate

    Are clients configured to send / receive DNS requests from your domain provider?

    DNS and configured in PFSENSE itself, DNS addresses and OPEN DNS 208.67.222.222

    What?

    When the device is online and NOT through the portal, what are the DNS servers the devices are configured to use?

    They MUST be able to resolve names before going through the portal.

    If you have configured name servers in the CP interface's DHCP server, those addresses must also be specified in the Allowed IP Addresses in the captive portal configuration.

    A quick test is to tell a client to navigate to http://10.10.10.10/

    If that works you are probably looking at a DNS issue.



  • Derelict nailed it…