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

    Connecting two different network in pfsense

    Scheduled Pinned Locked Moved General pfSense Questions
    6 Posts 2 Posters 10.6k 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.
    • T
      Tony
      last edited by

      Hi,

      I would like to know if it possible for pfsense to connect two or more different network. Here are the scenario in the same building:

      Company A is using 192.168.10.0 /24 subnet (using sonicwall as thier router, has it's own ISP)
      Company B is using 10.0.2.1 /24 subnet (using pfsense as thier router, has it's own ISP)

      What I want to accomplish is to have both network connect to each other, right now company B cannot access the company A network and vice versa company A cannot access the company B network.

      I am trying to setup one network card in pfsense and configure the network card as OPT2 with the Campany A subnet (192.168.10.12) and creating rules to allow access from OPT2 subnet going to pfsense LAN Subnet, and I also created Rule in LAN to have the source LAN Subnet  going to the OPT2 subnet.

      But no success can't ping the IP address of the company A subnet.

      Any help much greatly appreciated.

      Thank you.

      1 Reply Last reply Reply Quote 0
      • T
        Tony
        last edited by

        By the way, the OPT2 was physically connected to the switch of Company A.

        1 Reply Last reply Reply Quote 0
        • G
          Gob
          last edited by

          you need to put a static route on the sonicwall for the 10.0.2.0/24 network, using  192.168.10.12 for the gateway.
          that should get the pings back to the company B network instead of going off out to the internet through the sonicwall.

          g.

          If I fix one more thing than I break in a day, it's a good day!

          1 Reply Last reply Reply Quote 0
          • T
            Tony
            last edited by

            What about in the pfsense did I done a correct setup in pfsense? Do I still need to configure a static route in sonicwall or I can accomplish what I am trying to do without touching the configuration on sonicwall, just make a static route on pfsense?

            1 Reply Last reply Reply Quote 0
            • G
              Gob
              last edited by

              from the info you supplied, the pfsense setup should be ok, providing your rules are ok.
              the computers on the company A network can only talk directly to devices with a 192.168.10.xxx IP address. for all other IPs  they will forward requests to their configured gateway (the sonicwall).
              they know nothing about what lies beyond 192.168.10.12.
              your options are:
              1. add static route to sonicwall to bonce back requests for 10.0.2.xxx to 192.168.10.12

              2. add static routes to every computer in company A

              3. ditch the sonicwall ;D  . plug both ISP feeds into pfsnse and have pfsense as the gateway on both networks. gives you the ability to loadbalance your internet connections and provide failover for  both sites.

              If I fix one more thing than I break in a day, it's a good day!

              1 Reply Last reply Reply Quote 0
              • T
                Tony
                last edited by

                Sorry, that I have not reply to this for a while. If I am going to use the option 1 how do I physically connect both networks, I am guessing an ordinary patch cable would work by connecting it to pfsense OPT2 and the other end was connected to sonicwall available port. Is this how you connect to establish the connection?

                Thanks.

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