New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IPv6 has a wrong default behaviour #2539
Comments
How do you conclude it does not work? I have never tested because I don't have a IPV6 network here but in theory it should work for SFTP. |
I tested several IPv6 Accessible FTP Sites and haven't found any issue. |
IPv6 support is supposed to have the following behaviour :
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. |
I second that, with build 3.1.2 (4500). A is preferred over AAAA. If you need access to a testing server with both A and AAAA records or any other help with this, David, let me know. Any idea for a fix timeline? Thanks, Dominik |
According to (http://java.sun.com/j2se/1.5.0/docs/guide/net/ipv6_guide/index.html#ipv6-related) which also applies to Cyberduck:
To test IPv6 you therefore have to set the Using Passive FTP there may be problems connecting, as we do not currently support the IPv6 FTP extensions to parse a IPv6 address in response to |
Thanks for the update, David. I tried your suggestion. Following this document (http://developer.apple.com/documentation/Java/Reference/Java_InfoplistRef/Articles/JavaDictionaryInfo.plistKeys.html), in the Regarding the PASV problems, I can confirm them. It fails for example when using an explicit IPv6 address. From my point of view, that's not such a high priority issue as PASV mode could be less urgently required when you use IPv6. |
Replying to [comment:7 d-r@…]: |
That trick worked, now the connection is made to the IPv6 address, that's good. But it looks like a Bookmark's Active/Passive Setting is ignored. That's why LS works, but transfers always fail with "Cannot assign address". |
Replying to [comment:3 jerome@…]:
Can you direct me to the RFCs describing this? At my own setup this scenario not usable: With the |
I tested the nightly, works for me. Great! Thanks a lot, good work. I had to apply the address selection tweak, but then it works nicely against a ProFTPd server. Regarding address selection, according to this article [1] it should be RFC 3484. [1] http://www.cisco.com/web/about/ac123/ac147/archived_issues/ipj_9-3/ipv6_internals.html |
I will not currently change the default behaviour. However you can change the preference using the
This allows you to change the configuration without editing the |
Follow-up in #14286. |
Hi, despite the 'defaults' fix, at the moment 3.8.1 does not work with an IPv6 only SSH server, using a host name that has both A and AAAA records:
Connect to godzilla.terena.org -> Network Error: Connection failed
Connecting to the bare address (2001:610:148:dead::6) works fine.
Connecting to a hostname that ONLY lists a AAAA record (godzilla.ipv6.terena.org) also works fine...
FYI this is 10.6.6.
Thanks.
The text was updated successfully, but these errors were encountered: