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/[email protected]/
[ipv6-wg] 464XLAT / RFC 6877 [Re: IPv6 Only Testbed at RIPE68]
- Previous message (by thread): [ipv6-wg] IPv6 Only Testbed at RIPE68
- Next message (by thread): [ipv6-wg] 464XLAT / RFC 6877 [Re: IPv6 Only Testbed at RIPE68]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tore Anderson
tore at fud.no
Mon May 12 08:57:46 CEST 2014
Hi all, For those of you who are Linux users (or BSD/OS X hackers¹), and happen to encounter an application or service that doesn't appear to work correctly when connected to the IPv6-only network - do try and see if 464XLAT (RFC 6877) solves the problem before giving up and connecting to the default dual-stacked network. A Linux implementation can be found here: https://github.com/toreanderson/clatd I'd appreciate any feedback, suggestions, bug reports, and so on. I'm unfortunately not in Warszawa, but I am available on IRC (nick "tore"). [1] While clatd is developed and tested only on Linux, I believe it should be possible to port it to BSD/OS X. The actual RFC 6145 packet translations is performed by TAYGA (http://www.litech.org/tayga/) and as long as TAYGA works (I've never tried, but it is available in FreeBSD ports), it ought to be possible to adapt the currently Linux-specific commands in the clatd script that set up the network environment to their BSD/OS X counterparts. Patches are welcome! (Cc: opensource-wg) Tore * Marco Hogewoning > Welcome to Warsaw. Following the discussion at RIPE 66, and a > successful experoment in Athens last autumn, the IPv6 Working Group > is happy to provide you with an experimental network that is > configured to offer only IPv6. Please note this experimental network > is not supported by the RIPE NCC or RIPE 68 Technical Team. > > We encourage everybody to connect to this network and test any > websites, applications, hardware and software, and verify that they > operate when an IPv4 address is no longer available. > > Important: This network is an experiment and is offered on a > best-effort basis. We will try to maintain sufficient service levels > and are happy to look into and help troubleshoot any issues you may > encounter. If you rely on network connectivity for important > business, we recommend you connect to the regular RIPE Meeting > network. > > How to connect: > > - Make sure IPv6 is enabled on your device > - Connect to SSID: IPV6ONLYEXP (5GHz) or IPVONLYEXP2.4 (2.4 GHz) > - Enter the password: iknowbesteffort > > The network provides NAT64 translation to connect to legacy services > – please use the name server provided by the network to make use of > this feature. We suggest you leave IPv4 enabled as this will be the > scenario for most end users.
- Previous message (by thread): [ipv6-wg] IPv6 Only Testbed at RIPE68
- Next message (by thread): [ipv6-wg] 464XLAT / RFC 6877 [Re: IPv6 Only Testbed at RIPE68]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]