April 6, 20251 yr Hi unraid team! I have tried and searched for several days and I am unable to figure out how to do the mentioned in the title. I have even reached out on the discord and was told the user base is very small and asked me to move to the forums. REASON: Tailscale does not stream jellyfin because I am under CGNAT. I am forced to use tailscale DERP severs. I have tried several times, and it doesn't work like it does for others in other parts of the world. According to https://tailscale.com/kb/1232/derp-servers, "Tailscale runs DERP relay servers distributed around the world to link your Tailscale nodes peer-to-peer as a side channel during NAT traversal, and as a fallback in case NAT traversal fails and a direct connection cannot be established." So ipv6 is my only option and reverse proxy on it. SETUP DETAILS: I can confirm I am able to connect to the unraid gui via http ipv6 remotely after setting ipv4+ipv6 in unraid gui and some settings in my OpenWrt router. I followed this guide and changed to macvlan -- unraid guide link When I inspect docker custom network bond0 it has no ipv6 enabled by default. I have no idea why this will be the case? I believe because of this bond0 setting when assigned to a container, is not getting ipv6 via dhcp. And for bridge it is enabled but it is not macvlan driver. root@Marcus:~# docker inspect network bridge [ { "Name": "bridge", "Id": "67da0ca0768313c1d78b6fcc9a2e0155dd2637ff448633d36d94f3895865ac42", "Created": "2025-04-06T15:31:37.995198845+05:30", "Scope": "local", "Driver": "bridge", "EnableIPv6": true, "IPAM": { "Driver": "default", "Options": null, "Config": [ { "Subnet": "172.17.0.0/16", "Gateway": "172.17.0.1" }, { "Subnet": "fd17::/64", "Gateway": "fd17::1" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": { #redacted rest of the result root@Marcus:~# docker inspect network bond0 [ { "Name": "bond0", "Id": "12d68ab11cc0c49db92450d6c1643ee0619eb7e65598992782278c6dc65a2f79", "Created": "2025-04-06T15:31:38.99571313+05:30", "Scope": "local", "Driver": "macvlan", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "192.168.86.0/24", "Gateway": "192.168.86.1", "AuxiliaryAddresses": { "server": "192.168.86.52" } } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": {}, "Options": { "parent": "vhost0" }, "Labels": {} } ] Error: No such object: network root@Marcus:~# EXPECTED RESULT: I have dhcpv6 setup on my openwrt and want each docker container to receive ipv6 via dhcpv6. From there, I can allow firewall rule to access it. As I confirmed previously, I am able to connect to unraid gui via ipv6. I wish to get the same result for each docker container, and I believe macvlan will help me achieve this. Kindly, please provide me with the steps involved in doing this. Thank you!
April 6, 20251 yr docker can't grab ip from dhcp server. You better have your reverse proxy ilsten on ipv6 and proxying request to upstream servers (containers) via ipv4. I think the better is to completly desactivate ipv6 on docker containers; as the way it's handled by docker and isp providing mostly dynamic ipv6 or even worse only a /64 makes it almost useless.
April 7, 20251 yr Author 12 hours ago, caplam said: docker can't grab ip from dhcp server. You better have your reverse proxy ilsten on ipv6 and proxying request to upstream servers (containers) via ipv4. I think the better is to completly desactivate ipv6 on docker containers; as the way it's handled by docker and isp providing mostly dynamic ipv6 or even worse only a /64 makes it almost useless. Can you please tell me how? I can follow instructions well. I have a domain and setup nginx. Please, thank you!
April 7, 20251 yr Author 15 hours ago, caplam said: docker can't grab ip from dhcp server. You better have your reverse proxy ilsten on ipv6 and proxying request to upstream servers (containers) via ipv4. I think the better is to completly desactivate ipv6 on docker containers; as the way it's handled by docker and isp providing mostly dynamic ipv6 or even worse only a /64 makes it almost useless. I can connect to my unraid login page via jellyfin.domain_name.com, but not jellyfin itself. My caddy config is as follows: jellyfin.domain.xyz, www.jellyfin.domain.xyz { reverse_proxy http://172.17.0.12:8096 } 172.17.0.12:8096 is internal jellyfin ip which is running on docker bridge network
April 7, 20251 yr Author @JorgeB Hi, I saw you commented on another post related to ipv6. Can you please help my containers get ipv6 via dhcpv6 or any other viable method for me? I am not sure, but this post here says to use macvlan for dhcp. Please support, thank you!
April 7, 20251 yr 1 hour ago, mans_ said: Can you please help my containers get ipv6 via dhcpv6 or any other viable method for me? Not really, out of my wheelhouse.
April 7, 20251 yr 4 hours ago, mans_ said: I can connect to my unraid login page via jellyfin.domain_name.com, but not jellyfin itself. My caddy config is as follows: jellyfin.domain.xyz, www.jellyfin.domain.xyz { reverse_proxy http://172.17.0.12:8096 } 172.17.0.12:8096 is internal jellyfin ip which is running on docker bridge network you have to reverse proxy to http://ip-of-unraid:port if using bridge or http://ip-of-container:port if using macvlan. You can't grab an ip v6 or v4 by dhcp with docker. It's not related to unraid but docker itslef. Edited April 7, 20251 yr by caplam
April 7, 20251 yr Author 20 minutes ago, caplam said: you have to reverse proxy to http://ip-of-unraid:port if using bridge or http://ip-of-container:port if using macvlan. You can't grab an ip v6 or v4 by dhcp with docker. It's not related to unraid but docker itslef. Then where only will we use the ipv4 of the jellyfin container? My docker containers dont have ipv6 which is the issue here. I use bridge network and it doesn't work. It still goes to the unraid webui Quote You better have your reverse proxy ilsten on ipv6 and proxying request to upstream servers (containers) via ipv4. this was your initial advice
April 9, 20251 yr I'm afraid i can't give you a step by step guide as i didn't do it myself. I was in the same situation but figured out that my isp had an option at 2€/month for having a public ipv4. So i didn't have to use ipv6. And i think i couldn't have done that as my registrar doesn't provide a way of dynamically updating AAAA records. I guess you should : - figure out if you have a static or dynamic ipv6 and what kind (/64 or /56). If it's static it should be easy. - open port 443 to your reverse proxy (ipv6). - reverse proxy to your facing service using ipv4 of your upstream server If your ipv6 is dynamic i have no idea how you can do it. You would need to be able to update dynamically ipv6 of your reverse proxy (depends on whether your registar permits it or not). Then you would need to open 443 You better ask on openwrt forums.
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.