SDN - br ID vs vlan ID?

[maxbraketorque]

I'm messing around with VLAN options on my GT-AX6000 main/AP combo (not mesh) for an IOT network for 3006.102.

When I setup a custom network on the main router or AP router, and then choose the option that creates a unique subnet, the SDN system defaults to VLAN ID 52 and uses the .52 subnet. And if I run brctl show, the new SDN is associated with br52.

Now, if I decide to change the VLAN ID to something else, say 209 and change the subnet to .209, different things happen on the main and AP router.

• For the main router interface, the VLAN ID changes to 209, and the subnet changes to .209 as expected. However, if I run brctl show, the br ID remains 52.
• For the AP router, the VLAN ID changes to 209, and the subnet changes to .209 just as with the main router, and the br ID changes to 209 as well. This is the behavior that makes sense to me.

This difference in br ID assignment behavior between the main and AP routers makes it kinda hard to have a functioning IOT (or guest) network propagate to the AP router for anything but VLAN 52. Does anyone know why the main router stays at br52 instead of changing to br209 (for this example)? Is there a way to make the main router use br209 without causing any issues?

 

[CaptnDanLKW]

I'm in the middle of a major upgrade of hardware; New BE86U and redoing everything from scratch. Also noticed something similar.
Using YazDHCP
No Mesh nodes or APs, and my 1st creation of a new 'custom' SDN set up the 192.168.52.x address but the br device created was br54.

I know with my previous setup of my AX86U Pro, my br device was br52 but in that scenario I started with GNP and the built in DHCP reservation method before switching to YazDHCP.... probably not related but some data to think about, don't think it really matters as long as the code and configs know whats what.