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

    pfSense doesn't route PING replies from one of subnets

    Routing and Multi WAN
    4
    4
    516
    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.
    • dimskraftD
      dimskraft
      last edited by

      I have the following topology

      3cd53e0c-3ba5-443e-8a94-a33b19b6f5ea-image.png

      From myhost computer I am trying to ping router1 and ping router2.

      During ping, I am doing tcpdump -n -i re? icmp and for pinging router1 I see both requests and replies in both re1 and re2. But while pinging router2 I see replies only in re3, but I see only requests in re2.

      How to explain this?

      V 1 Reply Last reply Reply Quote 0
      • V
        vandi @dimskraft
        last edited by

        005f6495-eebc-4711-a57b-35930c572b80-image.png

        I think I'm having a similar issue. I haven't done any packet traces yet, but I can ping from LAN1 to LAN2 but not from LAN1 to LAN3. I can get to both LAN2 and LAN3 externally, So I'm very confused as to why there is a blockage...

        I had a similar issue on an opnSense setup but wasn't impressed with the setup/configuration.

        Thanks!

        1 Reply Last reply Reply Quote 0
        • JonathanLeeJ
          JonathanLee
          last edited by JonathanLee

          You guys set up ACL for pings right to allow them? Run a tracert command and see when it stops, that should be the device with the configuration issue.

          Make sure to upvote

          1 Reply Last reply Reply Quote 0
          • M
            mcury
            last edited by mcury

            This is probably a routing issue.

            Both routers, router1 and 2, need a static route pointing to pfsense re1 and re2 ips respectively , saying that LAN is behind it.

            dead on arrival, nowhere to be found.

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