When Docker is enabled, my custom networks switch around the gateways in a way that the parent interface (or native VLAN) becomes the default gateway which is undesired. The default gateway should be on VLAN 11 of the bridge, i.e; br0.11.

 

Docker disabled (✓):

 

Docker enabled (✕):

 

As seen above, routes have high metrics (unimaginatively 200 + the VLAN's ID number) to avoid overriding VLAN 11's gateway as the default. When Docker is down, this is obeyed; when Docker is up this is partly obeyed but there's what it seems like a shortcut of sorts related to DockerDHCP/IPAM that overrides the default gateway even if the checkboxes for that functionality are unmarked (and thus I assumed it meant for it to be off).

 

On the Docker settings regardless if it's on macvlan vs ipvlan there aren't settings that could potentially be used to fix it:

 

I have not tried it yet — partly because all input in Docker's network definitions except for the last in line have been grayed out — removing the network definition entry causing the problem but I have a feeling it'll just move (the default route) down to the next in line listed if I do anyway (i.e. from br0 to br0.10).

 

I hope I'm wrong but just in case I'll wait for advice before I start wrecking things.

 

Could you guys help me a little? You can just put a hint if you don't feel like typing and I'll do my homework from there.

I fixed it!

 

(I'm sorry, I couldn't wait.)

 

I created an interface for management:

 

…and another to serve solely as a bridge without any addressing whatsoever:

( … )

 

I just realized I need another for (heavy) data transfer, but that should do it.

 

Now fingers crossed it doesn't kpanic after a few hours like it's been doing for a while now.