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

    Can't ping or contact ADSL router from LAN

    Scheduled Pinned Locked Moved General pfSense Questions
    7 Posts 5 Posters 2.5k 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.
    • M
      mewsense
      last edited by

      I can ping my adsl routers (I have two) from the pfSense machine, but I cannot from my LAN. I'm not sure why, any ideas? My routers are 192.168.0.1, 192.168.1.1. Here are my firewall rules.

      Gateways

      1 Reply Last reply Reply Quote 0
      • jahonixJ
        jahonix
        last edited by

        The only allowed address to your Netgear is "Lan address" - which refers to your pfSense's LAN interface.
        There is no rule for others to ping there. I'd try dedicated ICMP/ping rules.

        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          Are your modems in bridge mode? It looks like they may not be.

          Steve

          1 Reply Last reply Reply Quote 0
          • P
            phil.davis
            last edited by

            Slightly off-topic - the 2nd rule only passes DNS UDP. Under some conditions DNS can use TCP, so you should make that pass UDP+TCP.
            The last rule pushes all traffic unmatched by a previous rule, into VPN gateway. That may be pushing traffic for the 192.168 WAN subnets. You will need ordinary pass rule/s prior to that for traffic you want to allow to the 192.168 WAN subnets.

            As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
            If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

            1 Reply Last reply Reply Quote 0
            • H
              heper
              last edited by

              your rule "access to netgear webgui" is set for TCP protocol traffic.

              pings or echo request->reply use the ICMP protocol.
              in other words … with that rule you shall never get pings to work.

              for testing set the protocol to ANY, and see if that helps

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                Assuming there is no extra interfaces, PPPoE trickery to be done the problem exactly as jahonix pointed out above. Your firewall rule allowing access to the modem only catches traffic from the pfSense LAN interface, hence you can ping it from the box itself. Change that rules source to 'LAN net' and you'll be good.
                Unless your LAN client is 10.0.0.61 in which case it should work.

                You may be falling foul of the negate rules. These are rules which 'negate' policy based routing for accessing local subnets and they use the system routing hence the default gateway. Your default gateway is the Netgear interface so it still should work. You can disable the negate rules though in System: Advanced: Firewall and NAT:

                Steve

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

                  Thanks everyone I created two new rules

                  TCP LAN net * -> Routers 80 (HTTP)
                  ICMP LAN net * -> Routers *

                  Works a treat

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