[ipv6-wg] IPv6 Only Network at RIPE 67
- Previous message (by thread): [ipv6-wg] IPv6 Only Network at RIPE 67
- Next message (by thread): [ipv6-wg] IPv6 Only Network at RIPE 67
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tore Anderson
tore at fud.no
Wed Oct 16 15:47:45 CEST 2013
* Gert Doering > On Wed, Oct 16, 2013 at 04:11:38PM +0300, Marco Hogewoning wrote: >> I had one user who had OpenVPN overriding the DNS resolver setting, which breaks NAT64 and in turn breaks everything else (including the VPN). > > It will break NAT64 while the VPN is up, but it should not break the VPN > itself (as the DNS settings *should* be restored when the VPN ends, and > while it's up, it will not look at DNS). > > What platform was this on, and which "gui bundle"? As mentioned, there's > a few different versions floating around (2.1, 2.3+ and 3.0 code basis). I think Marco is referring to a tweet I made, but I did not mean to say that the VPN breaks. It does not. It's just the VPN pre-empts the DNS64, and since only specific (my) IPv4/IPv6 networks are pushed by the VPN, this means that I can no longer reach IPv4-only content on the internet (IPv4-only content in my own network works fine, through the VPN, and all IPv6 content is also fine - through the VPN for my own networks, or directly for the rest of the internet). I didn't try contacting the OpenVPN server through the NAT64 (native IPv6 in both the server and client end now), but I could try that as well. I don't expect it to fail though, so unless you hear anything to the contrary, assume it worked fine. Tore
- Previous message (by thread): [ipv6-wg] IPv6 Only Network at RIPE 67
- Next message (by thread): [ipv6-wg] IPv6 Only Network at RIPE 67
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]