So I’ve had ipv4 working since install (obviously), but one pain point I have is sometimes windows or android decides to use ipv6 over ipv4.
My ISP provided modem gives me a /56, at this time I don’t want to give my bridged containers world routable IPs. Like that’s the entire reason I have things the way I do.
So I have docker running with ipv6
"experimental": false,
"ipv6": true,
"fixed-cidr-v6": "fd00:69:420:8::/64",
"ip6tables": true
I’ve made a network used by the containers I need.
docker network create \
--driver "bridge" \
--opt "encrypted" \
--scope "local" \
--subnet "172.27.1.0/24" \
--subnet "fd00:69:420:42::/64" \
--ipv6 \
--attachable \
"external_edge"
The relevant containers get IPs in 172.27.1.0/24 and fd00:69:420:42::/64.
eth0 Link encap:Ethernet HWaddr 02:42:AC:1B:01:06
inet addr:172.27.1.6 Bcast:172.27.1.255 Mask:255.255.255.0
inet6 addr: fd00:69:420:42::8/64 Scope:Global
inet6 addr: fe80::42:acff:fe1b:106/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:207924 errors:0 dropped:0 overruns:0 frame:0
TX packets:223200 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:32793948 (31.2 MiB) TX bytes:29743646 (28.3 MiB)
Inside out connectivity seems to be fine.
TheVault:/# ping -4 google.ca
PING google.ca (142.251.32.67): 56 data bytes
64 bytes from 142.251.32.67: seq=0 ttl=118 time=20.570 ms
64 bytes from 142.251.32.67: seq=1 ttl=118 time=21.572 ms
^C
--- google.ca ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 20.570/21.071/21.572 ms
TheVault:/# ping -6 google.ca
PING google.ca (2607:f8b0:400b:804::2003): 56 data bytes
64 bytes from 2607:f8b0:400b:804::2003: seq=0 ttl=117 time=20.918 ms
64 bytes from 2607:f8b0:400b:804::2003: seq=1 ttl=117 time=13.735 ms
64 bytes from 2607:f8b0:400b:804::2003: seq=2 ttl=117 time=21.750 ms
^C
--- google.ca ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 13.735/18.801/21.750 ms
But I can’t connect to services from outside.
ipv4 is fine https://thevault.local:9043/#!/3/docker/dashboard
ipv6 is not https://[fe80::265e:beff:fe6b:ae54]:9043/#!/3/docker/dashboard OR https://[2607::]:9043/#!/3/docker/dashboard
Bridged to host and the host webUI itself on https://[fe80::265e:beff:fe6b:ae54]/ OR https://[2607::]/ works.
So specifically 6to6 routing from me into my NAS isn’t working.
Should I see anything in ip6tables -t mangle --list?
-t filter and -t nat are full, and I have ipv6 connectivity in containers so I think I’ve done everything right.