[opensource-wg] [ipv6-wg] 464XLAT / RFC 6877 [Re: IPv6 Only Testbed at RIPE68]

Most recent Androids (4.3 and up I think) support 464XLAT out of the box too...

Regards
 
Bob
07958 318592
 
Life's for sharing... and what I like to share the most is a smile


-----Original Message-----
From: ipv6-wg-bounces at ripe.net [mailto:ipv6-wg-bounces at ripe.net] On Behalf Of Tore Anderson
Sent: 12 May 2014 07:58
To: Marco Hogewoning; ipv6-wg at ripe.net IPv6
Cc: opensource-wg at ripe.net
Subject: [ipv6-wg] 464XLAT / RFC 6877 [Re: IPv6 Only Testbed at RIPE68]

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.

NOTICE AND DISCLAIMER
This e-mail (including any attachments) is intended for the above-named person(s).  If you are not the intended recipient, notify the sender immediately, delete this email from your system and do not disclose or use for any purpose.  
 
We may monitor all incoming and outgoing emails in line with current legislation. We have taken steps to ensure that this email and attachments are free from any virus, but it remains your responsibility to ensure that viruses do not adversely affect you. 

EE Limited
Registered in England and Wales
Company Registered Number: 02382161
Registered Office Address: Trident Place, Mosquito Way, Hatfield, Hertfordshire, AL10 9BW