Unable to Adopt ER-605V2 with VLAN standalone configs

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

Unable to Adopt ER-605V2 with VLAN standalone configs

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Unable to Adopt ER-605V2 with VLAN standalone configs
Unable to Adopt ER-605V2 with VLAN standalone configs
2023-02-18 03:13:42
Model: ER605 (TL-R605)  
Hardware Version: V2
Firmware Version: 2.1.1 Build 20230115 Rel.77774

I recently configured my ER605 in a standalone mode with 4 VLAN's with management VLAN being on 50.

 

192.168.20.1/24 - VLAN 50 - IOT - PORT 2

192.168.30.1/24 - VLAN 50 - HOME - PORT 3

192.168.40.1/24 - VLAN 50 - OFFICE - PORT 4

192.168.50.1/24 - VLAN 50 - MGMT - PORT 5

 

I installed Omada controller as a VM under proxmox - Connected to PORT 5

 

When adopting the router, everything related to my configurations are wiped clean and there by making my network unusable. ie. I cannot access my proxmox servers because its connected directly to the router. Any thoughts on how to configure this?

 

Is this is not supported?, any suggestions?

  0      
  0      
#1
Options
1 Reply
Re:Unable to Adopt ER-605V2 with VLAN standalone configs
2023-02-18 09:40:42

  @TOmega 

 

I my personal experience I have found this to be a major problem with Omada, particularlly when adopting/changing the router.

 

If you create a management VLAN and place all Omada devices and the controller on this network, then you will have problems. In the router configuration you can set DHCP option 138 to tell devices where the Omada Controller is, but this (obviously) will not work if you are attempting to adopt/replace the router itself.

 

eg. When you replace/reset your router it will have a default IP of 192.168.0.1. If you have a management VLAN on 192.168.50.x then nothing is going to work.

 

I messed around with various configurations over the last couple of years and came to the conclusion that the _only_ way to configure the network that is consistently reliable is to make the factory default LAN (192.168.0.1/24) the "management" LAN. I have several VLANS for client devices and keep all the Omada devices on this default LAN.

 

Make sense ?

  1  
  1  
#2
Options