Custom Query (8073 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (274 - 276 of 8073)

Ticket Resolution Summary Owner Reporter
#1989 client: Override IP used in PASV connect Alexander Schuch puddle
Description

Servers behind NAT may give the wrong IP when they give the host/port info in their response to the client PASV.

I just experimented, and I can simply substitute the original server IP instead of using the one the server passed in the response.

I think this would make a nice option.

I'm seeing this matter when the server's NAT gateway can fix the outbound info in unencrypted channel (so I have no problem there), but the server's NAT gateway can't fix it in encrypted channel, so I can't connect unless I hack the code in CFtpControlSocket::List to switch IPs.

I think it would be nifty to have an Advanced option something like

"Use original Server IP in PASV connection"

for this case, to avoid having to hack in the cpp code myself :)

I might be able to submit a code patch for it, if I can (a) figure out the original server IP (which shouldn't be hard, but when I was hacking, I knew the server IP and just put in a hardcoded one, so I didn't solve this part), and (b) figure out the GUI stuff (probably much the harder part).

FtpControlSocket.cpp, v1.76 circa lines 1306-1309

if (pData->bPasv) {

pData->host = "99.99.99.99"; hack, should fetch

original server IP

if PASV create the socket & initiate outbound

data channel connection

if

(!m_pTransferSocket->Connect(pData->host,pData->port))

{

#2005 Timestamp in message log window Alexander Schuch anonymous
Description

Is there any way of turning on a timestamp in the message log window so I can see exactly when I connected, disconnected, etc. Basically, I want to know when every single occurrence happened.

Example: [20:30:04] Status: Connecting to 127.0.0.1 ... [20:30:10] Error: Unable to connect! [20:30:11] Status: Waiting to retry... (999 retries left)

Which shows me that at 8:30pm, I tried to connect to localhost and failed.

#2011 Allow a specific range of ports to use for PASV connection Alexander Schuch rickst29
Description

It seems that I must currently set my firewall to allow outgoing connections on ANY port > 1024. Could we please allow the user to specify a limited range of ports for Filezilla Client to use, allowing the firewall to be configured more tightly? Maybe the GUI could be integrated with Feature Request 875817, also related to PASV connections. And, my thanks for this great software!

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.