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

    Client to client ping in same network

    Scheduled Pinned Locked Moved Firewalling
    4 Posts 2 Posters 475 Views 2 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.
    • S Offline
      sahand_it
      last edited by

      hello guys,
      I have a weird problem. I can ping my clients in LAN network from pfsense or my servers in my DMZ network, but I can't ping them from other machines in same LAN.

      I got destination unreachable error message

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

        @sahand_it said in Client to client ping in same network:

        but I can't ping them from other machines in same LAN.

        Pfsense has nothing to do with clients talking to each other. A device on say 192.168.1.x/24 does talk to pfsense to ping 192.168.1.y/24

        If your clients can not ping each other, it has nothing to do with pfsense. Unless your bridging on pfsense between 2 parts of the same L2.

        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 | Lab VMs 2.8, 25.07

        S 1 Reply Last reply Reply Quote 1
        • S Offline
          sahand_it @johnpoz
          last edited by sahand_it

          @johnpoz thanks john for your response.

          my device 192.168.1.x/24 can't ping 192.168.1.y/24 but I can ping 192.168.1.y/24 directly from my pfsense GUI, also I can ping it from 192.168.2.z/24 which is another device behind another pfsense interface. And sadly I don't know where to check this problem anymore...

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

            @sahand_it my bad, it turns out that the Access Point was at a faulty state and restarting it resolved the issue...

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