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

    Is there a "CP for DumME Guide"?

    Scheduled Pinned Locked Moved Captive Portal
    16 Posts 5 Posters 1.8k 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
      kcallis
      last edited by

      My AP is on the OPT1 interface. All of the clients get their address from the OPT1 interface.

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

        Maybe my issue is with the DNS resolver??? I have my access point using DNS on the pfSense machine. Under the DNS Servers in the OPT1 DHCP server, I have left the DNS servers blank, and under General Setup, I have the google servers listed? What is suppose to be the proper setup? Since moving into using DNS Resolver, I think I have screwed everything up…

        1 Reply Last reply Reply Quote 0
        • D
          doktornotor Banned
          last edited by

          Point the DHCP clients to the pfSense box for DNS.

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

            That is what I have in play. The clients are getting their address from the pfSense, so I am assuming that I have things incorrect on the pfSense.

            1 Reply Last reply Reply Quote 0
            • D
              doktornotor Banned
              last edited by

              You just told us above that "Under the DNS Servers in the OPT1 DHCP server, I have left the DNS servers blank". Point the clients explicitly to the interface address of the captive portal. Don't leave things blank. Pointing people to Google DNS (which is not whitelisted in the portal) via some heuristics black magic behind the scenes will NOT work.

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

                May be I am not being clear.  From the Bullet stand point, the AP uses dhcp relay for the clients to get address from pfSense. The Bullet's DNS servers (or actually server) is pointed to 192.168.100.1 (both gateway as well as DNS/DHCP).

                [

                ![Bullet Bridge.png](/public/imported_attachments/1/Bullet Bridge.png)
                ![Bullet Bridge.png_thumb](/public/imported_attachments/1/Bullet Bridge.png_thumb)
                ![DHCP Wifi server.png](/public/imported_attachments/1/DHCP Wifi server.png)
                ![DHCP Wifi server.png_thumb](/public/imported_attachments/1/DHCP Wifi server.png_thumb)
                ![DNS Resolver.png](/public/imported_attachments/1/DNS Resolver.png)
                ![DNS Resolver.png_thumb](/public/imported_attachments/1/DNS Resolver.png_thumb)
                ![General Setup.png](/public/imported_attachments/1/General Setup.png)
                ![General Setup.png_thumb](/public/imported_attachments/1/General Setup.png_thumb)
                Firewall_Rules_WiFi.png
                Firewall_Rules_WiFi.png_thumb

                1 Reply Last reply Reply Quote 0
                • D
                  doktornotor Banned
                  last edited by

                  1/ For the last time, since I already pointed that out twice and it's getting a bit ridiculous. Do NOT leave the DNS Servers in WiFi's DHCP configuration blank. Point the clients explicitly to 192.168.100.1.
                  2/ Your Outgoing Network Interfaces configuration for the DNS resolver is completely wrong. You will get no resolution whatsoever via the internal interfaces. Leave that at All.

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

                    Thank you for the last time! I forgot to apply the changes and so I never did I get have that change working… As for the DNS Resolver, I have both the Outgoing and Ingoing all set as ALL... Or am I missing something else?

                    ![DNS Resolver.png](/public/imported_attachments/1/DNS Resolver.png)
                    ![DNS Resolver.png_thumb](/public/imported_attachments/1/DNS Resolver.png_thumb)

                    1 Reply Last reply Reply Quote 0
                    • DerelictD
                      Derelict LAYER 8 Netgate
                      last edited by

                      @kcallis:

                      May be I am not being clear.  From the Bullet stand point, the AP uses dhcp relay for the clients to get address from pfSense. The Bullet's DNS servers (or actually server) is pointed to 192.168.100.1 (both gateway as well as DNS/DHCP).

                      This makes zero sense.  If your bullet is in bridge mode there is absolutely no reason to use a dhcp relay.  That function is to get across layer 3/broadcast domain boundaries and pfSense DHCP doesn't even support it yet.  A layer 2 device will not gave a gateway.  Or at least if it does it's only for access to the AP interface itself, and will have nothing to do with client traffic.

                      It also makes no difference what the bullet is using for DNS.  That will only impact what the BULLET ITSELF uses to resolve names, unless you have everything set layer 3 and your clients are really using the bullet to resolve names, which would be wrong.

                      Put EVERYTHING you want to go to the clients on the pfSense DHCP server.  If your clients are using something else for a DHCP server you're doing it wrong.

                      Chattanooga, Tennessee, USA
                      A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                      DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                      Do Not Chat For Help! NO_WAN_EGRESS(TM)

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

                        After doing all sorts of things, it would seem that all that I needed to do was make a rule allowing UDP port 53 on the OPT1 and everything became mellow. I am not sure why I would have to do a rule on the OPT1 but not on the LAN, but it is working.

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