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

    How can untagged traffic end up on a VLAN?

    General pfSense Questions
    6
    9
    983
    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.
    • A
      Atreides
      last edited by

      If what I understand about VLANs is correct, if described simply, there are just adding a tag to a packet. Why then, if I set a port to be untagged traffic on my switch, and send it to pfSense over a trunk, will it be accepted in the default VLAN from that switch? Why does pfSense know that untagged traffic will be on VLAN 1, or whatever VLAN is the default was on the switch? Shouldn't the traffic not be accepted on any VLAN because its untagged?

      For example, I have a tp-link switch which I have set two ports to be access ports (UNTAGGED) and on the default VLAN. When I set the interface they are being accepted on in pfSense to igb1, I won't get traffic from those two switch ports. If I set them to VLAN 1 on igb1, I will get traffic from those two ports. Shouldn't they be accepted on igb1?

      Maybe I am misunderstanding how a default VLAN works, is traffic on the default VLAN untagged? If so why does a VLAN accepted it at all on pfSense?

      1 Reply Last reply Reply Quote 0
      • GrimsonG
        Grimson Banned
        last edited by

        @Atreides:

        For example, I have a tp-link switch

        https://forum.pfsense.org/index.php?topic=123324.0

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

          I have a tp-link switch

          That's the problem right there.  TP-Link doesn't understand VLANs and, as a result, sells equipment that doesn't handle VLANs properly.  If you want to run VLANs, stay away from TP-Link.  I have a TP-Link access point and have a similar problem, where native LAN traffic is winding up on the VLAN.

          Once again, for VLANs, stay away from TP-Link.

          PfSense running on Qotom mini PC
          i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
          UniFi AC-Lite access point

          I haven't lost my mind. It's around here...somewhere...

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

            Which can be extrapolated to stay away from tp link as a brand entirely since pretty much all networking gear of any substance whatsoever must understand dot1q.

            Just get a d-link. Same price point and it generally works.

            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
            • A
              Atreides
              last edited by

              @JKnott:

              I have a tp-link switch

              That's the problem right there.  TP-Link doesn't understand VLANs and, as a result, sells equipment that doesn't handle VLANs properly.  If you want to run VLANs, stay away from TP-Link.  I have a TP-Link access point and have a similar problem, where native LAN traffic is winding up on the VLAN.

              Once again, for VLANs, stay away from TP-Link.

              That links to a smart switch, mine is a managed TL-SG3424, do you think the same stands for it?

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

                @Atreides:

                @JKnott:

                I have a tp-link switch

                That's the problem right there.  TP-Link doesn't understand VLANs and, as a result, sells equipment that doesn't handle VLANs properly.  If you want to run VLANs, stay away from TP-Link.  I have a TP-Link access point and have a similar problem, where native LAN traffic is winding up on the VLAN.

                Once again, for VLANs, stay away from TP-Link.

                That links to a smart switch, mine is a managed TL-SG3424, do you think the same stands for it?

                I don't know, but given TP-Link's track record, I wouldn't be surprised.

                PfSense running on Qotom mini PC
                i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                UniFi AC-Lite access point

                I haven't lost my mind. It's around here...somewhere...

                1 Reply Last reply Reply Quote 0
                • johnpozJ
                  johnpoz LAYER 8 Global Moderator
                  last edited by

                  Yeah for the longest time they were saying it was designed that way without the ability to remove vlan 1 on purpose and that there was nothing wrong with it.. They just recently posted that it would be corrected and that there should be a new beta software to fix the problem in next week or so.

                  Taking that they clearly do not seem to understand how vlans are suppose to function, until their recent post.  Which we still have not seen the fixed firmware.  I am with jknott here, I wouldn't assume any of their other switches got it right either ;)  All I can tell you is that the cheaper tp-link 105e and 108e switches do not correctly isolate vlans since every port has vlan 1 which can not be removed.

                  You would have to do some testing on their higher end models to validate that they do not bleed vlan traffic.  Or just get a switch you know gets it right, etc.

                  An intelligent man is sometimes forced to be drunk to spend time with his fools
                  If you get confused: Listen to the Music Play
                  Please don't Chat/PM me for help, unless mod related
                  SG-4860 24.11 | Lab VMs 2.7.2, 24.11

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

                    I wouldn't assume any of their other switches got it right either

                    Nor their access points.  As mentioned in other threads, I have a WA901N AP, which has the same problem.  Even though their 2nd level support recongnized the problem a few years ago, there has been no fix so far.  I may replace the software with DD-WRT.  I expect that will work better.

                    PfSense running on Qotom mini PC
                    i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                    UniFi AC-Lite access point

                    I haven't lost my mind. It's around here...somewhere...

                    1 Reply Last reply Reply Quote 0
                    • jahonixJ
                      jahonix
                      last edited by

                      I have several TL-SG3210 (trying to be a cheaper SG300-10 derivate) and 1x TL-SG5428 as well as 1x TL-SG5412F.
                      Those are fully managed L2 "JetStream" switches and do not exhibit the behaviour of the entry-level smart switches. This is at home only. Since we use Cisco in the office and at client's site's extensively I probably would buy those for my home now as well.

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