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] Link to publicly available DNS64/NAT64 implementations
- Previous message (by thread): [ipv6-wg] Link to publicly available DNS64/NAT64 implementations
- Next message (by thread): [ipv6-wg] NAT64 Config on Cisco in Conference WLAN
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tore Anderson
tore at fud.no
Fri May 15 00:06:38 CEST 2015
* Marc Blanchet > On 14 May 2015, at 11:41, Jan Zorz wrote: > > > Dear IPv6 WG, > > > > As promised during the IPv6 WG meeting at RIPE70, I'm sending the > > link with information how to test remotely different > > implementations of NAT64 that we are running in Go6lab: > > > > http://go6lab.si/current-ipv6-tests/nat64dns64-public-test/ > > > > Ecdysis is the weakest one and somehow a bit buggy, > > why is it? > > FYI, Ecdysis has been integrated into OpenBSD pf and is now part of > the OpenBSD bistro. That version is more stable. So I would suggest > to use an openbsd platform to do testing and get best results > (compared to the linux one). Or, if there is a desire to run the implementation Linux in the first place, I'd suggest Jool (http://jool.mx), which is actively maintained. BTW all the NAT64 prefixes given on the page are incorrect, at least if the ping6 test targets given are correct the NAT64 prefixes are all /96es, not /64s. Tore
- Previous message (by thread): [ipv6-wg] Link to publicly available DNS64/NAT64 implementations
- Next message (by thread): [ipv6-wg] NAT64 Config on Cisco in Conference WLAN
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]