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

    FRESH 2.2.6 install, no resolution

    Scheduled Pinned Locked Moved DHCP and DNS
    5 Posts 3 Posters 1.2k 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 Offline
      Samuel_R
      last edited by

      Hey all,

      I'm having a problem getting a fresh install of 2.2.6 to access the Internet…. Or even ping anything outside an IP address. I can ping my router. With the Pfsense box in place and can access it in a browser, but cannot access anything past it. If I remove the Pfsense box and connect directly to the router, I can surf as normal.

      I've checked cabling, tried multiple installs, (2.2.2 and 2.2.6)... But cannot seem to get it to work.

      All firewall rules are default to setup (anti lockout, default allow for IPv4 and IPv6)
      Wan side has block private networks and block Bogon networks (tried without these selected to see if that was the problem)

      Default Gateway is 192.168.1.20 (the router's ip)
      LAN interface has an ip of 10.102.1.1/24
      Wan interface ip is 192.168.1.10/24 with default gateway selected (using 8.8.8.8 for dns)
      (Allows me to ping Google.com, but not access it via browser)
      When using dhcp for wan interface, I have allow override selected on general setup.
      (Allows me to ping 216.58.214.206 but cannot ping Google.com or any other domain)

      1 Reply Last reply Reply Quote 0
      • S Offline
        Samuel_R
        last edited by

        Update: found that nap was turned off on the router and was reporting in as 2012 instead of 2016. I can now sometimes do a successful dns lookup from Pfsense, but still cannot access anything directly through a browser.

        Edited: seems lookup isn't working 100%. Have to perform 2-3 lookups to get a result and even after getting a result, can still get several failures before getting another successful lookup.

        Again… Everything this works 100% if I simply remove Pfsense from the architecture.

        1 Reply Last reply Reply Quote 0
        • johnpozJ Offline
          johnpoz LAYER 8 Global Moderator
          last edited by

          "When using dhcp for wan interface, I have allow override selected on general setup."

          Which has noting to do with using the resolver out of the box which is the default now.

          If your having dns issues, try the forwarder vs the resolver.

          An intelligent man is sometimes forced to be drunk to spend time with his fools
          If you get confused: Listen to the Music Play
          Please don't Chat/PM me for help, unless mod related
          SG-4860 25.07.1 | Lab VMs 2.8.1, 25.07.1

          1 Reply Last reply Reply Quote 0
          • S Offline
            Samuel_R
            last edited by

            Thanks johnpoz. Forwarding worked. Any ideas why resolver wouldn't?

            1 Reply Last reply Reply Quote 0
            • jimpJ Offline
              jimp Rebel Alliance Developer Netgate
              last edited by

              The resolver defaults to non-forwarding mode with DNSSEC enabled, so if your clock is not right or if you have any upstream DNS fiddling happening it can be touchy, though for most it's a more functional, safer, and secure default.

              Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

              Need help fast? Netgate Global Support!

              Do not Chat/PM for help!

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