Changes between Initial Version and Version 1 of Ticket #12723


Ignore:
Timestamp:
Jun 1, 2022, 10:53:22 AM (23 months ago)
Author:
QIU Quan
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #12723 – Description

    initial v1  
    1616> Destination IP of data connection does not match peer IP of control connection. Not binding source address of data connection.
    1717
    18 Having searched this message in the source code, I landed a function `CTransferSocket` :: `SetupPassiveTransfer`, and found that its `host` argument seems to be assigned in the function `CFtpRawTransferOpData` :: `ParsePasvResponse`.
     18Having searched this message in the source code, I arrived at a function `CTransferSocket` :: `SetupPassiveTransfer`, and found that its `host` argument seems to be assigned in the function `CFtpRawTransferOpData` :: `ParsePasvResponse`.
    1919
    2020Inside `ParsePasvResponse`, the condition to assign the `peerIP` from the control socket to the `host_` of the passive data connection is an ''un-routable data peer address'' as well as a ''routable control peer address''. Unfortunately, with all un-routable, internal addresses for both data and control, my scenario effectively bypasses this mechanism.