Quentin McGaw

Oh boy! Sorry to disappoint, but Gluetun is really really not designed for such use case. There would be quite a bit of gymnastics to do firewall and routing wise...

- `WIREGUARD_PRIVATE_KEY` yes - `WIREGUARD_PRESHARED_KEY` I guess so - `WIREGUARD_ADDRESS` meh not really, an attacker can't do much with it anyway right? Also why do you guys see an interest...

> Keeping the existing IPv4 block and adding an additional WIREGUARD_ADDRESS line with the IPv6 block Note you can't set an env twice, you need to have it as a...

Since `AllowedIPs = 0.0.0.0/0,::0/0` is already set in the code, the only difference is the `[Interface]`'s `Address` having only the IPv4 address and not the IPv6 one. So I think...

I think the container was broken as it wouldn't set any address at all for Wireguard. I just fixed it in https://github.com/qdm12/gluetun/commit/61afdce788c8eb8896bb15a3276808ac819055f5 sorry about that. Please try with the corresponding...

Yes it's definitely `ip6tables` blocking something. If you don't mind me asking, can you get me what you get when you try to get something over IPv6, with the firewall...

Ah ok so `Firewall off: uses vpn IPv4 address, uses public IPv6 address` probably means it's using the non VPN IPv6 address. I think I found what's missing. 59a3a072e0fd7cead8ec78c74f284012fd124d0a adds...

I'm afk right now, but maybe try with the firewall disabled, is the ipv6 address the one from the vpn server or yours? Maybe this time the firewall does block...

> I have gluetun connected to my router and have access to the network, nothing points to it being a router issue. **Route** issue, not the same as *router* 😉...

> With the firewall off in gluetun ipv4 responds to icmp while ipv6 does not reply I'm not sure pinging gluetun is relevant here. The issue here is about tunneling...