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

    Captive Portal: no login screen

    Scheduled Pinned Locked Moved Captive Portal
    16 Posts 6 Posters 13.4k 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
      axscode
      last edited by

      Just my 2 cents.

      1. Enable DNS Forwarding
      2. Under DHCP Server
        Gateway Address = LAN Address
        DNS 1 = LAN Address
        DNS 2 = Blank

      You may now renew using your dhclient or ipconfig /renew (on win).

      Also, try disabling squid proxy just for testing, and if there's an assigned proxy for your browser.

      Regards.

      Regards

      1 Reply Last reply Reply Quote 0
      • B
        Burken
        last edited by

        I tryd that.. dident help.. even did a hard reboot on my pfsense…
        :(

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

          Can you share your hardware specs?

          And can you reinstall your pfsense?

          • use default configuration, but only editing your LAN and WAN. and get internet connection working

          • enable captive portal.

          • dont add any packages yet, and dont enable traffic shapings and all sorts of that, just the default.

          • if you get captive portal working, by then you'll add one by one what you need so that you will know whats interfering with CP.

          So far my new installation works perfectly
          – with or without radius

          packages

          • with bandwidthD
          • with IMSpector
          • with Dashboard

          Regards

          1 Reply Last reply Reply Quote 0
          • M
            mrvanity
            last edited by

            @axscode:

            Just my 2 cents.

            1. Enable DNS Forwarding
            2. Under DHCP Server
               Gateway Address = LAN Address
               DNS 1 = LAN Address
               DNS 2 = Blank

            You may now renew using your dhclient or ipconfig /renew (on win).

            Also, try disabling squid proxy just for testing, and if there's an assigned proxy for your browser.

            Regards.

            I had the same problem.The login page wouldn't appear and i had to manually navigate to http://ip:8000.
            The problem existed from the 1.2.3 RC's to the final version.
            As DNS servers on the DHCP I had DNS from Opendns.
            I removed the Open DNS servers from the DHCP page leaving it blank (the DNS forwarder is enabled) and everything works like a charm!!!

            Thanx axscode!!!

            1 Reply Last reply Reply Quote 0
            • B
              Burken
              last edited by

              I use

              My pfsense has 7 Interfaces enabled..
              WAN  - DHCP from ISP
              WAN1  - DHCP from ISP
              WAN2  - DHCP from ISP
              WAN3  - DHCP from ISP
              WAN4  - DHCP from ISP
              LAN  - 192.168.1.0/24
              GUEST - 192.168.0.0/24 - Captive Portal Enabled - DHCP Enabled. No DNS, GW edited. Interface ip 192.168.0.1

              Guest Firewall Rules:
              Allow
              Proto:
              *
              Source:
              Guest NET
              Port
              *
              Desti
              *
              Port
              *
              Gateway
              LoadBalance

              (and yes i have tryd without loadbalance rule)

              Packages installed:
              bandwidthd
              phpSysInfo
              rate

              ipconfig /all from computer connected to GUEST:
                Anslutningsspecifika DNS-suffix . : burken.biz
                Beskrivning . . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P) Family PCI-E
              Gigabit Ethernet NIC (NDIS 6.0)
                Fysisk adress . . . . . . . . . . : 00-23-8B-A8-DE-57
                DHCP activated. . . . . . . . . . : Ja
                Autokonfiguration activated. . . : Ja
                IPv4-adress . . . . . . . . . . . : 192.168.0.49(Standard)
                Nätmask . . . . . . . . . . . . . : 255.255.255.0
                Lånet erhölls . . . . . . . . . . : den 12 januari 2010 17:35:08
                Lånet upphör. . . . . . . . . . . : den 12 januari 2010 19:35:08
                Standard-gateway. . . . . . . . . : 192.168.0.1
                DHCP-server . . . . . . . . . . . : 192.168.0.1
                DNS-servrar . . . . . . . . . . . : 192.168.0.1
                NetBIOS över TCP/IP . . . . . . . : activated

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

                @mrvanity, Glad to hear that it works for you..

                @Burken, I am sorry mate, havent tried CP on multiple WANs

                Regards

                1 Reply Last reply Reply Quote 0
                • M
                  mrvanity
                  last edited by

                  @axscode:

                  @Burken, I am sorry mate, havent tried CP on multiple WANs

                  My setup consists on 2 wan connections and it works ok.
                  (see my setup here)
                  http://forum.pfsense.org/index.php/topic,16338.msg84899.html#msg84899

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

                    Well done mate. maybe you can share with burken some of your notes.

                    Regards

                    1 Reply Last reply Reply Quote 0
                    • B
                      Burken
                      last edited by

                      I dont think the multiple wan is the problem.
                      I can just change so everyting goes out to the normal WAN interface.. I will still never get navigated to the login screen…

                      I have 192.168.0.1 as DNS server..

                      :(

                      1 Reply Last reply Reply Quote 0
                      • M
                        mrvanity
                        last edited by

                        One of the differences i see in your setup is that you use a wlan interface.
                        My LAN interface ends up to a structure of ~50 AP's.
                        If it is possible, try to use an ethernet AP and and test again..

                        1 Reply Last reply Reply Quote 0
                        • B
                          Burken
                          last edited by

                          I don't use WLAN.
                          GUEST is FastEthernet-RJ45 to my neighbors computer.

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