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

    LAN machines "destination host unreachbale" can't ping.

    Scheduled Pinned Locked Moved Firewalling
    4 Posts 3 Posters 288 Views 3 Watching
    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.
    • N Offline
      norcimo
      last edited by

      Greetings, I'm a newbie.

      Happy to join the family.

      Ok. Installed and running. But the machines on the LAN can not ping or see each other. I run ADVANCE IP SCANNER on a server and it returns 2, the pfSense machine and a server I GOOGLED desktop onto to reach the WEBGUI of pfSense. (itself).

      WAN: 192.168.1.X DHCP to my cable modem.

      LAN : 10.0.0.X DHCP

      All machines have access to the internet, but from the server machine I can't ping them nor access the WEBGUI of each machine which have been configured.

      The firewall has default lan to any rule enabled.

      help please?

      S johnpozJ 2 Replies Last reply Reply Quote 0
      • S Offline
        SteveITS Rebel Alliance @norcimo
        last edited by

        @norcimo pinging between LAN devices on the same network doesn’t go through the router. Firewall on the devices?

        Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
        When upgrading, allow 10-15 minutes to reboot, or more depending on packages, and device or disk speed.
        Upvote 👍 helpful posts!

        N 1 Reply Last reply Reply Quote 0
        • N Offline
          norcimo @SteveITS
          last edited by norcimo

          @SteveITS Thanks for the reply.

          They are miners. With a simple WEBGUI on port 80 . I can't even get on them from the server which is on the same LAN. Thats the behaviour I see...wierd.

          Maybe I screwed up. Going to use the Wizard.

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

            @norcimo yeah as mentioned pfsense has zero to do with talking devices on the same network.. host unreachable for something on your own network points to not getting the mac address back from an arp..

            example if I just ping some IP that I know there is no device on.

            $ ping 192.168.9.42
            
            Pinging 192.168.9.42 with 32 bytes of data:
            Reply from 192.168.9.100: Destination host unreachable.
            Reply from 192.168.9.100: Destination host unreachable.
            Reply from 192.168.9.100: Destination host unreachable.
            Reply from 192.168.9.100: Destination host unreachable.
            
            Ping statistics for 192.168.9.42:
                Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
            

            Are your devices wireless/wired - could have AP isolation set? Where you don't allow clients to talk to each other. Wired could be a private vlan setup on the switch.

            Normal layer3 firewalls don't block arp.. So host unreachable is not what you would see, you would just see a timeout.

            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, 25.07.1

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