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

    No route to host / Cannot resolve: Host name lookup failure

    Scheduled Pinned Locked Moved Firewalling
    4 Posts 2 Posters 549 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.
    • R
      RaulChiarella
      last edited by

      Hello!

      I'm on a fresh install of pfSense, plugged in directly into my not managable switch.

      I also have other devices on the same switch working just fine...
      Well, i configured the pfSense Firewall to use the IP 192.168.17.150 and the gateway is 192.168.17.254 (My switch) - The same configuration worked well on my Zabbix (192.168.17.16) and my computer (192.168.17.20)

      I also configured another pfSense a few days ago and i didnt had this problem...

      Does someone knows what can fix this? Do you came across this situation? If yes, how did you resolve it?

      Thank you very much!

      KOMK 1 Reply Last reply Reply Quote 0
      • KOMK
        KOM @RaulChiarella
        last edited by

        @raulchiarella You will need to provide more details about your network setup.

        i configured the pfSense Firewall to use the IP 192.168.17.150 and the gateway is 192.168.17.254 (My switch)

        Is that pfSense WAN or LAN? If LAN, you shouldn't specify a gateway. If WAN, why would your gateway be your switch instead of your modem?

        R 1 Reply Last reply Reply Quote 1
        • R
          RaulChiarella @KOM
          last edited by

          @kom said in No route to host / Cannot resolve: Host name lookup failure:

          @raulchiarella You will need to provide more details about your network setup.

          i configured the pfSense Firewall to use the IP 192.168.17.150 and the gateway is 192.168.17.254 (My switch)

          Is that pfSense WAN or LAN? If LAN, you shouldn't specify a gateway. If WAN, why would your gateway be your switch instead of your modem?

          Hello! Its OK, i was behind another subnet. Thats why my WAN isnt my modem!

          The problema was the cable, can u believe it?
          The CABLE!! I made another one and it fixed my problem.

          KOMK 1 Reply Last reply Reply Quote 0
          • KOMK
            KOM @RaulChiarella
            last edited by

            @raulchiarella I can definitely believe it. Another guy had a cable problem here (sendto: errors IIRC) just a few days ago. It's more common than you think.

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