Bridge Problem With Docker

My bridge adaptor was working fine until I installed Docker, at which point it stopped forwarding traffic through itself.

[@TallPaulTech]

I don't proof-watch these things until I upload them, hence the unedited hocking up. You get that.

[@fghdfghdfghdfg]

"My bridge adaptor was working find"... in the description ... "My bridge adapter was working fine" ? 😂

[@FuzzyKaos]

I always appreciate your videos, thanks for posting!

[@BradleyHerbst]

I really appreciate videos like these where you show your troubleshooting processes. Thanks man!!

[@dingokidneys]

I always learn something about networking when I watch these videos, even if it's just "Oh that's a thing I have to look into more deeply."

[@backslash777]

It sounds like there is bridge firewalling going on. Basically out of the box it should go along the diagram you showed, but you can push bridged frames through netfilter by setting /proc/sys/net/bridge/bridge-nf-call-iptables to 1. Maybe the Docker does that behind the scenes. And maybe it is something other, but 10 years back we did transparent firewalling using this technique by filtering bridged traffic using iptables.

[@TallPaulTech]

That's the setting I wanted to mention because I looked at it at the time, but couldn't remember it when making the video. I think I toggled it with no effect though.

[@5mxg]

That's why I really like LXC for things that can be done with it.

[@apalrdsadventures]

every system I have that runs Docker becomes a networking nightmare, it's very inconsiderate of ... basically everyone

[@hgbugalou]

I'm playing with docker in my home lab too and while it's cool I find it's networking pretty clunky out of the box.

[@TallPaulTech]

Yeah, I'm just starting to use it more, finally. The network side of it does seem a bit hacked together, as you say.

[@SuperSerNiko97]

@@TallPaulTech I was using Docker for some services in the past before switching to Proxmox and one annoying thing that Docker did is that if the interface went down for whatever reason, when it came back up it just got ignored and I had to manually restart it.

[@mihumono]

Yeah, docker usually is a mess with firewall rules.

[@RK-ly5qj]

I can say that networking in docker sucks so much... Definitely designers didn't consult with network engineers xD

[@90hijacked]

Honestly the more i use podman the more excited i am for it, i am so sorry that a professional networking guy has to suffer through the nonsense they do to iptables... 🤣

[@martink.6872]

Not gonna pretend I understand the depths of docker or networking on that level, but I didn't get why at the diagram at 4:06 it didn't get on to 'Forward Bridge' in the bridge layer when the request wasn't meant for the local process? Why did it hit the IP rules then? You didn't go into further detail there or I just didn't get it.

[@dasgoll]

Which Linux distro is this?

[@rogo7330]

Did not know that you can just flush the whole ruleset. I guess I was just not paying attention, since basically everything that can be executed from a command line can be put into the config. nftables documentation sucks ass, not gonna lie.

[@fghdfghdfghdfg]

Docker is a cnut, I am a dumb cnut with docker, but following basic instructions I couldn't get docker containers access to the internet.... was a bigger problem with systemd-resolve (like wtf!) and ended up using --net=host to run containers. why does systemd need to fuck with DNS?!?! Argh!!