I have almost no info. How are you starting the container? docker-compose? If you aren't binding the container to a network or ip address, you are binding it to 0.0.0.0 which is all network interfaces. I don't have enough info to know what 10.0.3.1 is but the output of ip a would help.
I am starting with this script:
#!/bin/bash
IP_LOOKUP="$(ip route get 8.8.8.8 | awk '{ print $NF; exit }')" # May not work for VPN / tun0
IPv6_LOOKUP="$(ip -6 route get 2001:4860:4860::8888 | awk '{ print $10; exit }')" # May not work for VPN / tun0
IP="${IP:-$IP_LOOKUP}" # use $IP, if set, otherwise IP_LOOKUP
IPv6="${IPv6:-$IPv6_LOOKUP}" # use $IPv6, if set, otherwise IP_LOOKUP
DOCKER_CONFIGS="/srv/dev-disk-by-id-ata-Micron_1100_MTFDDAV256TBN_17501A32891E-part3/dockerconfig/piHole"
echo "IP: ${IP} - IPv6: ${IPv6}"
# Default ports + daemonized docker container
docker run -d \
--name pihole \
-p 53:53/tcp -p 53:53/udp -p 80:80 \
-v "${DOCKER_CONFIGS}/pihole/:/etc/pihole/" \
-v "${DOCKER_CONFIGS}/dnsmasq.d/:/etc/dnsmasq.d/" \
-e ServerIP="$IP" \
-e TZ="Europe/Berlin" \
-e WEBPASSWORD="jule123" \
--restart=always \
pihole/pihole:latest
docker logs pihole 2> /dev/null | grep 'password:'
# -e ServerIPv6="${IPv6:-$(ip -6 route get 2001:4860:4860::8888 | awk '{ print $10; exit }')}" \
# -e VIRTUAL_HOST="${IP}":81 \
Display More
ip -a tells me:
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 90:1b:0e:fc:2c:60 brd ff:ff:ff:ff:ff:ff
inet 192.168.177.3/24 brd 192.168.177.255 scope global enp0s31f6
valid_lft forever preferred_lft forever
inet6 2a00:xxxx:4509:ac00:xxxx:eff:fefc:2c60/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 2662sec preferred_lft 2662sec
inet6 fe80::921b:eff:fefc:2c60/64 scope link
valid_lft forever preferred_lft forever
3: lxcbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 00:16:3e:00:00:00 brd ff:ff:ff:ff:ff:ff
inet 10.0.3.1/24 brd 10.0.3.255 scope global lxcbr0
valid_lft forever preferred_lft forever
4: wgnet0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000
link/none
inet 10.192.122.1/24 scope global wgnet0
valid_lft forever preferred_lft forever
5: br-6566530af5f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:6b:a9:a1:aa brd ff:ff:ff:ff:ff:ff
inet 172.18.0.1/16 brd 172.18.255.255 scope global br-6566530af5f3
valid_lft forever preferred_lft forever
inet6 fe80::42:6bff:fea9:a1aa/64 scope link
valid_lft forever preferred_lft forever
6: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:9e:09:26:34 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
inet6 fe80::42:9eff:fe09:2634/64 scope link
valid_lft forever preferred_lft forever
7: br-05e0294fb85d: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:ee:85:07:6a brd ff:ff:ff:ff:ff:ff
inet 172.31.0.1/16 brd 172.31.255.255 scope global br-05e0294fb85d
valid_lft forever preferred_lft forever
inet6 fe80::42:eeff:fe85:76a/64 scope link
valid_lft forever preferred_lft forever
8: br-1549d5198bb3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:e1:6c:ce:a8 brd ff:ff:ff:ff:ff:ff
inet 172.19.0.1/16 brd 172.19.255.255 scope global br-1549d5198bb3
valid_lft forever preferred_lft forever
inet6 fe80::42:e1ff:fe6c:cea8/64 scope link
valid_lft forever preferred_lft forever
...
88: macvtap0@enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 500
link/ether 52:54:00:e5:86:5d brd ff:ff:ff:ff:ff:ff
inet6 fe80::5054:ff:fee5:865d/64 scope link
valid_lft forever preferred_lft forever
90: veth4e3b6e3@if89: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-bceb55143ce1 state UP group default
link/ether 46:c0:c1:36:4d:20 brd ff:ff:ff:ff:ff:ff link-netnsid 13
inet6 fe80::44c0:c1ff:fe36:4d20/64 scope link
valid_lft forever preferred_lft forever
91: macvtap1@enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 500
link/ether 52:54:00:84:97:d6 brd ff:ff:ff:ff:ff:ff
inet6 fe80::5054:ff:fe84:97d6/64 scope link
valid_lft forever preferred_lft forever
95: vethf2b1d18@if94: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-6566530af5f3 state UP group default
link/ether 76:d2:7a:a1:bf:de brd ff:ff:ff:ff:ff:ff link-netnsid 7
inet6 fe80::74d2:7aff:fea1:bfde/64 scope link
valid_lft forever preferred_lft forever
97: vethe474ade@if96: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-6566530af5f3 state UP group default
link/ether 46:f4:93:1b:6c:fe brd ff:ff:ff:ff:ff:ff link-netnsid 17
inet6 fe80::44f4:93ff:fe1b:6cfe/64 scope link
valid_lft forever preferred_lft forever
99: veth22debcf@if98: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-6566530af5f3 state UP group default
link/ether fa:98:00:a6:6e:e7 brd ff:ff:ff:ff:ff:ff link-netnsid 5
inet6 fe80::f898:ff:fea6:6ee7/64 scope link
valid_lft forever preferred_lft forever
101: veth28f4b14@if100: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-6566530af5f3 state UP group default
link/ether 3a:9d:b4:c1:11:8d brd ff:ff:ff:ff:ff:ff link-netnsid 18
inet6 fe80::389d:b4ff:fec1:118d/64 scope link
valid_lft forever preferred_lft forever
Display More
So, it is lxcbr0
Quote
Why would you purge it after I told you it wasn't causing the problem? You could try disabling all NAT networks in the kvm plugin. It shouldn't start a dnsmasq listener on that network then.
That was before you said it.
Quote
A bridge network defined in the plugin or a bridge network interface defined at the OMV network level? The latter should be used and is described thoroughly in the kvm guide.
A bridge defined in the plugin.
The guide states, what I need to do. I am a bit worried though regarding the remark that " If you have services configured on the host with this network interface (for example, Wireguard), you will need to reconfigure them to work with the bridge"
What except for wireguard could be affected?
PostUp = iptables -A FORWARD -i wgnet0 -j ACCEPT; iptables -A FORWARD -o wgnet0 -j ACCEPT; iptables -t nat -A POSTROUTING -o enp0s31f6 -j MASQUERADE
PostDown = iptables -D FORWARD -i wgnet0 -j ACCEPT; iptables -D FORWARD -o wgnet0 -j ACCEPT; iptables -t nat -D POSTROUTING -o enp0s31f6 -j MASQUERADE
So, I would have to replace the enp0s31f6 by br0?
Best regards,
Hendrik