@007revad commented on GitHub (Dec 20, 2024): Try this version: https://github.com/007revad/Synology_ContainerManager_IPv6/releases/tag/v2.0.5 Let me know if it works.

kerem commented

2026-03-07 19:07:59 +03:00

Author

Owner

@389377616 commented on GitHub (Dec 21, 2024):

尝试此版本： https ://github.com/007revad/Synology_ContainerManager_IPv6/releases/tag/v2.0.5

如果有效的话请告诉我。
命令查了下nas的ipv6地址，然后把查询到的那个64结尾的参数修改进脚本里的cidr参数里，然后运行脚本，运行完了以后使用docker network inspect bridge命令查询，发现EnableIPv6：true，这个说明应该是已经打了docker的ipv6了，但是我进了好几个网络模式是bridge的容器，进去使用sysctl net.ipv6.conf.all.disable_ipv6命令测试，结果全部返回的是net.ipv6.conf.all.disable_ipv6 = 1，这样我也搞不清是啥情况了，是cidr参数填写的有问题还是啥情况。

@389377616 commented on GitHub (Dec 21, 2024): > 尝试此版本： [https ://github.com/007revad/Synology_ContainerManager_IPv6/releases/tag/v2.0.5](https://github.com/007revad/Synology_ContainerManager_IPv6/releases/tag/v2.0.5) > > 如果有效的话请告诉我。命令查了下nas的ipv6地址，然后把查询到的那个64结尾的参数修改进脚本里的cidr参数里，然后运行脚本，运行完了以后使用docker network inspect bridge命令查询，发现EnableIPv6：true，这个说明应该是已经打了docker的ipv6了，但是我进了好几个网络模式是bridge的容器，进去使用sysctl net.ipv6.conf.all.disable_ipv6命令测试，结果全部返回的是net.ipv6.conf.all.disable_ipv6 = 1，这样我也搞不清是啥情况了，是cidr参数填写的有问题还是啥情况。 ![IPv6](https://github.com/user-attachments/assets/ef0dd461-96f8-45ec-9957-30310d0eddfa) ![sh](https://github.com/user-attachments/assets/5bd1f28b-db04-49c0-afbc-4774bda2fb53)

kerem commented

2026-03-07 19:07:59 +03:00

Author

Owner

@389377616 commented on GitHub (Dec 21, 2024):

After I changed the network mode of a container from bridge to host, I found that ipv6 was enabled when I queried it from the container. However, I would prefer that the container have an ipv6 URL in bridge mode, because if all containers use host mode, some container port numbers will conflict with the ports used by the nas host.

@389377616 commented on GitHub (Dec 21, 2024): After I changed the network mode of a container from bridge to host, I found that ipv6 was enabled when I queried it from the container. However, I would prefer that the container have an ipv6 URL in bridge mode, because if all containers use host mode, some container port numbers will conflict with the ports used by the nas host.

kerem commented

2026-03-07 19:07:59 +03:00

Author

Owner

@007revad commented on GitHub (Dec 22, 2024):

This is strange. I've only ever been able to enable IPv6 on the bridge network, and not the host network. People have asked me how to enable IPv6 on the host network and I've been telling them it's not possible.

I wonder if Container Manager only allows the bridge network to use IPv6 while Synology's Docker only allows the host network to use IPv6.

@007revad commented on GitHub (Dec 22, 2024): This is strange. I've only ever been able to enable IPv6 on the bridge network, and not the host network. People have asked me how to enable IPv6 on the host network and I've been telling them it's not possible. I wonder if Container Manager only allows the bridge network to use IPv6 while Synology's Docker only allows the host network to use IPv6.

kerem commented

2026-03-07 19:07:59 +03:00

Author

Owner

@389377616 commented on GitHub (Dec 22, 2024):

This is strange. I've only ever been able to enable IPv6 on the bridge network, and not the host network. People have asked me how to enable IPv6 on the host network and I've been telling them it's not possible.

I wonder if Container Manager only allows the bridge network to use IPv6 while Synology's Docker only allows the host network to use IPv6.

I'm not sure about this. I haven't used Container Manager on DSM 7.2. The Docker on DSM 7.1 has ipv6 in the container in host mode. It was available before I used the script. I haven't used ipv6 successfully in bridge mode.

@389377616 commented on GitHub (Dec 22, 2024): > This is strange. I've only ever been able to enable IPv6 on the bridge network, and not the host network. People have asked me how to enable IPv6 on the host network and I've been telling them it's not possible. > > I wonder if Container Manager only allows the bridge network to use IPv6 while Synology's Docker only allows the host network to use IPv6. I'm not sure about this. I haven't used Container Manager on DSM 7.2. The Docker on DSM 7.1 has ipv6 in the container in host mode. It was available before I used the script. I haven't used ipv6 successfully in bridge mode.

kerem commented

2026-03-07 19:07:59 +03:00

Author

Owner

@389377616 commented on GitHub (Dec 22, 2024):

Could it be that the cidr parameter I wrote in the script is incorrect? I am not particularly clear about the ipv6 cidr parameter. I used the ip -6 route show command to obtain the local ipv6, found the one ending with 64 and filled it into the script. I don't know if it has anything to do with this. I have a suggestion: can the cidr parameter be obtained directly when the script is running, instead of being manually entered by the user?

@389377616 commented on GitHub (Dec 22, 2024): Could it be that the cidr parameter I wrote in the script is incorrect? I am not particularly clear about the ipv6 cidr parameter. I used the ip -6 route show command to obtain the local ipv6, found the one ending with 64 and filled it into the script. I don't know if it has anything to do with this. I have a suggestion: can the cidr parameter be obtained directly when the script is running, instead of being manually entered by the user?

kerem commented

2026-03-07 19:07:59 +03:00

Author

Owner

@007revad commented on GitHub (Dec 25, 2024):

You could try 240e::/64

@007revad commented on GitHub (Dec 25, 2024): You could try 240e::/64

kerem commented

2026-03-07 19:07:59 +03:00

Author

Owner

@389377616 commented on GitHub (Dec 25, 2024):

You could try 240e::/64

It still doesn't work. After writing 240e::/64 into the script, docker cannot be started directly after running the script. I went into the two configuration files /var/packages/Docker/etc/dockerd.json and /var/packages/Docker/target/config/dockerd.json and changed 240e::/64 to 240e::1/64 before starting docker. However, ipv6 is still not normal in bridge network mode.

@389377616 commented on GitHub (Dec 25, 2024): > You could try 240e::/64 It still doesn't work. After writing 240e::/64 into the script, docker cannot be started directly after running the script. I went into the two configuration files /var/packages/Docker/etc/dockerd.json and /var/packages/Docker/target/config/dockerd.json and changed 240e::/64 to 240e::1/64 before starting docker. However, ipv6 is still not normal in bridge network mode.

kerem commented

2026-03-07 19:07:59 +03:00

Author

Owner

@cca2878 commented on GitHub (Sep 15, 2025):

Same situation on DSM7.2. In the container, "sysctl net.ipv6.conf.all.disable_ipv6" returns 1.
But ContainerManager seems enable ipv6 on "host" network defaultly, no need for any action.

@cca2878 commented on GitHub (Sep 15, 2025): Same situation on DSM7.2. In the container, "sysctl net.ipv6.conf.all.disable_ipv6" returns 1. But ContainerManager seems enable ipv6 on "host" network defaultly, no need for any action.