Hello, I want to use IPV6 with my VPN provider within the custom docker network created for wg0. Unraid/Docker seems to have generated only an IPV4 subnet for the related custom network.

Also it seems that in root/config/wireguard/wg0.cfg no ipv6 route is added (interface up) or deleted (interface down):

PostUp=ip -4 route flush table 200

PostUp=ip -4 route add default via 10.133.136.143 dev wg0 table 200

PostUp=ip -4 route add 192.168.231.0/24 via 192.168.231.1 dev br0 table 200

PostDown=ip -4 route flush table 200

PostDown=ip -4 route add unreachable default table 200

PostDown=ip -4 route add 192.168.231.0/24 via 192.168.231.1 dev br0 table 200

Greetings and thank you in advance.

Yeah, the build in wireguard implementation doesnt support ipv6 at all atm. I still havent come around to attempt to fix it but if you need ipv6, ive a container in CA you can use for it.

3 minutes ago, Mainfrezzer said:

Yeah, the build in wireguard implementation doesnt support ipv6 at all atm. I still havent come around to attempt to fix it but if you need ipv6, ive a container in CA you can use for it.

Thank you for the fast response. So If I understand your docker, it comes with proxy/socks I need to connect to? It is only partly useful for my case since I need the "route" to be dead on interface disconnect and I'm not sure how I can implement this on Unraid.

Edited October 25, 2025Oct 25 by InternetD

Depends what you want to do. If you want other container to go through the VPN, you just select their network to be the vpn container like this


the privoxy http proxy and mircosocks socks5 proxy are more for like things hosted outside of unraid.

Smarttube on a firetv stick (i dont know if libretube supports proxy) or just a seperate firefox browser that goes through there on your pc.

Edited October 25, 2025Oct 25 by Mainfrezzer

Thank you, I will give it a try.

Edit: @Mainfrezzer Your docker works well, but sadly the web interface of the other docker I want to use refuses to work even after mapping all ports required accordingly within the template of your docker. I need to find a fix for that.

Edited October 25, 2025Oct 25 by InternetD

5 hours ago, InternetD said:

Thank you, I will give it a try.

Edit: @Mainfrezzer Your docker works well, but sadly the web interface of the other docker I want to use refuses to work even after mapping all ports required accordingly within the template of your docker. I need to find a fix for that.

did you add the ip range of your lan/the network youre trying to access the container gui from, to the template of the wireguard container?

13 hours ago, Mainfrezzer said:

did you add the ip range of your lan/the network youre trying to access the container gui from, to the template of the wireguard container?

If you meant that, yes I did.

Which container is it, where the gui isnt working?

2 hours ago, Mainfrezzer said:

Which container is it, where the gui isnt working?

https://github.com/linuxserver/docker-qbittorrent/pkgs/container/qbittorrent

i see why, 8080 is "blocked/already used" by privoxy and the gui runs on 8080.

You can change the privoxy port by changing this variable





Edit: if you get the "unauthorized" message in the browser, add

WebUI\HostHeaderValidation=false

to the qBittorrent.conf under [Preferences]

Edited October 26, 2025Oct 26 by Mainfrezzer

55 minutes ago, Mainfrezzer said:

i see why, 8080 is "blocked/already used" by privoxy and the gui runs on 8080.

You can change the privoxy port by changing this variable

I tried to change the port in either one but said web gui stays unreachable. I'm looking right now into it again to see if I have not goofed a port or something.

@Mainfrezzer Well looks like I did an error on my side yesterday and got the web gui worked (forgot to change the related setting/port within the qbittorent webgui itself). How do I pass the needed port from the wireguard client toward qbitorrent?

Edited October 26, 2025Oct 26 by InternetD

they share the same "interface", every port that you map to the wireguard container goes also to the qbittorent container. So if you run something on 5023/tcp, you map that to the wireguard client and it will reach the attached qbittorrent container, same with 38282/udp for example, for lan that is. Same for the vpn connection, everything that hits the wireguard ip of the container, hits qbittorrent aswell, if its listening on that port, no template modification needed

Edited October 26, 2025Oct 26 by Mainfrezzer

20 minutes ago, Mainfrezzer said:

they share the same "interface", every port that you map to the wireguard container goes also to the qbittorent container. So if you run something on 5023/tcp, you map that to the wireguard client and it will reach the attached qbittorrent container, same with 38282/udp for example, for lan that is. Same for the vpn connection, everything that hits the wireguard ip of the container, hits sonar aswell, if its listening on that port.

Wel it doesnt seem that ports on the tunnel can reach the qbitorrent docker. My VPN provider gives me port 59963 UDP and TCP but I cant get it through to qbitorrent.

You might have to set the variable in the qBittorrent template for the incoming port



Torrenting isnt my strong expertise but it should work absolutely fine from the logs as its binding properly to the wireguard interface ip (10.123.0.2 and fc00:123::2), as long as your provider does forward it to your client.

Edited October 26, 2025Oct 26 by Mainfrezzer