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

    VLAN Tag not being passed

    Scheduled Pinned Locked Moved L2/Switching/VLANs
    32 Posts 6 Posters 4.5k 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.
    • DerelictD
      Derelict LAYER 8 Netgate @randy9000
      last edited by

      @randy9000 Again, the switch port has to be expecting tagged traffic on that port.

      This stuff works 100%.

      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)

      R 1 Reply Last reply Reply Quote 0
      • R
        randy9000 @Derelict
        last edited by

        @derelict

        Okay. Retrying again.

        1 Reply Last reply Reply Quote 0
        • R
          randy9000 @NOCling
          last edited by

          @nocling & @Derelict

          On the Netgear switch, am I to only tag "T" the port that the cable is in and untag "U" the others with on the VLAN? Or, Tag "T" all of the ports that will be used on the VLAN?

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

            @randy9000 Everything tagged on the pfsense switch side needs to be tagged on the switch port you are connecting to it.

            VLAN-pfSense copy.png

            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)

            R 1 Reply Last reply Reply Quote 0
            • R
              randy9000 @Derelict
              last edited by

              @derelict

              It seems as though the issue is with me netgear smart switch. If I plug a pc directly into port 2 of the Netgate 3100 I can get and ip address and internet. However, when I connect it to the netgear switch I get nothing.

              I also noticed that in order for my laptop to get and ip address the port 2 tagged check box but be unchecked and the port 5 box must be checked.

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

                @randy9000 That is how it works. Client devices like laptops almost exclusively get connected to single-VLAN, untagged ports.

                Tagged ports are for connections to other VLAN-aware devices like switches and access points and router ports with VLAN tags configured.

                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)

                R 1 Reply Last reply Reply Quote 0
                • R
                  randy9000 @Derelict
                  last edited by

                  @derelict

                  I think I may have confused you.

                  It works when I connect the laptop to the router on port 2. However, when I connect the router port 2 to the Netgear switch port 24 (Vlan tagged ) and the laptop to the netgear port 23 (untagged) The laptop cannot communicate with the router for an ip address etc.

                  DerelictD 1 Reply Last reply Reply Quote 0
                  • N
                    NOCling
                    last edited by

                    Your Port 2 is not tagged corectly.

                    Do this and it will work.
                    I use 10 VLANs over LAN 1 and here all works fine.

                    Netgate 6100 & Netgate 2100

                    R 1 Reply Last reply Reply Quote 0
                    • R
                      randy9000 @NOCling
                      last edited by

                      @nocling

                      What action are your referring to for me to do?

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

                        If connecting a laptop to a switch port with a tagged VLAN on it gets access for the laptop on that VLAN without taking special measures on the laptop to tag the VLAN on the port then the switch isn't configured like you think it is.

                        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)

                        R 1 Reply Last reply Reply Quote 0
                        • R
                          randy9000 @Derelict
                          last edited by

                          @derelict & All

                          Thanks for your help. The issue is resolved.

                          The problem was the Netgear switch port was being blocked because of STP rules.

                          Issue Resolved!

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