This is still a problem. I updated firmware on 1 of my switches and now it is constantly spamming DNS queries for the domain `omada`. The no controller discover command did not work for me and I do...

Hey, I have configured the switchport that connects to router with a profile that looks like, native vlan => 1 tagged vlans => 10,20,30,40,50,60,70,99,140,150,160 Management vlan is 99 It sends a...

Hi, For interfaces 1 through 5, I have configured the profile as, "System". This custom profile has vlan 1 as the native vlan and vlans 10,20,30,40,50,60,70,99,140,150,160 as the tagged vlans. This...

Bumping this up again. This just keeps coming up. What is the problem with support a feature that is already supported in standalone mode ? I do not want silly vlan 1/untagged traffic. I have a...

There is no solution to this bug. It only announces it's presence in vlan1 instead using the configured vlan interface and it continues to be a problem.

@Clive_A > First, at the very beginning of this long back-and-forth conversation, I have said and pointed out how the broadcast works and if you use a different VLAN, you should try the discovery...