Comment 6 for bug 1932292

Thanks. This shows that you're using LXD with an externally defined bridge, so aren't using any of LXD's own integration with nft or xtables for firewalling.

So this isn't something that LXD would really be able to help with. When LXD itself creates a bridge, it tries to prepend some allow rules to mitigate such issues, though not always very successfully.

In general, we've been trying to push conflicting projects (k8s, docker, ...) to work on their firewalling rules so that they only apply to their own interfaces and don't go messing with other bridges or interfaces on the system.