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

    Can't see Captive portal login page

    Scheduled Pinned Locked Moved Captive Portal
    5 Posts 2 Posters 1.7k 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.
    • K
      KaruK
      last edited by

      Hello everyone, a newbie to pfSense, so please be gentle :)

      I installed pfSense 2.3.2 64-bit to one pc which have 2 network interfaces.
      I configured WAN and LAN interfaces, DHCP (works only for opt1 interface), DNS (enabled as DNS forwarder).
      Also I created on VLAN interface (opt1 - 192.168.12.1/24).

      I also configured a Level 3 switch for connecting pfSense pc and test pc's.
      I also created firewall rules for LAN and OPT1

      Then I tested Internet connection over VLAN interface. I got right IP address (192.168.12.30) from DHCP and
      internet connection works well. I can read difference webpages.

      Now I configured captive portal (uses opt1 interface), users and vouchers.
      When I opened my browser (homepage is http://www.google.com) - I only see message - cannot open webpage..ˇ
      I checked that I got right IP address (192.168.12.30) from DHCP.

      I used IE and Google Chrome browsers but I didn't see captive portal login page.

      I checked the conf but I don't discovered something wrong.
      Should I create my own login page? I understood that pfSense has its own built-in webpage for logging via captive portal.
      Or did I something wrong?

      Can someone clarify this for me

      1 Reply Last reply Reply Quote 0
      • GertjanG
        Gertjan
        last edited by

        @KaruK:

        I checked that I got right IP address (192.168.12.30) from DHCP.

        What was the IP-DNS you got ?
        Gateway ?
        (both should be 192.168.30.1 == OPT1 = "pfSEnse").

        You really deactivated the pfSEnse DHCP-server from LAN ?

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        1 Reply Last reply Reply Quote 0
        • K
          KaruK
          last edited by

          From DHCP I got:
          IP: 192.168.12.30
          IP-DNS - 8.8.8.8
          Gateway - 192.168.12.1

          I didn't see any reason for why I must use DHCP for LAN interface. It has static IP address 192.168.30.10.
          I want to use VLAN 12 for quests. I don't want they use net 192.168.30.0/24 resources.
          Interface OPT1
          192.168.12.1 / 24
          DHCP server range 192.168.12.30 to 12.254

          Interface LAN
          192.168.30.10 / 24

          Interface WAN

          192.168.0.219 / 24
          Gateway 192.168.0.1

          Do you mean that VLAN users must get gateway address 192.168.30.10 from dhcp server?
          If I use VLAN 12 without captive portal all work perfectly.

          1 Reply Last reply Reply Quote 0
          • GertjanG
            Gertjan
            last edited by

            @KaruK:

            IP-DNS - 8.8.8.8

            and this IP is allowed to pass through (udp and tcp) ont the OPT1 (captive portal) interface ?

            Normally, you should use the DNS resolver (not forwarder) on the pfSense box. So your clients would see 192.168.12.1 as a gateway and DNS server.
            This DNS server (pfSense) will be your "DNS cache" and he will ask 'above' if needed  - even 8.8.8.8 (Google) if you instructed it to do so.
            This means : no settings to change, the captive portal works 'out of the box'.

            Gateway LAN : nothing to do with your question, but why change the default value (192.168.1.1) to .10 ?
            (never understood why people change that value, it's .1 or .254 - never something in the middle - it your gateway after all.)

            No "help me" PM's please. Use the forum, the community will thank you.
            Edit : and where are the logs ??

            1 Reply Last reply Reply Quote 0
            • K
              KaruK
              last edited by

              Thank you Gertjan

              It seems that reconfiguring DNS (forwarder –> resolver) and removing 8.8.8.8 helped.
              Problem is solved.

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