Business Community > Controllers > Why can't I select a VLAN as native and tagged at the same time?
< Controllers

Why can't I select a VLAN as native and tagged at the same time?

Why can't I select a VLAN as native and tagged at the same time?

Why can't I select a VLAN as native and tagged at the same time?
Why can't I select a VLAN as native and tagged at the same time?
2023-10-31 15:10:33 - last edited 2023-11-01 07:13:17
Model: OC200  
Hardware Version: V1
Firmware Version:

Hello,

I'm sadly facing more and more issues with the TP-Link Hardware. 

 

At the moment I'm trying to configure a port, but it seems not to be possible.
I would like to set a native network and also have the same as tagged VLAN on the port.

 

I's something I configure very often for port where a management PC is use:
- You can connect PC without special configuration and will be in the LAN network for example

- but you can also connect a PC with VLAN tagging and also use the LAN as tagged and in addition for example the management VLAN.

 

Also it's a security issue if I always have to choose a VLAN as native which is not beeing used in the tagged list. Even if I don't need it at this port.

 

 

But it seems that this is not possible.

 

Is this an error? Please correct or change here!

 

  0      
 
  0      
 
#1
Options
2 Accepted Solutions
Re:Why can't I select a VLAN as native and tagged at the same time?-Solution
2023-10-31 21:11:02 - last edited 2023-11-01 07:13:17

  @SebastianH 

 

 

For EAP ports for example:

 If I would like to have 3 SSIDs, I would put 3 VLANs on this port. Should be enough. Why do I need to configure a 4th one as native?

 

Native is simply the trunking vlan.. in your case vlan 10 (Heimnetz), the traffic needs to be on this vlan to allow the trunking of the packets from AP to Switch to Router etc.  You have to have a trunking vlan, and since its a trunk its untagged, therefore you cant set a tag on it.  

So when you plug in your AP and configure the SSIDs Kinder, IoT and Gastnetz set their vlan tags accordingly..  These tags will be ignored when the packet hits the switchport (trunk).   Basically what you are saying is on the Heimnetz 10 trunking vlan, accept traffic from 20, 30 and 50.  it will obviously already accept its own vlan 10 traffic so you dont need to "tag it"

 

 

Or for a management PC:

3 VLAN on the port (e.g. management, LAN, Camera) and LAN as native. 

I can configure my PC to use TAGs and enter all VLANs, or I connect without tagging and I'm ending up in the default LAN.

 

Yeah totally.. as its native its trunk, therefore if you dont tag it will be Heimnetz, otherwise its what you tag it as (provided you have permitted it).

 

 

 

What will happen if I configure a native VLAN (e.g. 10) and then sending a tagged (10) frame to this port? 

 

Never tried it to be honest and why would you?  Adding tags adds overhead, why would you want to tag traffic for a network its already on?  It seems pointless and just adds latency. 

Hypothetically, if a packet arrived at the port tagged for 10, i cant see why it wouldnt work however as its on the allowed list.   

 

 

Its just occurred to me that you may be wanting to use Heimnetz as a client VLAN to handle clients?  Am i correct?    If so rename Heimnetz to Trunking or LAN and create a new vlan for Heimnetz say id 60..

The only thing on your "trunking vlan" should be your network hardware, not clients.  

 

 

Recommended Solution
  0  
  0  
#4
Options
Re:Why can't I select a VLAN as native and tagged at the same time?-Solution
2023-11-01 00:05:09 - last edited 2023-11-05 19:01:06

  @SebastianH 

 

What I don't really get is the trunking thing you are mentioning. Is it needed because of the SDN service? A separate non tagged VLAN over all ports?

 

A trunk for me is a link between two network devices with multiple VLANs on it. 

 

 

All switches have a trunk by default and its usually VLAN1 and yes its used to link different network devices together as you say.   In TP Link world this is called LAN and its also vlan1 if i remember right, but you have remove or renamed that to Heimnetz and basically made that your trunk on VLAN10.   The id is irrelevent really, native is just the term for trunking. 

 

When you apply a VLAN to a port the ONLY traffic that can go down that port is that specific VLAN, unless its a trunk port.   As mentioned by default this is called LAN

If you look at the screenie below this is my port profile for the switchports connected to my APs.  I have 3x vlans (iot guest and home) trunked over that port on the native LAN

 

This is basically what you need to setup.      If i changed that native to say IOT vlan, then the AP itself couldnt talk to the switch as they are both on the LAN, it would lock out the port.

 

 

Yes SDN based networks are different from traditional vlans and switching,

Recommended Solution
  0  
  0  
#6
Options
6 Reply
Re:Why can't I select a VLAN as native and tagged at the same time?
2023-10-31 20:22:03

  @SebastianH 

 

Why would you want to set the same tag as native?  

 

Native is just the network that it trunks over, therefore you dont need to tag it as its already on that network.  You would literally be tagging traffic with the network tag for the network it is already on, it would accomplish nothing. 

 

Other vendors do this also, its not specifically a TP Link thing..

 

 

  0  
  0  
#2
Options
Re:Why can't I select a VLAN as native and tagged at the same time?
2023-10-31 20:44:35

  @Philbert 

For EAP ports for example:

 If I would like to have 3 SSIDs, I would put 3 VLANs on this port. Should be enough. Why do I need to configure a 4th one as native?

 

Or for a management PC:

3 VLAN on the port (e.g. management, LAN, Camera) and LAN as native. 

I can configure my PC to use TAGs and enter all VLANs, or I connect without tagging and I'm ending up in the default LAN.

 

 

What will happen if I configure a native VLAN (e.g. 10) and then sending a tagged (10) frame to this port? 

  0  
  0  
#3
Options
Re:Why can't I select a VLAN as native and tagged at the same time?-Solution
2023-10-31 21:11:02 - last edited 2023-11-01 07:13:17

  @SebastianH 

 

 

For EAP ports for example:

 If I would like to have 3 SSIDs, I would put 3 VLANs on this port. Should be enough. Why do I need to configure a 4th one as native?

 

Native is simply the trunking vlan.. in your case vlan 10 (Heimnetz), the traffic needs to be on this vlan to allow the trunking of the packets from AP to Switch to Router etc.  You have to have a trunking vlan, and since its a trunk its untagged, therefore you cant set a tag on it.  

So when you plug in your AP and configure the SSIDs Kinder, IoT and Gastnetz set their vlan tags accordingly..  These tags will be ignored when the packet hits the switchport (trunk).   Basically what you are saying is on the Heimnetz 10 trunking vlan, accept traffic from 20, 30 and 50.  it will obviously already accept its own vlan 10 traffic so you dont need to "tag it"

 

 

Or for a management PC:

3 VLAN on the port (e.g. management, LAN, Camera) and LAN as native. 

I can configure my PC to use TAGs and enter all VLANs, or I connect without tagging and I'm ending up in the default LAN.

 

Yeah totally.. as its native its trunk, therefore if you dont tag it will be Heimnetz, otherwise its what you tag it as (provided you have permitted it).

 

 

 

What will happen if I configure a native VLAN (e.g. 10) and then sending a tagged (10) frame to this port? 

 

Never tried it to be honest and why would you?  Adding tags adds overhead, why would you want to tag traffic for a network its already on?  It seems pointless and just adds latency. 

Hypothetically, if a packet arrived at the port tagged for 10, i cant see why it wouldnt work however as its on the allowed list.   

 

 

Its just occurred to me that you may be wanting to use Heimnetz as a client VLAN to handle clients?  Am i correct?    If so rename Heimnetz to Trunking or LAN and create a new vlan for Heimnetz say id 60..

The only thing on your "trunking vlan" should be your network hardware, not clients.  

 

 

Recommended Solution
  0  
  0  
#4
Options
Re:Why can't I select a VLAN as native and tagged at the same time?
2023-10-31 21:25:53

  @Philbert 

Philbert wrote 

Its just occurred to me that you may be wanting to use Heimnetz as a client VLAN to handle clients?  Am i correct?    If so rename Heimnetz to Trunking or LAN and create a new vlan for Heimnetz say id 60..

The only thing on your "trunking vlan" should be your network hardware, not clients.  

 

 

Yes, that's what it is.

And slowly I begin to understand the logic here. The naming seems to be different between suppliers, which doesn't makes it easier.

 

What I don't really get is the trunking thing you are mentioning. Is it needed because of the SDN service? A separate non tagged VLAN over all ports?

 

A trunk for me is a link between two network devices with multiple VLANs on it. 

  0  
  0  
#5
Options
Re:Why can't I select a VLAN as native and tagged at the same time?-Solution
2023-11-01 00:05:09 - last edited 2023-11-05 19:01:06

  @SebastianH 

 

What I don't really get is the trunking thing you are mentioning. Is it needed because of the SDN service? A separate non tagged VLAN over all ports?

 

A trunk for me is a link between two network devices with multiple VLANs on it. 

 

 

All switches have a trunk by default and its usually VLAN1 and yes its used to link different network devices together as you say.   In TP Link world this is called LAN and its also vlan1 if i remember right, but you have remove or renamed that to Heimnetz and basically made that your trunk on VLAN10.   The id is irrelevent really, native is just the term for trunking. 

 

When you apply a VLAN to a port the ONLY traffic that can go down that port is that specific VLAN, unless its a trunk port.   As mentioned by default this is called LAN

If you look at the screenie below this is my port profile for the switchports connected to my APs.  I have 3x vlans (iot guest and home) trunked over that port on the native LAN

 

This is basically what you need to setup.      If i changed that native to say IOT vlan, then the AP itself couldnt talk to the switch as they are both on the LAN, it would lock out the port.

 

 

Yes SDN based networks are different from traditional vlans and switching,

Recommended Solution
  0  
  0  
#6
Options
Re:Why can't I select a VLAN as native and tagged at the same time?
2023-11-05 19:03:35

  @Philbert 

Thank you for your help.

I made it running successfully and also changed the management VLAN to a separate VLAN like in the description. 

 

One additional question:

Do I still need VLAN 1 for the devices, even if I changed everything to a separate management VLAN?

 

Thank you.

 

BW

Sebastian 

  0  
  0  
#7
Options

Information

Helpful: 0

Views: 457

Replies: 6

Related Articles
tagged vlan not working if same as native
522 0
Why can't i change the channel?
512 0
Why can't I buy a single powerline adapter (AV1000 or equivalent)?
956 0
VLAN with only tagged network
767 0
Tagged VLAN for Guest WiFi
616 0
Manage switch over tagged vlan
326 0
About Us
Press
Copyright © TP-LINK CORPORATION PTE. LTD. All rights reserved.