FileZilla Client (Windows) uses IPv6 in preference to IPv4 - Fallback to IPv4 does not work in all cases
|Reported by:||Michael Gruber||Owned by:|
|Component version:||Operating system type:||Windows|
|Operating system version:||Windows 7 64bit|
Ticket #4204 is still an issue:
In preparation of the World IPv6 Day at 8 June 2011 we added AAAA Records in the DNS to the host names of our servers.
We can successful connect to all the services at the server via IPv6 - with the exception of the FileZilla Server, that does not offer IPv6 support.
This should not be an issue, because the Clients like web browsers or mail clients typically first try IPv6 and then fallback to IPv4, if no IPv6 connection can be established.
But the FileZilla Client does no fallback to the IPv4 address (what is also sent by the DNS server), FTP doesn't work any longer.
This could get an big issue and could cast a damning light on the FileZilla Client after IPv6 will be enabled by more and more ISP - not only at the World IPv6 Day!
Change History (6)
comment:3 by , 9 years ago
|Status:||closed → reopened|
|Summary:||FileZilla Client (Windows) uses IPv6 in preference to IPv4 - Fallback to IPv4 missing → FileZilla Client (Windows) uses IPv6 in preference to IPv4 - Fallback to IPv4 does not work in all cases|