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

    Issue with changing over WAN connection

    Scheduled Pinned Locked Moved General pfSense Questions
    2 Posts 2 Posters 1.0k 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.
    • L Offline
      luke240778
      last edited by

      Hey, my current WAN connection is static, connected to a fiber connection.  As a failsafe i am trying to see how easy it will be to switch it over to another ADSL line.

      I am seeing DNS problems but can''t understand whats going wrong.  As far as i can see the only changes that i need to make is the IP and Gateway on the WAN interface, and the DNS servers on the General Setup page.  Am  missing something?  DHCP server has no DNS servers set, so it should just use the default ones on the General Setup.

      Am i wrong? or missing something?

      Problems i am seeing are:

      On Status > Gateways, the new one says online.. BUT computers on my LAN can ping 8.8.8.8 and so on, but can't open any www. sites, which to me means DNS problem.  But i dont see anywhere else on pfSense that i need to change any DNS settings.

      A second attempt and different results.. Gateway status says Online, but not even pfSense can ping it via IP or ping anything else on the www.

      Any ideas?

      1 Reply Last reply Reply Quote 0
      • W Offline
        wallabybob
        last edited by

        @luke240778:

        On Status > Gateways, the new one says online.. BUT computers on my LAN can ping 8.8.8.8 and so on, but can't open any www. sites, which to me means DNS problem.

        Unfortunately humans often translate a browser error message to "can't open site zzz" with significant information loss. The browser error report is almost always more informative than "can't open …"

        The problem could be upstream congestion, no access to the name server, broken upstream link between you and the hosts you attempted to access, ... The browser error report will likely give a clue to help identify a specific cause.

        @luke240778:

        A second attempt and different results.. Gateway status says Online, but not even pfSense can ping it via IP or ping anything else on the www.

        As above, giving the ping command and its response is almost always more informative than "can't ping".

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