On Tue, May 12, 2015 at 2:50 PM, Jérôme Fleury <[email protected]> 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 <[email protected]> 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 <[email protected]> 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 ([email protected]) 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
