hypeit
May 6, 2023, 2:45pm
4
I would rather check if docker is not interfering the bridge in the first place.
Maybe your issue is similar to
I seted all routes I could think. But does not worked.
this one,
sudo iptables -I DOCKER-USER -i eth1 -o br0 -j ACCEPT
sudo iptables -I DOCKER-USER -o eth1 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
this one,
sudo iptables -I DOCKER-USER -i br0 -o enp7s0f0 -j ACCEPT
sudo iptables -I DOCKER-USER -o br0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
and this one.
sudo iptables -I DOCKER-USER -i eth1 -o enp7s0f0 -j ACCEPT
sudo iptables -I DOCKER-USER -o eth1 -m conntrack --cts…
When I wanted to make sure in my case I tried something like
flush-iptables.sh
#!/bin/bash
# Script is needed because my default firewall rules are messed up and after
# every restart, docker containers can't make connections to the host, notably
# preventing debuggers like xdebug from attaching.
# If networking fails in your containers but works in others, rm and re-create the
# docker network that container is bound to.
set -euo pipefailshow original
Just to make sure it was docker
Or better Linux Containers - LXD - Has been moved to Canonical