Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Sometimes Captive Portal doesn't work

    Scheduled Pinned Locked Moved Captive Portal
    4 Posts 3 Posters 3.1k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      Asterisk
      last edited by

      Hi, i've setup Captive Portal + IAS on Windows Server 2003, and it work well, but sometimes when browser starts, it seems looking for resolve site's name and stop, no splash screen appears
      Same result with internal auth, so it's not depending to the communication between pfSense and IAS.
      If now i'm stopping and restarting Captive Portal, it will work well again.
      I've pfSense 1.2 RC4, any suggestions?
      ps.

      No Squid, no multi wan
      DHCP on OPT1, and a firewall rule from OPT1 network to 192.168.1.1 port 8000 tcp (firewall address on OPT1)
      Bye!

      1 Reply Last reply Reply Quote 0
      • H
        hoba
        last edited by

        Anything in the systemlogs when that happens? Also note that the captive portal will not work if the pfsense can't resolve DNS. It first has to resolve the site that you want to hit (like google.com) before it redirects you to the captive portal page. If for some reason the pfSense doesn't get DNS from the servers it uses (system>general) it might appear that the captive portal is not working during that time.

        What I don't understand is the firewalrule that you put on OPT1. Is that the only rule you have there? How should it work at all this way?

        1 Reply Last reply Reply Quote 0
        • A
          Asterisk
          last edited by

          Yes, DNS is working, beacuse if captive portal it's disabled i can visit google.com without problems.
          And no, there are other rules, opt1 to wan (53 udp, 80 http, 433 http on WAN and tcp 8000 on 192.168.1.1)
          DNS server it's Windows server 2003, now a check system log.
          Thanks!

          1 Reply Last reply Reply Quote 0
          • A
            acction
            last edited by

            I suspect that your are not using the pfSense DNS forwarder.

            You can either remove your external DNS address from your captive portal DHCP configuration
            and use the DNS forwarder, or add the DNS address to the allowed addresses in the captive portal configuration.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.