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

    Routing between networks

    Scheduled Pinned Locked Moved Routing and Multi WAN
    5 Posts 2 Posters 1.0k 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
      Modivion
      last edited by

      Hello guys,

      So i've set up a PfSense box, all going well so far. I have 4 interfaces.

      • WAN1 DHCP
      • LAN 192.168.10.1/24
      • WAN2 PPPOE
      • LAN 192.168.20.1/24

      I would like clients on the 192.168.10.1/24 network to be able to talk to clients on the 2nd LAN 192.168.20.1/24.

      However, if I ping a client now, it gets timed out. I have checked firewall logs, and nothing is showing blocked there.

      Am I missing something here?

      Thanks guys.

      Roy

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

        Gotta add that I can actually ping and access pfsense through 192.168.20.1.

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

          I guess you have the default "allow all" rule on LAN. That should be all that is needed.
          I see you have multi-WAN. If you have policy-routing rules that feed all traffic into a gateway group, then you will need a rule before that to pass source LAN1 destination LAN2 gateway none - otherwise that local traffic will get forced out some WAN by the policy-routing.
          Or it might be a Windows device on LAN2 that has a firewall that will not answer "ping" from outside its own subnet.

          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
          • M
            Modivion
            last edited by

            Changed the gateway on LAN 1 to default and that fixed my problem.

            Thanks again for the help!

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

              That fixes the problem you were having between LAN1 and LAN2.
              But now all the LAN1 internet traffic will just go out the default gateway. If you were wanting failover or outbound load balancing then you will have to be a bit more fancy with the rules - 1 to pass local traffic, and the next to send the rest to a gateway group.

              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
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.