On Tue, May 12, 2015 at 3:00 PM, Jen Linkova <[email protected]> wrote: > 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
Seems to be a know issue: https://www.dropboxforum.com/hc/communities/public/questions/203283805-IPv6-Support- "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
