I have a bridge on my host (just like docker0 and even though you can use this for a minimal test you can replicate on any other bridge that you may create on your host).
If one runs curl --interface docker0 google.com on their host everything is fine and a response gets back.
But if one does the same thing, from within a container (with net=host) they will get Failed to connect to google.com port 80: No route to host.
I tracked the tcp connection and can clearly see that in the container after the initial SYN_SENT (which I see on the physical interface connected) the connection is somehow dropped, but by who? and why?
Any clues would be much appreciated:D