dohqu8Zi

Thanks for the correction.

BTW: Depending on the configuration you can create a new namespace within Docker to gain CAP_NET_RAW since namespaces can nest.

No, Docker usually drops CAP_NET_RAW within the container. But you can change that and other container technologies definitely keep CAP_NET_RAW within the container.

No.

Create a new user namespace and you have CAP_NET_RAW within your shiny new namespace.

The bug is already fixed and they have better things to do than messing with our trolling. :-)

I hope to see a mainline submission for public review of this soon.

The majority of OpenWRT/LEDE patches are gross hacks that need a major rework or a completely different approach. This is not the first patch of that kind.

Sadly, the author failed to read on the history of kdbus and AF_BUS.

Just using UNIX domain socks is not the solution. This is more or less what dbus currently does and has major issues with memory accounting and trusts.