[Cyberduck-trac] [Cyberduck] #2539: IPv6 has a wrong default behaviour

[Cyberduck]

#2539: IPv6 has a wrong default behaviour
-----------------------+----------------------------------------------------
 Reporter:  anonymous  |        Owner:  dkocher 
     Type:  defect     |       Status:  reopened
 Priority:  high       |    Milestone:  3.1.3   
Component:  core       |      Version:  3.1.2   
 Severity:  major      |   Resolution:          
 Keywords:  IPV6       |  
-----------------------+----------------------------------------------------

Comment(by dkocher):

 Replying to [comment:3 jerome@…]:
 > IPv6 support is supposed to have the following behaviour :
 > - IPv6 should be tried first IF the host has an AAAA record AND
 localhost has a global IPv6 address (not just the local link one)
 > - If both A and AAAA records are avaible for the host, AAAA should have
 precedence
 > - UNLESS User is given explicit choice to default to IPv4
 >
 > My test showed that for an host beeing reachable on both protocols, also
 having both A and AAAA records, Cyberduck defaults to IPv4
 >
 > I couldn't find any setting to change this faulty behaviour.
 >
 > When given with an IPv6 adress, cyberduck rightfully uses IPv6.

 Can you direct me to the RFCs describing this? At my own setup this
 scenario not usable: With the `java.net.preferIPv6Addresses` property
 described above the `AAAA` takes precedence but I have no IPv6 routing
 connecting to the address therefore fails.

-- 
Ticket URL: <http://trac.cyberduck.ch/ticket/2539#comment:12>
Cyberduck <http://cyberduck.ch>
FTP, SFTP, WebDAV, Cloud Files and Amazon S3 Browser for Mac OS X.