Navigation

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

    Additional private routed subnets

    Firewalling
    3
    5
    1294
    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.
    • C
      charlien last edited by

      I work out of my house and have a "home" network that is 192.168.50.x/24. I have a layer 3 switch that routes to my "business" network 172.16.0.0/24. The reason for this is both networks need their own DHCP server and I frequently pack up my business network and take it on the road. When they are in my home I want the networks to be able to see each other and both access the Internet. Last time I tried to set up PFSense I had issues with Internet access on my business network and interLAN routing. I didn't have a lot of time and could not resolve it without the fear that I was exposing my networks on the Internet. I need to replace my current router and am committed to make this work. Can someone get me a couple quick pointers on the best way to achieve this? I need to keep the layer 3 switch in the mix.

      Thank you in advance

      1 Reply Last reply Reply Quote 0
      • Cry Havok
        Cry Havok last edited by

        Why do you need to keep the switch (which sounds more like a router) in the mix? It would be much simpler to have 2 LAN interfaces, one for each network.

        1 Reply Last reply Reply Quote 0
        • S
          Supermule Banned last edited by

          Or VLAN's….. :)

          1 Reply Last reply Reply Quote 0
          • C
            charlien last edited by

            @Cry:

            Why do you need to keep the switch (which sounds more like a router) in the mix? It would be much simpler to have 2 LAN interfaces, one for each network.

            I need the switch in the mix because of cabling issues. Yes it is acting as a router/ Ports 1-11 are on the 192.168.50.0 subnet and the 12th routes to the 172.16.0.0 subnet.

            I really don't care about blocking out bound traffic. Couldn't I just change the firewall ruling allowing the 192.168.50.0 subnet out to ...? I tried adding a rule by copying the rule added for the 192.168.50.0 subnet and changed it to 172.16.0.0 but that did not work. Yes, I did change it to advanced mode.

            1 Reply Last reply Reply Quote 0
            • C
              charlien last edited by

              I gave up and installed a third NIC. Everything is working.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post

              Products

              • Platform Overview
              • TNSR
              • pfSense Plus
              • Appliances

              Services

              • Training
              • Professional Services

              Support

              • Subscription Plans
              • Contact Support
              • Product Lifecycle
              • Documentation

              News

              • Media Coverage
              • Press
              • Events

              Resources

              • Blog
              • FAQ
              • Find a Partner
              • Resource Library
              • Security Information

              Company

              • About Us
              • Careers
              • Partners
              • Contact Us
              • Legal
              Our Mission

              We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

              Subscribe to our Newsletter

              Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

              © 2021 Rubicon Communications, LLC | Privacy Policy