copying file between directories with /tool fetch gives timeout

RouterOS Scripting
1

This has been asked before and there have been post with a roudabout solution but it does not seem to work.

I need to copy files between directories on my router (LTE12, OS version 7.16.1) with usb memory inserted. The solutions which were given so far, and which seem to work use the /tool fetch mode=ftp address=[gatewayIP] pointing the src-path and dst-path to the file to copy and file to save

my command and resulting error are:

/tool fetch address=gatewayIP src-path="routeros-7.15.3-arm.npk" dst-path="usb1-part2/sources/test.npk"  mode=ftp  
  status: failed

failure: connection timeout

src-path file lives in “usb1-part2/sources”. As the CH-LTE12 only has 16MB ( :frowning: ) of local storage, the currently available space on the device is 2MB. Ram however is available up to 170MB.

Whatever I try (adding user and password, increating timeout value, adding full path, etc) I always get the same error.

Any help highly appreciated!

2

Why you do not download and save already the file on correct place instead of download on another place?

3

Try using localhost as the IP, and make sure 127.0.0.1 is allowed in /ip/firewall/filter (and recent defaults generally allow it). While could a be a few things why this does not work… firewall blocking it be 1st to look at.

Also note that in 7.17, if you’re downloading RouterOS packages to install locally, that’s ain’t going to work in 7.17 without changing device-mode.

4

Fair point!

But given MT's recent focus on NAS things... some "copy" and "move" are still missing, which results in these kludgey solutions like FTP+fetch.

5

If I'm connected by with winbox of course I put files at the right spot directly, but I'm asking this question because I want to do some management by SMS messages. As an example I used a firmware file, but most of the time I'll be using this for storing fallback backups (new versions) and so on.

6

I’ve tried 127.0.0.1 but also the same error. It could be that this is because lo is not setup correctly althought I have not changed anything manually.

Could you please give me the firewall rule(s) which are required to allow access with 127.0.0.1/lo
Are for lo to work other settings (/ip/address, /interface/bridge, etc) required?

7

It appeared that, probably while setting up the firewall, the loopback rule was moved to below the “defconf: drop all not coming from LAN” rule. Moving it above this rule the loopback device could be used again and the copy command worked again.
Thanks for pointing me to the firewall!

8

Good to hear, it did seem like the firewall. I just thought there be a good chance you both had the default firewall & the loopback rule be in the right spot. Without config, guessing isn’t always 100% accurate :slight_smile:.

If you’re only use FTP for the copy… you might consider restricting FTP to just localhost allowed-address= in /ip/services. While firewall was actually overly blocking FTP here… the 2nd level of protection of /ip/services’s allowed-address= is worth considering.

9

Thanks for the advise and warning, I indeed forgot to limit the FTP service to local access (127.0.0.1) only. Also created an ‘ftp-user/pw’ only allowed on 127.0.0.1 to be used in scripts.
Thanks again for your valuable help!