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

    New VLAN setup

    Scheduled Pinned Locked Moved General pfSense Questions
    50 Posts 5 Posters 17.1k 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.
    • marcellocM
      marcelloc
      last edited by

      Lan will be vlan1 on re1 and opt1 will be vlan100 on re1.

      Disconnect re2

      Treinamentos de Elite: http://sys-squad.com

      Help a community developer! ;D

      1 Reply Last reply Reply Quote 0
      • ?
        A Former User
        last edited by

        and then i can plug in my 16 port netgear into a port on the HP that i didnt configure yet…we forgot to calculate that.  everything on that 16 port netgear is on 192.168.1.0 /24 network...do i need to tag another port on the hp vlan switch?

        so it will look like this

        isp-----cable modem-------pfsense-------hp vlan switch--------16 port netgear

        1 Reply Last reply Reply Quote 0
        • marcellocM
          marcelloc
          last edited by

          Or use re2 as opt2 to connect netgear.

          Treinamentos de Elite: http://sys-squad.com

          Help a community developer! ;D

          1 Reply Last reply Reply Quote 0
          • ?
            A Former User
            last edited by

            @marcelloc:

            Or use re2 as opt2 to connect netgear.

            but isnt network 192.168.1.1 already existing on re1?

            1 Reply Last reply Reply Quote 0
            • marcellocM
              marcelloc
              last edited by

              If both switches are on same network, just plug netgear on port 3

              Treinamentos de Elite: http://sys-squad.com

              Help a community developer! ;D

              1 Reply Last reply Reply Quote 0
              • P
                podilarius
                last edited by

                Tagging a port means it can be in multiple VLANS. Using a port untagged means that anything on the port is in the VLAN that you assigned. Excluded means that port is not participating in that vlans. If you assign untagged in 2 different vlans on the same port, then the second ignored.

                So re2 (vlan1) goes into port 8 and services the main LAN.
                Then re1 goes into port 1 (vlan100).
                Your wifi goes into port 2
                your other switch you want in with vlan100 goes into port 3.

                Then setup vlan like so.

                VLAN1
                e,e,e,u,u,u,u,u

                VLAN100
                u,u,u,e,e,e,e,e

                Do not setup re1 for a vlan since you are port grouping on the switch. You will setup re1 as if you are just using a different switch.

                You would only tag port 8 if you wanted only 1 physical port on the pfsense firewall to access both vlans. Since you are using physically seperated nics and you only want to setup 2 different LANs, this would be ideal.

                good luck.

                1 Reply Last reply Reply Quote 0
                • ?
                  A Former User
                  last edited by

                  @podilarius:

                  Tagging a port means it can be in multiple VLANS. Using a port untagged means that anything on the port is in the VLAN that you assigned. Excluded means that port is not participating in that vlans. If you assign untagged in 2 different vlans on the same port, then the second ignored.

                  So re2 (vlan1) goes into port 8 and services the main LAN.
                  Then re1 goes into port 1 (vlan100).
                  Your wifi goes into port 2
                  your other switch you want in with vlan100 goes into port 3.

                  Then setup vlan like so.

                  VLAN1
                  e,e,e,u,u,u,u,u

                  VLAN100
                  u,u,u,e,e,e,e,e

                  Do not setup re1 for a vlan since you are port grouping on the switch. You will setup re1 as if you are just using a different switch.

                  You would only tag port 8 if you wanted only 1 physical port on the pfsense firewall to access both vlans. Since you are using physically seperated nics and you only want to setup 2 different LANs, this would be ideal.

                  good luck.

                  i am going to try to decipher all of this tomorrow.  too much happening right now.

                  i appreciate all the help.  you are telling me to set it up slighty different than what marcelloc said.  if not, then i mis understood him.

                  one thing we didnt bring up yet was port priority.  i saw that under the vlan section of the HP switch and decided i had enough for tonight.

                  thanks again guys.

                  1 Reply Last reply Reply Quote 0
                  • marcellocM
                    marcelloc
                    last edited by

                    Podilarius, you missed some posts, the setup is done.

                    Re2 is not needed as both networks 192 and 10 are tagged on port 1 and assigned on pfsense.

                    The second switch is on same 192 network, so no need to tag, just uplink.

                    Treinamentos de Elite: http://sys-squad.com

                    Help a community developer! ;D

                    1 Reply Last reply Reply Quote 0
                    • P
                      podilarius
                      last edited by

                      Sorry about that then. I did miss them. Dang, I missed a whole page of posts. marcelloc, your setup is the whole basis on why vlans are even used. It does just depend on what you want to do though. Didn't mean to confuse things.

                      1 Reply Last reply Reply Quote 0
                      • marcellocM
                        marcelloc
                        last edited by

                        never mind, there were many posts since your last visit  ;)

                        Treinamentos de Elite: http://sys-squad.com

                        Help a community developer! ;D

                        1 Reply Last reply Reply Quote 0
                        • stephenw10S
                          stephenw10 Netgate Administrator
                          last edited by

                          Turn your back for a second and BAM the thread goes up to 4 pages!

                          Why all manufacturers can't agree on a standard naming scheme for VLANs is beyond me. Cisco in particular seem to have their own names for everything.

                          The labeling of ports as Tagged, Untagged or Excluded is confusing. It is basically describing what action the switch will take to traffic leaving that port.

                          The section of network between the firewall and the switch that carries all the vlan tagged traffic from several vlans is known as a vlan trunk. Though I think that could be Cisco's naming it's pretty much universal!

                          Traffic within the switch, on a particular VLAN, destined for the firewall must exit onto the trunk connection and remain tagged. Hence that port is labeled Tagged.

                          Traffic within the switch, on a particular VLAN, destined for a client computer must exit from one of the ports with clients connected and have vlan tagging removed. Hence those ports are labeled Untagged.

                          All the ports which are neither a trunk connection nor an exit port for that particular vlan are labeled Excluded.

                          I hope that makes some sort of sense to you.

                          If your goal here was to get some VLAN experience then I think you're right on target!  ;)

                          Steve

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