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

    pfsense 2.7.0-BETA

    Scheduled Pinned Locked Moved CE 2.7.0 Development Snapshots (Retired)
    27 Posts 5 Posters 3.9k 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.
    • S
      stephenkwabena @stephenw10
      last edited by

      @stephenw10 said in pfsense 2.7.0-BETA:

      I see nothing here that indicates it's a DNS issue.

      Yes, I can access pfsense GUI using the domain name I resolved (https://firewall.mydomain.com) same LAN.

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        OK so when you're testing from a client that cannot reach the internet how does it fail? What error do you see?

        S 1 Reply Last reply Reply Quote 0
        • S
          stephenkwabena @stephenw10
          last edited by

          @stephenw10 said in pfsense 2.7.0-BETA:

          What error do you see?

          The only thing I get with a client connected via cable and wireless is "connected, no internet" but I can access the pfsense GUI

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Ok, so if you try to ping google.com from that client how does it fail?

            S 1 Reply Last reply Reply Quote 0
            • S
              stephenkwabena @stephenw10
              last edited by stephenkwabena

              @stephenw10 said in pfsense 2.7.0-BETA:

              Ok, so if you try to ping google.com from that client how does it fail?

              Screenshot from 2023-06-24 21-06-19.png

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                OK that indicates a DNS failure. 😉

                So check pfSense can resolve locally. Make sure the client is actually using pfSense for DNS.

                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by stephenw10

                  There are two threads for this with people contributing in each.

                  Lets's continue in the other thread: https://forum.netgate.com/topic/180907/pfsense-2-7-0-beta

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S stephenw10 referenced this topic on
                  • First post
                    Last post
                  Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.