kenny114086 Posted August 4, 2021 Share Posted August 4, 2021 I have enable IPV6 for unraid, and the network setting can get the IPV6 address. But in docker setting I can't found "IPv6 custom network on interface br0 (optional)", only IPv4. Please HELP! Quote Link to comment
bonienl Posted August 4, 2021 Share Posted August 4, 2021 Can you show the output of ip -6 addr Quote Link to comment
kenny114086 Posted August 4, 2021 Author Share Posted August 4, 2021 Hi Bonienl Below is the output. root@Tower:~# ip -6 addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1000 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 9: eth0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 state UP qlen 1000 inet6 fe80::d250:99ff:fe67:83c0/64 scope link valid_lft forever preferred_lft forever 10: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000 inet6 2408:8256:5682:7a50:182f::2cd/128 scope global dynamic noprefixroute valid_lft 6794sec preferred_lft 6794sec inet6 fe80::d250:99ff:fe67:83c0/64 scope link valid_lft forever preferred_lft forever 15: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP inet6 fe80::42:63ff:fe15:ec76/64 scope link valid_lft forever preferred_lft forever 17: veth470a5d9@if16: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP inet6 fe80::dc65:4cff:fe8c:656c/64 scope link valid_lft forever preferred_lft forever 20: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UNKNOWN qlen 1000 inet6 fe80::fc54:ff:fe93:4aa9/64 scope link valid_lft forever preferred_lft forever 22: vethd66e27e@if21: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP inet6 fe80::688a:ceff:feea:5a1a/64 scope link valid_lft forever preferred_lft forever 24: vethefd6d3f@if23: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP inet6 fe80::2072:84ff:fe5e:7266/64 scope link valid_lft forever preferred_lft forever 25: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UNKNOWN qlen 1000 inet6 fe80::fc54:ff:fe0a:678e/64 scope link valid_lft forever preferred_lft forever 27: vetha296016@if26: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP inet6 fe80::3452:7bff:fead:180c/64 scope link valid_lft forever preferred_lft forever 28: vnet2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UNKNOWN qlen 1000 inet6 fe80::fc54:ff:fea8:3584/64 scope link valid_lft forever preferred_lft forever 29: vnet3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UNKNOWN qlen 1000 inet6 fe80::fc50:56ff:fe21:f209/64 scope link valid_lft forever preferred_lft forever 33: vethf578a38@if32: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP inet6 fe80::f0f8:8fff:fed0:34d8/64 scope link valid_lft forever preferred_lft forever 35: veth7e6ff9c@if34: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP inet6 fe80::144e:3ff:fef5:ebfc/64 scope link valid_lft forever preferred_lft forever 38: vethf02d455@if37: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP inet6 fe80::5874:c1ff:fe9c:fd4b/64 scope link valid_lft forever preferred_lft forever 40: veth0f75ea4@if39: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP inet6 fe80::684e:c6ff:fe67:2de5/64 scope link valid_lft forever preferred_lft forever Quote Link to comment
bonienl Posted August 5, 2021 Share Posted August 5, 2021 (edited) Thx. I need this one too ip -6 route show dev br0 Edited August 5, 2021 by bonienl Quote Link to comment
kenny114086 Posted August 5, 2021 Author Share Posted August 5, 2021 Please check. root@Tower:~# ip -6 route show dev br0 2408:8256:5682:7a50:1000::/68 proto ra metric 210 mtu 1480 pref medium 2408:8256:5682:830b:1000::/68 proto ra metric 210 mtu 1480 pref medium fe80::/64 proto kernel metric 256 pref medium multicast ff00::/8 proto kernel metric 256 pref medium default via fe80::21b:21ff:fe36:cfe proto ra metric 210 mtu 1480 pref medium Quote Link to comment
bonienl Posted August 5, 2021 Share Posted August 5, 2021 One more command to test ip -6 route show dev br0 2408:8256:5682:7a50:182f::2cd/128 Quote Link to comment
kenny114086 Posted August 5, 2021 Author Share Posted August 5, 2021 The ip6 address changed to 2408:8256:5682:830b:182f::2cd/128 after I rebooted the router, but no any output for both of these ip6 address. root@Tower:~# ip -6 route show dev br0 2408:8256:5682:830b:182f::2cd/128 root@Tower:~# ip -6 route show dev br0 2408:8256:5682:7a50:182f::2cd/128 Quote Link to comment
bonienl Posted August 5, 2021 Share Posted August 5, 2021 Ok, this explains why you are not seeing the IPv6 option under Docker. I need to make an adjustment in the detection logic, this will be in a future release. Quote Link to comment
kenny114086 Posted August 6, 2021 Author Share Posted August 6, 2021 I have a question why others can get the IPv6 for docker? And will the adjustment release on 6.9.3? Quote Link to comment
bonienl Posted August 6, 2021 Share Posted August 6, 2021 Usually address mask and route mask are equal, in your case these are different. The current detection logic doesn't take that into account. A correction will come in version 6.10 Quote Link to comment
kenny114086 Posted August 6, 2021 Author Share Posted August 6, 2021 Thanks, Bonienl Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.