| Subject: | FTP_PASSIVE not supported by network, supported by server unchecked. |
Net::FTP 2.77.
I'm not sure this bug has been reported before -- it /sounds/ like it
has, but in awkward connections where the FTP server permits passive
connections but the network configuration doesn't, and Net::FTP picks a
passive connection this happens when FTP_DEBUG=1
Net::FTP=GLOB(0x2793658)<<< 227 Entering Passive Mode
(174,36,119,242,9,190).
Net::FTP=GLOB(0x2793658)>>> STOR dealermade_inventory.csv
Can't use an undefined value as a symbol reference at
/usr/share/perl/5.10/Net/FTP/dataconn.pm line 54.
However, using "tshark -i eth0 -f tcp -R ftp"
7.639299 174.36.119.242 -> 192.168.1.201 FTP Response: 227 Entering
Passive Mode (174,36,119,242,9,190).
7.639535 192.168.1.201 -> 174.36.119.242 FTP Request: STOR
dealermade_inventory.csv
19.752635 174.36.119.242 -> 192.168.1.201 FTP Response: 425 Can't open
data connection.
181.555621 174.36.119.242 -> 192.168.1.201 FTP Response: 421 Timeout
(120 seconds): closing control connection.
181.555982 174.36.119.242 -> 192.168.1.201 FTP Response: 421 Terminating
connection.
You'll see the server is actually responding that it can't open a data
connection after the STOR, which is what Net::FTP should be registering
prior to the connection/ftp session termination. This would give
Net::FTP the ability to maybe fallback to ACTIVE transfer if passive
failed via 425.
--
Evan Carroll
perl@evancarroll.com
http://www.evancarroll.com