IPv6-only network at RIPE70
I'm glad to announce that there is a IPv6-only (with NAT64) network at RIPE70. Please note that this experimental network is not supported by the RIPE NCC or RIPE 67 Technical Team and is offered on a best-effort basis. How to connect: - Make sure IPv6 is enabled on your device - Connect to SSID: IPV6ONLYEXP - Enter the password: iknowbesteffort Please note that NAT64&DNS64 is used to provide connectivity to IPv4-only resources, so use DNS servers information provided by the network. If you see any connectivity issues: - connect to the 'normal' dual-stack one; - if connecting to dual-stack network solves the issue, please email me (furry13@gmail.com) with details, I'd love to know about any problems. General feedback (do you guys see any value in such an experiment, what was your experience etc) is appreciated. -- SY, Jen Linkova aka Furry
Sorry, a very important part was missed in my email: Big thanks to Cisco Systems (Eric Vynce, Steve Simlo and Andrew Yourtchenko in particular) for providing with NAT64 solution and to RIPE NCC for building this network and proving that IPv6 does work! IPv6-only network @RIPE would have never happened without their help! My apologies for not mentioning this in my email in the first place. On Mon, May 11, 2015 at 1:46 PM, Jen Linkova <furry13@gmail.com> wrote:
I'm glad to announce that there is a IPv6-only (with NAT64) network at RIPE70.
Please note that this experimental network is not supported by the RIPE NCC or RIPE 67 Technical Team and is offered on a best-effort basis.
How to connect:
- Make sure IPv6 is enabled on your device - Connect to SSID: IPV6ONLYEXP - Enter the password: iknowbesteffort
Please note that NAT64&DNS64 is used to provide connectivity to IPv4-only resources, so use DNS servers information provided by the network.
If you see any connectivity issues: - connect to the 'normal' dual-stack one; - if connecting to dual-stack network solves the issue, please email me (furry13@gmail.com) with details, I'd love to know about any problems.
General feedback (do you guys see any value in such an experiment, what was your experience etc) is appreciated.
-- SY, Jen Linkova aka Furry
-- SY, Jen Linkova aka Furry
I suspect Dropbox to hardcode their IP in their application. It's not working at all on ipv6-only. On the contrary, I'm pleasantly surprised to see that Cisco DTLS VPN works over NAT64. Thanks for giving us a sandbox, that is really interesting. On Mon, May 11, 2015 at 5:41 AM, Jen Linkova <furry13@gmail.com> wrote:
Sorry, a very important part was missed in my email:
Big thanks to Cisco Systems (Eric Vynce, Steve Simlo and Andrew Yourtchenko in particular) for providing with NAT64 solution and to RIPE NCC for building this network and proving that IPv6 does work! IPv6-only network @RIPE would have never happened without their help!
My apologies for not mentioning this in my email in the first place.
On Mon, May 11, 2015 at 1:46 PM, Jen Linkova <furry13@gmail.com> wrote:
I'm glad to announce that there is a IPv6-only (with NAT64) network at RIPE70.
Please note that this experimental network is not supported by the RIPE NCC or RIPE 67 Technical Team and is offered on a best-effort basis.
How to connect:
- Make sure IPv6 is enabled on your device - Connect to SSID: IPV6ONLYEXP - Enter the password: iknowbesteffort
Please note that NAT64&DNS64 is used to provide connectivity to IPv4-only resources, so use DNS servers information provided by the network.
If you see any connectivity issues: - connect to the 'normal' dual-stack one; - if connecting to dual-stack network solves the issue, please email me (furry13@gmail.com) with details, I'd love to know about any problems.
General feedback (do you guys see any value in such an experiment, what was your experience etc) is appreciated.
-- SY, Jen Linkova aka Furry
-- SY, Jen Linkova aka Furry
On Tue, May 12, 2015 at 2:50 PM, Jérôme Fleury <jerome@fleury.net> wrote:
I suspect Dropbox to hardcode their IP in their application. It's not working at all on ipv6-only.
Yeah, looks like that: furry@Wintermute:~>sudo tcpdump -i en0 -s 1500 -n 'net 64:ff9b::6ca0:0/120 or net 108.160.172.0/24' tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on en0, link-type EN10MB (Ethernet), capture size 1500 bytes 14:59:48.934365 ARP, Request who-has 108.160.172.193 tell 169.254.64.90, length 28 14:59:49.323255 ARP, Request who-has 108.160.172.204 tell 169.254.64.90, length 28 14:59:50.019231 ARP, Request who-has 108.160.172.193 tell 169.254.64.90, length 28 14:59:50.420251 ARP, Request who-has 108.160.172.204 tell 169.254.64.90, length 28 I'll follow up on this...
On the contrary, I'm pleasantly surprised to see that Cisco DTLS VPN works over NAT64.
Thanks for giving us a sandbox, that is really interesting.
Great to know, thanks for the feedback!
On Mon, May 11, 2015 at 5:41 AM, Jen Linkova <furry13@gmail.com> wrote:
Sorry, a very important part was missed in my email:
Big thanks to Cisco Systems (Eric Vynce, Steve Simlo and Andrew Yourtchenko in particular) for providing with NAT64 solution and to RIPE NCC for building this network and proving that IPv6 does work! IPv6-only network @RIPE would have never happened without their help!
My apologies for not mentioning this in my email in the first place.
On Mon, May 11, 2015 at 1:46 PM, Jen Linkova <furry13@gmail.com> wrote:
I'm glad to announce that there is a IPv6-only (with NAT64) network at RIPE70.
Please note that this experimental network is not supported by the RIPE NCC or RIPE 67 Technical Team and is offered on a best-effort basis.
How to connect:
- Make sure IPv6 is enabled on your device - Connect to SSID: IPV6ONLYEXP - Enter the password: iknowbesteffort
Please note that NAT64&DNS64 is used to provide connectivity to IPv4-only resources, so use DNS servers information provided by the network.
If you see any connectivity issues: - connect to the 'normal' dual-stack one; - if connecting to dual-stack network solves the issue, please email me (furry13@gmail.com) with details, I'd love to know about any problems.
General feedback (do you guys see any value in such an experiment, what was your experience etc) is appreciated.
-- SY, Jen Linkova aka Furry
-- SY, Jen Linkova aka Furry
-- SY, Jen Linkova aka Furry
On Tue, May 12, 2015 at 3:00 PM, Jen Linkova <furry13@gmail.com> wrote:
On Tue, May 12, 2015 at 2:50 PM, Jérôme Fleury <jerome@fleury.net> wrote:
I suspect Dropbox to hardcode their IP in their application. It's not working at all on ipv6-only.
Yeah, looks like that:
furry@Wintermute:~>sudo tcpdump -i en0 -s 1500 -n 'net 64:ff9b::6ca0:0/120 or net 108.160.172.0/24' tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on en0, link-type EN10MB (Ethernet), capture size 1500 bytes 14:59:48.934365 ARP, Request who-has 108.160.172.193 tell 169.254.64.90, length 28 14:59:49.323255 ARP, Request who-has 108.160.172.204 tell 169.254.64.90, length 28 14:59:50.019231 ARP, Request who-has 108.160.172.193 tell 169.254.64.90, length 28 14:59:50.420251 ARP, Request who-has 108.160.172.204 tell 169.254.64.90, length 28
Seems to be a know issue: https://www.dropboxforum.com/hc/communities/public/questions/203283805-IPv6-... "After checking in with our engineering team, unfortunately we can't commit to a timeline for IPv6 access right now. " However I do see some difference between 'not support v6' and 'hardcode v4 addresses' ;-\ -- SY, Jen Linkova aka Furry
On Tue, May 12, 2015 at 2:50 PM, Jérôme Fleury <jerome@fleury.net> wrote:
I suspect Dropbox to hardcode their IP in their application. It's not working at all on ipv6-only.
Heh, they are not hardcoding anything, they are just not consistent: 1) asking for AAAA for client.v.dropbox.com 15:10:32.233655 IP6 2001:67c:64:49:4c02:64ed:71e7:a16.62668 > nat64-ubuntu.ripemtg.ripe.net.domain: 54028+ AAAA? client.v.dropbox.com. (38) 15:10:32.234425 IP6 2001:67c:64:49:4c02:64ed:71e7:a16.58556 > nat64-ubuntu.ripemtg.ripe.net.domain: 28552+ AAAA? d.dropbox.com. (31) 15:10:32.270841 IP6 nat64-ubuntu.ripemtg.ripe.net.domain > 2001:67c:64:49:4c02:64ed:71e7:a16.58556: 28552 3/4/0 CNAME d.v.dropbox.com., AAAA 64:ff9b::6ca0:ace1, AAAA 64:ff9b::6ca0:acc1 (241) 15:10:32.279229 IP6 nat64-ubuntu.ripemtg.ripe.net.domain > 2001:67c:64:49:4c02:64ed:71e7:a16.62668: 54028 2/4/0 AAAA 64:ff9b::6ca0:accc, AAAA 64:ff9b::6ca0:acec (230) 2) but then asking for A only: 15:10:32.643915 IP6 2001:67c:64:49:4c02:64ed:71e7:a16.51052 > nat64-ubuntu.ripemtg.ripe.net.domain: 42675+ A? d.v.dropbox.com. (33) 15:10:32.647198 IP6 nat64-ubuntu.ripemtg.ripe.net.domain > 2001:67c:64:49:4c02:64ed:71e7:a16.51052: 42675 2/4/0 A 108.160.172.193, A 108.160.172.225 (201) 15:10:32.650615 ARP, Request who-has d.v.dropbox.com tell 169.254.64.90, length 28 -- SY, Jen Linkova aka Furry
Jen Linkova <furry13@gmail.com> writes:
If you see any connectivity issues: - connect to the 'normal' dual-stack one; - if connecting to dual-stack network solves the issue, please email me (furry13@gmail.com) with details, I'd love to know about any problems.
And some more content for http://wiki.test-ipv6.com would be good. "This site contains information on what has been tested in IPv6 environments. Most notably, things that work or fail in the IPv6 single-stack environment, or in environments such as NAT64/DNS64 or XLAT464." Jens -- ---------------------------------------------------------------------------- | Foelderichstr. 40 | 13595 Berlin, Germany | +49-151-18721264 | | http://blog.quux.de | jabber: jenslink@jabber.quux.de | --------------- | ----------------------------------------------------------------------------
participants (3)
-
Jen Linkova -
Jens Link -
Jérôme Fleury