Tip: Use Plink in Putty for Bastion Access

Symptom:

    When we first to set up plink in putty to bypass bastion.  We often get such error

  "incoming packet was garbled on decryption"

Solution:

   There are quite a few reasons for that.  One of reason is that on the first time. plink need users to consent if store key in cache or not.  As it is on proxy command, thus users can't input, thus we can get this  "incoming packet was garbled on decryption" which is nothing related
To fix this, we run below command to plink know, next time plink won't ask again.

$ plink opc@<bastion server> -nc <target host>:22
The server's host key is not cached in the registry. You
have no guarantee that the server is the computer you
think it is.
The server's ssh-ed25519 key fingerprint is:
ssh-ed25519 255 d7:56:12:9f:2a:ee:d2:55:24:5a:73:dc:a0:f2
If you trust this host, enter "y" to add the key to
PuTTY's cache and carry on connecting.
If you want to carry on connecting just once, without
adding the key to the cache, enter "n".
If you do not trust this host, press Return to abandon the
connection.
Store key in cache? (y/n) y