Thanks, that's a great write up. One thing I didn't ubderstand however is in your Docker macvlan, you set the parent to br0.10 and br0.20, where are those parents defined?
Maybe I misunderstood the macvlan documents but what I did was defining a vlan in server netplan vlan0.100 and set the macvlan parent to that vlan0.100. Is that not how it's supposed to be?
I will post it when I get my hands on it, but basically I made a macvlan which is using the server vlan, and then in the compose I set the network to that macvlan, which seems to be functional at least
That is my gut feeling too, but as I mentioned in another comment all physical devices work fine in their respective subnet. This is happening before I move the containers to a new subnet, and before these changes everything was working fine.
For large networks with over 20 devices, I find them acceptable not because they are good but because other options are more expensive.
For small networks? I despise them
The UI keeps changing and moving around settings for no good reason after each update
You can't setup devices directly if you have a device or two, you are required to setup a control center
The control center is already slow and sluggish, but the real nightmare starts when you start having 100 or more devices
Last couple of years they have been releasing batches with serious issues, software and hardware. The way they accepted recall for unfixable devices was so limited that many people are left with broken APs that will kill their network occasionally and the poor consumer has no idea why.
Honestly fuck 'em. there's more but I don't wanna give them any more rent space in my head on a Sunday lol
And it only took 728472994881 bullets!