Navigation

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

    Pfsense/ one Nic for munity VLAN

    L2/Switching/VLANs
    4
    6
    399
    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.
    • D
      Dafoxx last edited by Dafoxx

      Hey guys,
      I'm very new to Vlanning so help with this would be much appreciated, I have here a 6port Smoothwall, its not running anything so changes can be made.
      we are using NIC1/WAN, this needs te able to see for example vlan2 (and for other networks but not yet), vlan 3, vlan4)
      How would I set this up?

      My thought on this is that just adding the traffic tags say vLan4 for NIC3, same for the others E.g:
      Nic3 > vLan2 > switch port configured for vlan2
      Nic4 > vLan3 > switch port configured for vlan3
      Nic5 > vLan4 > switch port configured for vlan4
      Nic6 > vLan5 > switch port configured for vlan5
      WAN switch port set up to see all 4 vlans?

      1 Reply Last reply Reply Quote 0
      • B
        bhjitsense last edited by

        One physical interface (as long as it supports VLAN tagging) can be used for all your VLANs. You don't need one NIC for each VLAN. Each VLAN will then become a virtual interface on which you will place firewall rules. These rules can block/allow traffic to other interfaces/virtual interfaces. Your WAN interface will not need to know about the VLANs.

        P 1 Reply Last reply Reply Quote 0
        • D
          Dafoxx last edited by

          Thank you for putting your time into replying to me. now i understand.
          This is now working as expected from the customer's point of view.

          1 Reply Last reply Reply Quote 0
          • P
            penguin-nut @bhjitsense last edited by

            @bhjitsense I have the concept of 1 NIC and all VLANS assigned to that NIC pfsense. How do I add the default VLAN 1 that is untagged. My VLANS can talk to each other via pfsense but the untagged default, can't get to it.

            1 Reply Last reply Reply Quote 0
            • JKnott
              JKnott last edited by

              @penguin-nut said in Pfsense/ one Nic for munity VLAN:

              I have the concept of 1 NIC and all VLANS assigned to that NIC pfsense. How do I add the default VLAN 1 that is untagged. My VLANS can talk to each other via pfsense but the untagged default, can't get to it.

              The bare interface, without VLANs is untagged. It is also often called "VLAN1", even though it doesn't have a tag.

              P 1 Reply Last reply Reply Quote 0
              • P
                penguin-nut @JKnott last edited by

                @jknott Figured out the VLAN stuff, all set. Thanks for responding.

                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