Custom Query (8170 matches)
Results (385 - 387 of 8170)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#4193 | rejected | Active connection via UPNP Internet gateway device | ||
Description |
It would be excellent if FileZilla Client would connect in active mode via UPNP Internet gateway device |
|||
#7948 | duplicate | Active ftp over socks proxy implemented incorrectly | ||
Description |
In Filezilla 3.5.3, specify active ftp and no fallback, and a socks5 proxy. Connect to a ftp server, this is done correctly over the socks proxy. Download something, and observe that a *passive* data connection is created over the socks proxy instead of an active one. |
|||
#1179 | Active mode data connection is made from the wrong port | |||
Description |
According to the FTP specification (RFC0959), in active FTP mode, the data connection should be made from port L-1, where L is the port that the server is listening for control connections (see section 3.2 Establishing Data Connections, paragraph 1). This should be true for every active mode transfer. FileZilla Server attempts to bind the outgoing port as per specification, but fails to do this when another active mode data connection exists. The second connection will get port L+1, and if a third connection is opened, then it will get an arbitrary OS-assigned port. Versions:
0.9.4, 0.9.8a, 0.9.19)
To reproduce:
host to the same server host.
-n" on the client host. Expected behavior:
port 21.
Observed behavior:
port 21.
unspecified port. Cause:
requested local port is already used by another socket.
setsockopt(socket, SOL_SOCKET, SO_REUSEADDR, ...) call, passing TRUE as the option value, before binding the socket. |