Valid_lft forever preferred_lft interfaces After applying pipework: (eth1) ip aĤ98: eth0: mtu 1500 qdisc noqueue state UP group default To be able to reach your container from Internet, you will need to assign an IPv6 address from a subnet of your public IPv6.īy assigning IPv6 address to a new interface in the container (eth1), the IPv4 default route is removed and the new IPv6 default route will point to the new IPv6 default gateway via eth1.Ĭontainer interfaces before applying pipework: ip aġ: lo: mtu 65536 qdisc noqueue state UNKNOWN group default Sudo pipework br4 -i eth1 ip a a 2001:db8:44::FF/64 dev br4 Pipework allows more flexible network configuration: sudo docker run -t -i -name myimage /bin/bash You can accomplish access to the container through IPv6 using pipework. It is not recommended to do any kind of NAT in IPv6 environment, that defeats the purpose of IPv6. Seems like I need add route from docker0 bridged IPv6 traffic to eth0, but have no idea what exactly to do. IPv6 and IPv4 routing is enabled ( cat /proc/sys/net/ipv6/conf/default/forwarding gives 1 and cat /proc/sys/net/ipv6/conf/all/forwarding gives 1). TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
RX packets:1 errors:0 dropped:0 overruns:0 frame:0 TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 RX packets:90 errors:0 dropped:0 overruns:0 frame:0 TX packets:20269 errors:0 dropped:0 overruns:0 carrier:0 RX packets:78994 errors:0 dropped:0 overruns:0 frame:0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 nc -w 10 2a00:1450:4010:c07::71 80 outputs nc: connect to 2a00:1450:4010:c07::71 port 80 (tcp) timed out: Operation now in progress.įollowing this documentation ifconfig eth0 ifconfig docker0 ip -6 route show shows: eth0 Link encap:Ethernet HWaddr fa:16:3e:74:4a:b9 I have problems with routing traffic from Docker (version 1.5.0) container on IPv6 only host.
0 kommentar(er)
