[issue1661754] ftplib passive ftp problem on multihomed clients

Giampaolo Rodola' added the comment: > we do not want that the same (host, port) is used for > both control and data connections. I meant *port*, not (host, port). -- ___ Python tracker

[issue1661754] ftplib passive ftp problem on multihomed clients

Changes by Giampaolo Rodola' : -- assignee: -> giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue1661754] ftplib passive ftp problem on multihomed clients

Giampaolo Rodola' added the comment: Patch in attachment updates the previous one which no longer applies cleanly in py 3.3. The control connection address is used for *both* passive (PASV) and active (PORT) connections, which is the same approach I used in pyftpdlib. Removed test_source_addr

[issue1661754] ftplib passive ftp problem on multihomed clients

Changes by Mark Lawrence : -- versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.6, Python 3.0 ___ Python tracker ___ ___ Pytho

[issue1661754] ftplib passive ftp problem on multihomed clients

Giampaolo Rodola' added the comment: Issue 8594 is related with this one. -- superseder: -> Add a "source_address" option to ftplib ___ Python tracker ___ ___

[issue1661754] ftplib passive ftp problem on multihomed clients

Changes by Daniel Diniz : -- nosy: +giampaolo.rodola stage: -> test needed type: -> behavior versions: +Python 2.6, Python 3.0 -Python 2.5 ___ Python tracker ___