-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue when using Ipv6 inhome #19
Comments
I do not have a device available with IPv6 so unfortunately I am unable to test this myself.
2:
After that, click the JackettVPN container and restart it. |
Well, thanks for that fast response. I am not quite sure if we you should kill ipv6 in the container if somebody want to use the docker container on an other type of host/system with full dual-stack internet (ipv4+6). After some time I found a way to ignore the all ipv6 stuff that my vpn provider pushed to me. These lines should go in the openvpn (.ovpn) config file.
If someone is really paranoid, it would be good to fully disable ipv6 so no traffic can leak with ipv6 outside the ipv4 tunnel. A -e variable would be nice to disable or enable ipv6 at the startup. Many thanks for your hard work to maintain this. An other error I had was somehting with udp..then I swichted in the ovpn to tcp and it works now. Maybe at some point I will create a new issue for that. |
Thanks for letting me know what should be included in the config files! |
This commit adds a new environment variable that allows users to enable IPv6 in the container. By default IPv6 will be disabled and can be enabled by setting the environment variable DISABLE_IPV6 to 0. Closes issue #19 (hopefully)
I've added a new environment variable called 'DISABLE_IPV6'. Please also remove the following lines you added to your ovpn config file to see if this new environment variable indeed works as expected.
|
I updated and add all missing Variable and so on.. So all litte note in the readme for all who are using a vpn provider with ipv6 support in config files should be good then. |
Every config I was tring I got the same error at the end. Do you know how to stop adding these ipv6 routes since docker on unraid doesnt use any ipv6 connectivity ?
My host is an unraid machine.
The text was updated successfully, but these errors were encountered: