Closed beechfuzz closed 4 years ago
qdm12
commented
4 years ago Hello thanks for reporting the issue. I'm on Mullvad too so I hope I can assist you better. Anyway, searching for your error, I just found an openvpn config line to add to ignore all the ipv6 rules Mullvad pushes. I'll add at noon (in 2hrs) and you could then try without that ipv6 disabled docker config as well. It should make it work. š Will comment back once it's up.
qdm12
commented
4 years ago Can you please try with the image qmcgaw/private-internet-access:mullvad-disable-ipv6 and see if it works without the Docker ipv6 configuration line? If it does, I'll merge that in the latest docker image. Thanks in advance!
beechfuzz
commented
4 years ago That works!
One final question (totally unrelated): When do you think wireguard will be implemented (if at all)? Not trying to be a choosing beggar, just curious cuz I'm excited to try it with this.
qdm12
commented
4 years ago Actually that works but doesn't tunnel ipv6, which, let's face it, barely anyone uses, but still.
If your Docker is setup to use ipv6 (again, barely anyone uses that), then it is actually useful. I'll modify the code further to allow people to specify to tunnel Ipv6 for Mullvad (which, by the way, is the only provider to tunnel ipv6)... Anyway very niche but required case š
I quite like Wireguard too, I'm using it as my vpn server of choice. But back then, none of the providers supported it. There is an implementation in Go out there which I could plug in somehow. It is feasible, just a lot of changes to make as it's different IPs, ports, each provider has their own custom steps etc. I definitely have it stored at the back of my head, but I'd say at least 2-3 months (unless I get fired, then days š).
qdm12
commented
4 years ago Hello again, I pushed the changes I was talking about.
HOWEVER, researching your issue a bit more, can you please run on your host:
ls /proc/sys/net/ipv6/conf/all/ | grep ipv6On mine it returns disable_ipv6, but yours might be disable. If so, you should be able to run with
docker run -d --name="gluetun" \
--volume /opt/docker/volumes/gluetun:/gluetun \
--cap-add=NET_ADMIN \
--env VPNSP="mullvad" \
--env USER="<masked>" \
--env COUNTRY="USA" \
--env CITY="Dallas, TX" \
--env PORT_FORWARDING="on" \
--env PORT_FORWARDING_STATUS_FILE="/gluetun/forwarded_port" \
--sysctl net.ipv6.conf.all.disable=0 \
qmcgaw/private-internet-accessLet me know so that I can update the Wiki. I'll add that PR on ipv6 anyway to remove the need for that Docker run flag. Thanks!
beechfuzz
commented
4 years ago root@server:~# ls /proc/sys/net/ipv6/conf/all | grep ipv6
ls: cannot access '/proc/sys/net/ipv6/conf/all': No such file or directoryI had actually tried the --sysctl net.ipv6.conf.all.disable=0 option before, but the container threw an error at me:
docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"write sysctl key net.ipv6.conf.all.disable_ipv6: open /proc/sys/net/ipv6/conf/all/disable_ipv6: no such file or directory\"": unknown.Hm, what do you get with ls /proc/sys/net/? Maybe ipv6 is just not in your OS/kernel š¤
I get
bridge/ core/ ipv4/ ipv6/ mptcp/ netfilter/ nf_conntrack_max unix/
6RASi
commented
4 years ago I'm trying to get this to work with my Mullvad docker-compose.yml but I'm getting a similar error to the original when I try to run it through Portainer
http error: Error response from daemon: OCI runtime create failed: container_linux.go:341: creating new parent process caused "container_linux.go:1923: running lstat on namespace path \"/proc/25893/ns/net\" caused \"lstat /proc/25893/ns/net: no such file or directory\"": unknown (err=Error response from daemon: OCI runtime create failed: container_linux.go:341: creating new parent process caused "container_linux.go:1923: running lstat on namespace path \"/proc/25893/ns/net\" caused \"lstat /proc/25893/ns/net: no such file or directory\"": unknown) (code=500)
My PIA docker-compose is working fine
beechfuzz
commented
4 years ago Hm, what do you get with
ls /proc/sys/net/? Maybe ipv6 is just not in your OS/kernel š¤I get
bridge/ core/ ipv4/ ipv6/ mptcp/ netfilter/ nf_conntrack_max unix/
root@server:~# ls -al /proc/sys/net/
total 0
dr-xr-xr-x 1 root root 0 Sep 24 13:31 .
dr-xr-xr-x 1 root root 0 Sep 23 06:19 ..
dr-xr-xr-x 1 root root 0 Sep 24 13:31 bridge
dr-xr-xr-x 1 root root 0 Sep 24 16:16 core
dr-xr-xr-x 1 root root 0 Sep 24 13:31 ipv4
dr-xr-xr-x 1 root root 0 Sep 24 22:49 netfilter
-rw-r--r-- 1 root root 0 Sep 24 22:49 nf_conntrack_max
dr-xr-xr-x 1 root root 0 Sep 24 22:49 unixAlright that makes sense. Most likely you just don't have ipv6 in your Kernel. If you feel curious, you can follow these steps.
Anyway, I'll merge the pull request in latest so you should be able to run it without that ipv6 docker config line.
beechfuzz
commented
4 years ago You're the man! Thanks for being responsive and all your effort. Enjoy a beer on me (not literally -- that would be weird).
qdm12
commented
4 years ago @beechfuzz Cheers for the monthly beer! I'm in the process of reworking the Wiki and will merge my pull request when I'm done, that may take one more day.
@orion-LY do you mind creating another issue for your case as this seems, well, like another issue š And please share your compose configuration on that other issue (omit passwords) too.
qdm12
commented
3 years ago Hey @beechfuzz
You might be happy with https://github.com/qdm12/gluetun/pull/565 š For now it only supports Mullvad, I'm adding more as I write this!
TLDR: Added
--sysctl net.ipv6.conf.all.disable_ipv6=0to mydocker runcommand, but it throws an error1. Is this urgent?
2. What VPN service provider are you using?
3. What's the version of the program?
4. What are you using to run the container?
5. Command:
2 commands -- 1 with
--sysctl net.ipv6.conf.all.disable_ipv6=0and one without that.6. Extra information
Logs for the command with
--sysctl net.ipv6.conf.all.disable_ipv6=0:Logs for the command without
--sysctl net.ipv6.conf.all.disable_ipv6=0:Host OS: