Skip to content
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

Feedback: IPv6 #70

Closed
Vexz00 opened this issue May 5, 2024 · 3 comments
Closed

Feedback: IPv6 #70

Vexz00 opened this issue May 5, 2024 · 3 comments

Comments

@Vexz00
Copy link

Vexz00 commented May 5, 2024

I'm referring to this:
⚠️ IPv6 is an experimental Docker feature, no thorough test was done to ensure there is no IP/DNS leak with Gluetun configured with IPv6. Feel free to create an issue or pull request if you have some testing done and can confirm.
Wiki-source

tl;dr: IPv6 with Gluetun works fine and there's no DNS leak from what I can tell.

Longer version:

  • I live in Germany.
  • I have dual stack (IPv4 + IPv6). → In Germany I get a GUA starting with 2003:...
  • I use Mullvad VPN.
  • I usually let my DNS leak intentionally because I rather use NextDNS for some additional filtering instead of the privacy aspect you gain from routing your DNS through the VPN tunnel. But for this test I used Gluetun's Unbound.

Here's my docker compose script that I used:

version: "3.9"

services:
  gluetun:
    image: qmcgaw/gluetun:v3.38
    container_name: Gluetun_VPN
    network_mode: "bridge"
    cap_add:
      - NET_ADMIN
    sysctls:
      - net.ipv6.conf.all.disable_ipv6=0
    environment:
      - VPN_SERVICE_PROVIDER=mullvad
      - VPN_TYPE=wireguard
      - WIREGUARD_PRIVATE_KEY=<MY PRIVATE KEY>
      - WIREGUARD_ADDRESSES=10.66.243.129/32,fc00:bbbb:bbbb:bb01::3:f380/128
      - SERVER_CITIES=Zurich
    ports:
      - 1080:1080
    restart: always

  socks5:
    image: serjs/go-socks5-proxy:latest
    container_name: Go-Socks5-Proxy
    network_mode: "service:gluetun"
    depends_on:
      - gluetun
    restart: always

The proxy settings in Firefox were set accordingly to connect to the docker container.

Results:

@qdm12
Copy link
Owner

qdm12 commented Jul 29, 2024

That's awesome, thank you for reporting this 👍 I've put a link to this issue in the ipv6 document in a5c112d. Also, your screenshots seem to be gone, would you mind pasting them directly as a comment so they are hosted on github? Thanks!!

@qdm12 qdm12 closed this as completed Jul 29, 2024
Copy link

Closed issues are NOT monitored, so commenting here will NOT be seen by the maintainer.
If you think this is still unresolved and have more information to bring, please create another issue.

This is an automated comment setup because @qdm12 is the sole maintainer of this project
which became too popular to monitor closed issues for additional comments.

@Vexz00
Copy link
Author

Vexz00 commented Jul 29, 2024

That's awesome, thank you for reporting this 👍 I've put a link to this issue in the ipv6 document in a5c112d. Also, your screenshots seem to be gone, would you mind pasting them directly as a comment so they are hosted on github? Thanks!!

@qdm12 I hope I'm doing this right.

IP-adresses
Feedback_IPv6_·Issue#70_·qdm12gluetun-wiki–_Li_2024-07-29_17-36-17

DNS leak test
Feedback_IPv6_·Issue#70_·qdm12gluetun-wiki–_Li_2024-07-29_17-37-48

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants