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

    Single WAN, Multi LAN, Lab Setup

    Scheduled Pinned Locked Moved General pfSense Questions
    3 Posts 3 Posters 934 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.
    • B
      blasterboy16
      last edited by

      I am working on some changes to my home lab. My goal is to use multiple NICs in my pfSense box to connect to two Cisco routers.

      The idea would be to then connect each router with T1 links and start messing around with routes and other stuff… blah blah blah Cisco side training/learning stuff...

      Back to the point. My pfSense setup.

      My pfSense server has three NICs. One for WAN and two for LAN.
      Can I setup each LAN NIC with its own /16 subnet? I.E. LAN1(17.20.0.0/16) and LAN2(17.21.0.0/16)? Would this allow all pfSense services to function for both LAN connections? Including any downloaded addons (IPS/IDS, webfilter, etc)?

      I would then use my Cisco routers to further break down those /16s into /24s or smaller.

      Am I on the right track? Or is there a better way to achieve my goal?

      Have I left out any information that would be helpful?

      -JF

      1 Reply Last reply Reply Quote 0
      • KOMK
        KOM
        last edited by

        No problem.  My current pfSense LAN is 10.10.0.0/16 and my DMZ is a 172.16.1.0/24.

        1 Reply Last reply Reply Quote 0
        • DerelictD
          Derelict LAYER 8 Netgate
          last edited by

          No problem with that but I don't think I would do it that way.

          I might assign a /24 to one of your pfSense interfaces and put the cisco WAN ports on that, then in pfSense route, say, 10.1.0.0/16 to one and 10.2.0.0/16 to the other.  Then the first could do whatever it wanted with 10.1.0-254.X and the second whatever it wanted with 10.2.0-254.X.

          Chattanooga, Tennessee, USA
          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
          Do Not Chat For Help! NO_WAN_EGRESS(TM)

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