@Fae This guide assumes you already have a network with an adopted Omada router, so the process fails at the first step, because I'm trying to adopt a new router that does not have a management VLAN...

@G.V.S Yes, this makes perfect sense.., separate by default, allow by exception... This also leads me to conclude I'm going to have to completely restructure my network and get rid of my Management...

@G.V.S I'm just about to get an ER605, and reading up on this I thought the exact opposite was true i.e. traffic is routed between VLANS by default, and you have to setup ACL's to stop it doing...

@Fae So, how do you do this when the OC200 controller, switches and AP's are running on a Management VLAN ? eg. LAN network ( i.e. untagged VLAN 1) is 192.168.1/24 Management VLAN (tagged VLAN 200)...

@Philbert Thanks for the link..., the manual looks out of date with the guides on how to setup VLANS's etc. I'm trying to get info on how to adopt a router to an existing Omada network, but it looks...

Can anyone confirm/deny if the ER605v2 can: 1) Setup a DHCP server for each defined VLAN ? 2) Set DHCP address reservations (via MAC address) within each VLAN ? There is nothing in the manual to say...