Bug ID 1112109: Unable to retrieve SCP files using WinSCP or relative path name

Last Modified: May 29, 2024

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
13.1.5, 13.1.5.1, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 17.0.0, 17.0.0.1, 17.0.0.2

Fixed In:
17.1.0, 16.1.4, 15.1.9

Opened: Jun 03, 2022

Severity: 3-Major

Related Article: K000134769

Symptoms

When you attempt to retrieve a file with WinSCP, you receive an error dialog and the session will be terminated: "SCP Protocol error: Invalid control record (r; elative addresses not allowed) Copying files from the remote side failed." If you attempt to transfer a file by the relative path with a command line utility the transfer will fail with the message: "relative addresses not allowed"

Impact

Cannot use WinSCP to retrieve files such as packet captures, log archives, or other diagnostic data from the BIG-IP system.

Conditions

-- Running BIG-IP version with a fix for ID 915981 -- Using WinSCP set to use SCP protocol to retrieve files from a BIG-IP system. -- Using a relative remote path to transfer a file with the command line SCP utility.

Workaround

Use a command line SCP tool that allows specifying an absolute path for the source and/or destination file (a path that starts with a forward slash /), when the source and/or destination locations are a BIG-IP device. You may use WinSCP in SFTP mode if the user ID is permitted to do so.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips