This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ipv6-wg@ripe.net/
[ipv6-wg] IPv6 only as default for next meeting
- Previous message (by thread): [ipv6-wg] IPv6 only as default for next meeting
- Next message (by thread): [ipv6-wg] Extension Headers / Impact on Security Devices
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Mon May 18 16:17:28 CEST 2015
Hi, On Mon, May 18, 2015 at 12:39:41PM +0000, Shane Kerr wrote: > I'm happy with your proposal for RIPE 71, of course, since I don't have > horrible VPN software from the 20th century. ;) Thing is, this wasn't actually the VPN software's doing, but DNS(64) - so if you try to access an IPv4-host *inside* the VPN, but try to resolve it using the public recursive DNS that you've been given, your client will receive an IPv6 address instead... With "full redirect VPN" this works (redirect DNS inside the VPN) but with "split tunnel" VPN, you're basically stuck between a rock and a hard place here - either you use the inside DNS, then your access to outside IPv4-only places fails (no DNS64), or you use the outside DNS, then see above... Gert Doering -- part time VPN software maintainer -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 811 bytes Desc: not available URL: </ripe/mail/archives/ipv6-wg/attachments/20150518/734cd653/attachment.sig>
- Previous message (by thread): [ipv6-wg] IPv6 only as default for next meeting
- Next message (by thread): [ipv6-wg] Extension Headers / Impact on Security Devices
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]