From MikroTik Wiki
< Manual:IP
Revision as of 07:44, 26 April 2019 by Krisjanisj (talk | contribs) (Labojums - no ir default, pec ugrade ar previous value yes -> remote)
Jump to navigation Jump to search


This menu controls if ssh server behaviour regarding port forward and authentication methods.


Property Description
allow-none-crypto (yes|no; Default: yes) Whether to allow connection if cryptographic algorithms are set to none.
always-allow-password-login (yes | no; Default: no) Whether to allow password login at the same time when public key authorization is configured.
forwarding-enabled (both | local | no | remote; Default: no) Allows to control which SSH forwarding method to allow:
  • no - SSH forwarding is disabled;
  • local - Allow SSH clients to originate connections from the server;
  • remote - Allow SSH clients to listen on the server and forward incoming connections;
  • both - Allow both local and remote forwarding methods.
host-key-size (1024 | 1536 | 2048 | 4096 | 8192; Default: 2048) What RSA key size to use when host key is being regenerated.
strong-crypto (yes | no; Default: no) Use stronger encryption, HMAC algorithms, use bigger DH primes and disallow weaker ones:
  • prefer 256 and 192 bit encryption instead of 128 bits;
  • disable null encryption;
  • prefer sha256 for hashing instead of sha1;
  • disable md5;
  • use 2048bit prime for Diffie Hellman exchange instead of 1024bit.


Property Description
export-host-key (key-file-prefix) Export public and private RSA/DSA keys to files. Command takes one parameter:
  • key-file-prefix - used prefix for generated files, for example, prefix 'my' will generate files 'my_rsa', '' etc.
import-host-key (private-key-file) Import and replace private DSA/RSA key from specified file. Command takes one parameter:
  • private-key-file - name of the private RSA/DSA key file
regenerate-host-key () Generated new and replace current set of private keys (DSA, RSA) on the router. Be aware that previously imported keys might stop working.


Note: When connecting from RouterOS built in client to router with strong crypto disabled, temporary strong crypto must be disabled on connecting router too. Reason is that strong crypto forces algorithms which are not supported when this feature is disabled.


Remote forwarding

To use remote forwarding from Linux host using OpenSSH client type in following command:

 ssh reamoteuser@remotehost -L port:remotehost:remoteport


  • remoteuser - username on the router
  • remotehost - routers address (router should be able to resolve host name if address is not an IP address)
  • port - local port that your host will listen on
  • remoteport - port on the router

If user requires telnet to router, but you do not want to allow it to be plain text, Following can be done:

ssh admin@ -L 3000:

now when user uses telnet localhost 3000" it will log in the router using telnet over encrypted tcp connection.


Note: we fully support SFTP v3 as described in draft-ietf-secsh-filexfer-02.txt other versions can cause problems

Local Forwarding

ssh -N -D <local_port> -l <user> <remote_address>


  • local_port - local port that your host will listen on
  • user - username on the router
  • remote_address - routers address

For example:

ssh -N -v -D 9999 -l admin

Now you can use local port 9999 to fetch files:

curl -x socks5h://localhost:9999

See also