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

    Migration of pfSense and DNS issue

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    3 Posts 1 Posters 435 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.
    • C
      ccomp
      last edited by ccomp

      I have migrated my old pfSense 2.2 to a new 2.4. Quite on the same hardware (Alix).
      For that, I installed the new one with a fresh install, I exported the old configuration (Backup) and imported it on the new (Restore). I reassigned the interfaces to the good one and the new firewall is connected to the net. At this exact point, I have excatly the same rules on the old and the new.
      All seems fine on the new one, except I do not have any connection between inside and outside.
      After some tests, I realised the issue could be in the DNS names' resolution.
      If I ping 8.8.8.8 from inside, it is fine. Ping responds. But if I do ping www.google.com, I do not have any response : «From _gateway (192.168.0.1) icmp_seq=776 Destination Host Unreachable»

      If I try the same thing from the diagnostics/Traceroute, I have the resolution from WAN, but not from localhost or LAN.

      Do you know what could be wrong or how to find where it is wrong ?

      Many thanks.

      C 1 Reply Last reply Reply Quote 0
      • C
        ccomp @ccomp
        last edited by

        OK, here some updates :
        The DNS is OK. ping www.google.ch or fr.wikipedia.org resolves the name, but the IP address is unreachable.
        But IPv6 address seems OK from LAN (but not from localhost). I changed the DNS servers (to be sure), but nothing changed.
        I disabled the firewall (pfctl -d), nothing works, as expected.

        I do not see any rules which could explain why IPv6 works and IPv4 does not.
        Any idea ?

        1 Reply Last reply Reply Quote 0
        • C
          ccomp
          last edited by

          Problem solved : It was the default gateway for IPv4. It was using the IPv6 gateway.
          I think the new version applies a more strict policy.
          ;)

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