ER605 V1 - Can't delete a vlan that used to belong to a second wan

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

ER605 V1 - Can't delete a vlan that used to belong to a second wan

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
ER605 V1 - Can't delete a vlan that used to belong to a second wan
ER605 V1 - Can't delete a vlan that used to belong to a second wan
2023-04-01 16:47:15 - last edited 2023-04-01 16:48:54
Model: ER605 (TL-R605)  
Hardware Version: V1
Firmware Version: 1.2.2

Hi,

ER605 V1. firmware 1.2.1, 1.2.3 beta and now 1.2.2 beta.

I set a second wan a while ago when I switched internet provider. I was using firmware 1.2.1. The device created vlan 4093 and associated it to the second wan. Now I'm using only one wan and the vlan 4093 is still configured and tied to port 2. I tried to delete it but I can't. When I try, the device respond : "The current VLAN has been referenced. It cannot be deleted." The same is happening with firmwares beta 1.2.3 and 1.2.2.

I also reconfigure the device to dual wan and then tried to delete vlan 4093 but no luck. Maybe someone has an idea or a workaround.

Thanks

  0      
  0      
#1
Options
1 Reply
Re:ER605 V1 - Can't delete a vlan that used to belong to a second wan
2023-04-02 16:30:08

  @PlasticWood 

 

TPlink routers will auto-create VLANs for each WAN interface it seems.  By default I configure my ER605's with two WAN's just in case I ever have to swap in a temp uplink then I won't trash the existing connection and I don't have to rebuild the router either to switch back and forth.  However, this auto creates:

 

WAN1 - VLAN4094

WAN2 - VLAN4093

 

Now if you're saying you cannot delete 4093 after reconfiguring your router back to a single WAN port, then two things come to mind.  1. you may need to power cycle your router to 'clear' the previously existing, system created VLAN.  2. It may always be defined and reserved so that all the loadbalancing magic can work.

 

Either way I wouldn't be concerned....you have 4,000 other options.

<< Paying it forward, one juicy problem at a time... >>
  0  
  0  
#2
Options