Business Community > Gateways > VLAN 802.1Q Not working as expected.
< Gateways

VLAN 802.1Q Not working as expected.

VLAN 802.1Q Not working as expected.

VLAN 802.1Q Not working as expected.
VLAN 802.1Q Not working as expected.
2025-11-18 16:59:11
Model: ER7212PC  
Hardware Version: V2
Firmware Version: Latest

Hello, I am struggling with VLAN setup on this tplink device. 

I am with experience in Corporate LAN networks so 802.1Q VLAN is well known at my end.

 

Expected results:

VLAN 2 Office

- Interface

-Default VLAN

-VLAN number 2(changed to 2) 

Unagged ports 5-10(PVID) 

Tagged ports 11-12

Selected ininterface options ports 5-12, confugired on device as PVID for ports 5-10

 

 

- VLAN  VMware Vmotion

- configured as VLAN so tagged on all pprts

- VLAN Number 5

 

- VLAN Management

- Interface

- VLAN number 4

Untagged ports 11-12

Selected Interface options porrs 11-12, configured on device PVID on ports 11-12

 

 

The issue is that VLAN 2 is not tagged on ports 11-12. ( at least not communicatng as there is no way of checking what is actually tagged) I Have connected Hypervisor for Office VM's on ports 11-12 and tp-link does not provide connectivity. This is observed as bug in device operations. Vlan 5 works fine on Hypervisor devices as tagged VLAN. 

Hours wasted troubleshooting waiting for support telephone pickup so basically no telephone support available. 

Kindly provide solution how to make default vlan untagged for PVID and tagged on specified ports. 

Any support how to see cli config to see if this is actually seen as tagged also welcome. 

 

 

Of course verified docs and this VLAN config seems to be supported.  But not working as advertised. 

 

 

 

 

 

 

 

 

  1      
 
  1      
 
#1
Options
10 Reply
Re:VLAN 802.1Q Not working as expected.
2025-11-18 18:52:24

Hi @Lucek,

 

Not sure you should trunk the default VLAN.  If you need to trunk VLAN 2, just don't make it the default VLAN.

  0  
  0  
#2
Options
Re:VLAN 802.1Q Not working as expected.
2025-11-18 19:29:36

  @Lucek 

 

Have you actually assigned all the vlans to all the ports in the lan settings ?

 

If you adjust the port to a native PVID, it will be untagged port on that PVID, all others will be tagged.  If a vlan isnt assigned to a port, it wont be there in any form.

 

If you go to each port on the unit and look in the PVID list, you should see them all - that is how you can double check a vlan is assigned to that port or not

  0  
  0  
#3
Options
Re:VLAN 802.1Q Not working as expected.
2025-11-19 01:50:34

Why i cannot use default vlan as trunk? 

Documentation linked on vendor page clearly says that VLAN(and Interface) that is not set as PVID will be tagged. 

 

Yes I have double and triple checked that Interface config  have correct port selected. 

In GUI config looks fine. This looks like a Bug in software.

 

I cannot make successful ping communication to gateway while my VM is assigned to VLAN 2, 

How to deal with support and get this bug resolved since no phone is picked and no emails are replied placed in web support form? 

Is there any way to place official TAC ticket other than this forum? 

I am happy to provide any technical details that will help vendor to resolve this bug. 

  0  
  0  
#4
Options
Re:VLAN 802.1Q Not working as expected.
2025-11-20 05:59:52

  @Lucek 

Perhaps you could provide a screenshot of the current configuration to better understand the issue? How is your current VLAN 2 configured? Also, what does your Hypervisor for Office VMs need in order to function properly? Does it require receiving VLAN 2 tagged traffic to work correctly? In addition, what is the current firmware version you are running? Please confirm whether you have contacted the support team for your region—under normal circumstances, someone should be providing assistance.Technical Support

Wishing you a joyful life and smooth internet! Get the Latest Firmware Releases for Omada Routers Here - Subscribe for Updates Omada US Enterprise Beta Program Launch
  0  
  0  
#5
Options
Re:VLAN 802.1Q Not working as expected.
2025-11-20 14:56:46

I have called to phone provided on TPlink website, waited several times for summarised time for about 3 hours, had no luck for someone to pickup phone. 

Also placed two requests using webform but no response from tplink since about two weeks now unfortunately

 

Thank you for your messages:) 

 

So Basically providing SS to help understand

Hypervisor have it's own builtin magnaged switch so needs to have tagged VLAN 2 to allow communication, you can understand this as a trunk port like any other managed switch. 

 

 

 

 

File:
Zrzut ekranu 2025-11-20 155146.pngDownload
  0  
  0  
#6
Options
Re:VLAN 802.1Q Not working as expected.
2025-11-20 14:57:09

Next SS - only one allowed in one reply

File:
Zrzut ekranu 2025-11-20 155220.pngDownload
  0  
  0  
#7
Options
Re:VLAN 802.1Q Not working as expected.
2025-11-20 14:57:20

Next SS - only one allowed in one reply

File:
Zrzut ekranu 2025-11-20 155338.pngDownload
  0  
  0  
#8
Options
Re:VLAN 802.1Q Not working as expected.
2025-11-20 14:58:56

Next SS - only one allowed in one reply 

 

Firmware: 
2.1.2 Build 20250705 Rel.59147

 

I can see today that there is new version available to install. so will try to do this soon and recheck. Need to plan Maintenance break with Business as device is in Prod now.

File:
Zrzut ekranu 2025-11-20 155406.pngDownload
  0  
  0  
#9
Options
Re:VLAN 802.1Q Not working as expected.
2025-11-21 21:19:36

  @Lucek 

 

Are you sure your VMs themselves are correctly setting 802.1Q taggng ?

  0  
  0  
#10
Options
Re:VLAN 802.1Q Not working as expected.
2025-11-26 07:48:35 - last edited 2025-11-26 07:53:17

Yes. I am sure. I have spend my time with due digilience. I have two other VM's in VLAN 5( configured as VLAN on TPlink device on two hosts connected to ports 11 and 12, and those VM's are able to communicate with each other using tagged VLAN. I have also similar configuration using other switches on many sites so I am sure that issue is caused by 7212ER device. I have been able to isolate the problem with confidence before raising this problem on the forum.. I have been able to find maintenance break yesterday and upgrade to latest firmware, but the VLAN issue is still present. I am dissapointed by tplink at the moment. It was mistake to buy this device.

 

 

Model
ER7212PC 2.0
Firmware Version
2.2.2 Build 20251118 Rel.39539

  0  
  0  
#11
Options

Information

Helpful: 1

Views: 400

Replies: 10

About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.