Docker ip multicast how to#

The FritzBox has a static route for 10.0.0.0 255.255.255.0 192.168.1.1.Fancy Docker orchestration systems, like Kubernetes or DC/OS, have networking layers that can be setup for complicated ingress and load balancer configurations. PostDown = iptables -D FORWARD -i %i -j ACCEPT iptables -D FORWARD -o %i -j ACCEPT iptables -t nat -D POSTROUTING -o ens3 -j MASQUERADE PostUp = iptables -A FORWARD -i %i -j ACCEPT iptables -A FORWARD -o %i -j ACCEPT iptables -t nat -A POSTROUTING -o ens3 -j MASQUERADE

22 dev ens3 proto kernel scope link src Link/ether 02:42:91:ad:db:f2 brd ff:ff:ff:ff:ff:ffģ7: wg0: mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000 Valid_lft 2597782sec preferred_lft 2597782secĤ: docker0: mtu 1500 qdisc noqueue state DOWN group default PostDown = iptables -D FORWARD -i %i -j ACCEPT iptables -D FORWARD -o %i -j ACCEPT iptables -t nat -D POSTROUTING -o enp3s0 -j MASQUERADE Ģ: ens3: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

PostUp = iptables -A FORWARD -i %i -j ACCEPT iptables -A FORWARD -o %i -j ACCEPT iptables -t nat -A POSTROUTING -o enp3s0 -j MASQUERADE Inet6 fe80::8a7b:703c:eb38:12c0/64 scope link noprefixrouteĢ1: docker0: mtu 1500 qdisc noqueue state DOWN group default Link/ether b4:96:91:20:65:4d brd ff:ff:ff:ff:ff:ffĥ: mesh-bridge: mtu 1500 qdisc noqueue state UP group default qlen 1000 Server A: # I stripped devices that are unreleatedĢ: enp3s0: mtu 1500 qdisc mq master mesh-bridge state UP group default qlen 1000 Valid_lft forever preferred_lft ip routeġ92.168.0.0/22 dev eth0 proto kernel scope link src ping 10.0.0.1 Ip link add docker-shim link mesh-bridge type macvlan mode bridge One last thing, docker container that only have the default network are able to reach Server B.ĭevice Details: Docker Container: # how I created the macvlan

Docker ip multicast how to#

I'm also open for suggestions how to rebuild the network from scratch I would imagine that there is something wrong with my iptables or the macvlan device itself. The think is, I'm able to get all connections to work (e.g. That broke my routing via the bridge that I used with fastd. That way normal devices as well as docker container where able to reach Server B.īecause of package loss (>6%) of my local internet lately, fastd stopped working (package loss of over 89%) and I tried replacing fastd with wireguard.īut wireguard only works on Layer 3. I used to run fastd on Server A & B (Server B was IP 192.168.1.2) and had a bridge device on Server A that managed local ethernet, docker macvlan and the tap device from fastd.

192.168.2.x for Docker Containers run on Server A (later more on that one).

192.168.1.x for servers with static IPs.

It's DHCP is configured with a network mask of 22. Now my local network has a FritzBox with IP: 192.168.0.1.

Server B: a VPS with debian 11.3 (5.10.0 kernel - also has wireguard support).

Server A: a local NAS running RHEL 8.5 (5.17.1 kernel - so it has native wireguard support) local IP 192.168.1.1.