On the previous posts, we have haveused VyOS as our default gateway and our NAT device. We were connecting straight to the console of the VM, where we could apply any changes. Imagine that we have many devices that we want to manage and maintain. Connecting every time to the HyperVisor make thing difficult and time consuming. On real life scenarios we also have various Linux VMs like VyOS where we have to console into them or Cisco Devices like Cisco Router, Swiches, ASA, Call Managers (CUCM) etc. where we could physically connect to them using a console cable.
All those networking devices support SSH (Secure Shell). It is a secure method to remote login to another computer. Normally it requires a username and password that we have previosuly setup on the machine we want to connect. There is also the Telnet option, but the connection is not secure and someone using a packet sniffer can intercept sensitive information on that session, for example the username and password.
There are various applications that can be used for SSH connection. The most popular ones are Putty (Windows - free to use), Teraterm (Windows - open source) and SecureCRT (Windows,MACOS,Linux - $99.00 USD). SecureCRT is a great tool, where you can run script/commands automating many simple networkign tasks, for example once I am logged in show me the CPU usage. I am using 7.3.7 version at work (MAC version) and it has some really cool features, other similar free applications do not have. The current SecureCRT version is 8.5.2 (January 2019). On my next labs I will use Putty, and maybe Multi Putty Manager, which allows multiple putty connections on different tabs.
I recently came accross an great multi-remote tool, where you can have your SSH, Telnet, RDP, VNC connections in one place, called mRemoteNG and is presented on a newer post
We will start with the basics of Putty first.
We will go through the basic setup of the MSI installer. The Portable version (Putty.exe) also works really well.
The most useful option of Putty, is that we can log every session on a text file. Every command we type and every output is displayed on that file. This is very useful when someone more senior (for example during Cisco TAC cases) we can see which commands were applied in order to get our problem solved. In case of a misconfiguration, we can go to the log file and check what we have actually misconfigured.
We will use wildcards and we will specify names that include date and time, as well as the hostname for better administration.
The log files can be specified under Session > Logging
Every time we do a change, we have to select the Default Setings under session and Press save.
Under WIndows Appearance, we can change the Font type and size
We can also change the Foreground and Background Color under Winwod > Colours
Don't forget to save the changes.
Now on the Session section, we can type a hostname or an IP Address to connect using SSH or another protocol.
THe first time we wil try to connect we will get a warning, that the remote host key is not trusted by Putty. We can press "Yes" to save it on Putty's cache.
We can see that after login in, we arrive to the same session as if we were using the console. As you can imagine this is great, since we can copy/paste commands, an option that is not available with th console.
The log file, we discused earlier shows the same information as the SSH Window.
All those networking devices support SSH (Secure Shell). It is a secure method to remote login to another computer. Normally it requires a username and password that we have previosuly setup on the machine we want to connect. There is also the Telnet option, but the connection is not secure and someone using a packet sniffer can intercept sensitive information on that session, for example the username and password.
There are various applications that can be used for SSH connection. The most popular ones are Putty (Windows - free to use), Teraterm (Windows - open source) and SecureCRT (Windows,MACOS,Linux - $99.00 USD). SecureCRT is a great tool, where you can run script/commands automating many simple networkign tasks, for example once I am logged in show me the CPU usage. I am using 7.3.7 version at work (MAC version) and it has some really cool features, other similar free applications do not have. The current SecureCRT version is 8.5.2 (January 2019). On my next labs I will use Putty, and maybe Multi Putty Manager, which allows multiple putty connections on different tabs.
I recently came accross an great multi-remote tool, where you can have your SSH, Telnet, RDP, VNC connections in one place, called mRemoteNG and is presented on a newer post
We will start with the basics of Putty first.
We will go through the basic setup of the MSI installer. The Portable version (Putty.exe) also works really well.
The most useful option of Putty, is that we can log every session on a text file. Every command we type and every output is displayed on that file. This is very useful when someone more senior (for example during Cisco TAC cases) we can see which commands were applied in order to get our problem solved. In case of a misconfiguration, we can go to the log file and check what we have actually misconfigured.
We will use wildcards and we will specify names that include date and time, as well as the hostname for better administration.
The log files can be specified under Session > Logging
Every time we do a change, we have to select the Default Setings under session and Press save.
We can also change the Foreground and Background Color under Winwod > Colours
Don't forget to save the changes.
Now on the Session section, we can type a hostname or an IP Address to connect using SSH or another protocol.
THe first time we wil try to connect we will get a warning, that the remote host key is not trusted by Putty. We can press "Yes" to save it on Putty's cache.
We can see that after login in, we arrive to the same session as if we were using the console. As you can imagine this is great, since we can copy/paste commands, an option that is not available with th console.
The log file, we discused earlier shows the same information as the SSH Window.
No comments:
Post a Comment