Cannot add an IPSec proposal due to timeout

Hello,

We are trying to setup a simple IPSec tunnel, and we cannot add the ipsec proposal. When we execute this:

/ip ipsec proposal
add auth-algorithms=sha256 enc-algorithms=aes-256-cbc name=my-proposal
pfs-group=none

It dos nothing, and after 1 minute or so the operation times out. Also, executing:

/ip ipsec proposal print

Gives similar result: it does not return anything, and we need to cancel the operation (ctrl+c) to get the prompt back.
We tried using winbox but could not add the proposal either.
We have mikrotik v6.38.4.
At first, we thought the operation was taking too long because of the high network load, but we tried today when workload was almost zero and got same result.
Any ideas? Where to look for also would help, given that no error is given, just timeout.

I had a similar issue on a different hardware and RouterOS version with /ip route anything, and a reboot has solved it. So first try a reboot, and if it doesn’t help, upgrade to at least 6.40.8, as 6.38.4 is quite old.

Ok, tried today again after a restart, but unfortunately got the same results. We are going to perform the upgrade, try again and share the results here again.
Meanwhile, any other suggestion will be much appreciated.
Thanks a lot!

Hello again,

we tried today to perform the upgrade from 6.38.4 to 6.42.7 but we could not achieve it.

Here is what we have tried:

  1. Downloaded the 6.42.7 package for our router model (RB1100AHx4: https://download.mikrotik.com/routeros/6.42.7/routeros-arm-6.42.7.npk), and when we tried to FTP the file to the root folder “/” it just disappears after the upload completed. We tried this with Filezile client and also from Winbox client, with the same results. Alternatively, we tried to upload to another location, so we created a folder “/upgrade” and uploaded the package into it. The upload completed and the file was there, but when we moved to the root folder (as it is needed for the upgrade) it just disappears.
  2. Tried to perform the upgrade directly with Winbox from: Quickset > Check for updates > Download&Install, but the upgrade does not succeed: it downloads the files and reboots, but nothing is done. No error indication on logs, but my suspicious is that the same as in 1 happened: the files got erased after download, because if we monitor the free space it grows from 37Mb occupied as the download is in progress up to around 49Mb, but suddenly it just becomes 37Mb again.
  3. Last resort is to upgrade win Netinstall but the device was not showing into Netinstall UI. Our maintenance window was closing so we could not try much with this alternative, so we wrapped our work and left everything working so everyone can get to work again.

It is strange that the files disappears after being moved to the root folder. Also, something curious: we had to perform physical reset of the router and restore manually all configurations because our “admin” user had not “full” permissions but only “write” permissions, and hence could not try to do the upgrade nor FTP files. There was though a user “system” with “full” permissions, but we did not created such user, and it actually shows no last login date. This fact, along with some strange behavior we observed (like HTTP calls randomly giving 400 error because of a “wrong header”, and some failed attempts to login observed in system logs with random users like “admin”, “root”, “default”, etc.) gives us the idea that maybe we got “hacked” or something similar and that is why we had limited permissions. Is it possible that an upgrade is being interrupted by some exploit? Has anyone ever observed something like this?

We need to try again with a Netinstall to upgrade the system, because we still cannot add the IPSec rules to create our tunnel. In the mean time, any additional information or ideas would be much appreciated. Thanks all!

Heraldo.

It looks like a malware infection others have experienced too, so netinstall is your only chance. I’d recommend to use another device to debug the netinstall on the PC while not under time constraints before trying again on the production device.