Custom Query (8170 matches)
Results (184 - 186 of 8170)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3821 | fixed | download speed limit causes connection timeouts | ||
| Description |
Since version 3.1.3, setting a download speedlimit of 100 KB/s causes endless connection timeouts. As soon as I remove the limit, I get no timeouts at all. |
|||
| #8245 | rejected | Unusual behavior of estimated remaining time during upload/download. | ||
| Description |
I am using v3.5.3-nightly: |
|||
| #4204 | rejected | FileZilla Client (Windows) uses IPv6 in preference to IPv4 | ||
| Description |
I have several Windows clients running Windows XP Pro SP3 and Windows Vista SP1. I have FileZilla client 3.2.0 installed. All these machines have a dual IPv4 and IPv6 configuration as I am currently testing IPv6. My DNS server (Windows 2003 Server SP2) returns both IPv4 and IPv6 addresses for my servers when queried. My FileZilla sever (0.9.30) is running on a Windows XP SP3 machine, also with a valid IPv6 configuration. When I use the FileZilla client to try and connect to a server for which my DNS server can return both an IPv6 address and an IPv4 address, the FileZilla client always tries to use the IPv6 address in preference to the IPv4 address. This might not be an issue except that the FileZilla server does not seem to listen to/accept connections on its host's IPv6 address. As a result the client is not able to connect. I have tried changing the binding order on the client machines to make IPv4 come before IPv6 but it does not help. This seems like a bug to me. Surely use of IPv6 should at a minimum only be by explicit request? Ideally one could specify which to use as a default at the client level and maybe also with a host specific override. I imagine mixed environments are becoming quite common and this could become a big problem. |
|||
