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

    Its not possible to ping host between

    Scheduled Pinned Locked Moved Firewalling
    4 Posts 4 Posters 576 Views 4 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.
    • J Offline
      jhave
      last edited by

      Hello,

      I do not understand why this work. I have created a IOT network for some of my devices but they need access to my NAS on 192.168.1.205 but im not able to ping i from my IOT network. There are a rule for it but its as its only work from the IOT -> LAN but not reverse.

      My LAN rules:
      88a7cb94-d228-412c-95c5-1d5a137173ca-image.png

      My IOT rules:
      a4d618c2-d089-46bf-9d85-420b807c5426-image.png

      The log from the rule from IOT to 192.168.1.205 (on the LAN network)
      b4e7035f-3e8d-4bd4-882d-8a12e51c2e2d-image.png

      Some there can tell me what i do wrong as i understand do pfsense automatic create the reverse rule for it?

      M J 2 Replies Last reply Reply Quote 0
      • M Offline
        mcury Rebel Alliance @jhave
        last edited by

        @jhave First rule in the IOT tab doesn't need to exist, connections within the same broadcast domain goes through the switch and not through the gateway.
        Check your NAS firewall, its probably blocking connections from the IOT network.

        dead on arrival, nowhere to be found.

        1 Reply Last reply Reply Quote 0
        • J Offline
          Jarhead @jhave
          last edited by

          @jhave In addition to the above, use the packet capture in diagnostics.
          Makes troubleshooting easy.

          1 Reply Last reply Reply Quote 0
          • M Offline
            MichaelCropper
            last edited by

            Based on a recent similar issue, I'd also recommend taking a look at the inbound firewall rules on the NAS. I had a similar problem recently where ping wasn't working and the summary was that it was caused by the destination machine blocking inbound ICMP traffic (the protocol that ping use under the hood) https://www.contradodigital.com/2022/07/25/how-to-troubleshoot-ping-icmp-not-working/

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