Lab Accessing Network Devices With SSHTopologyAddressing
Lab - Accessing Network Devices with SSH
Topology
Addressing Table
Device
Interface
IP Address
Subnet Mask
Default Gateway
R1
G0/1
192.168.1.1
255.255.255.0
N/A
S1
VLAN 1
192.168.1.11
255.255.255.0
192.168.1.1
PC-A
NIC
192.168.1.3
255.255.255.0
192.168.1.1
Objectives
Part 1: Configure Basic Device Settings
Part 2: Configure the Router for SSH Access
Part 3: Examine a Telnet Session with Wireshark
Part 4: Examine a SSH Session with Wireshark
Part 5: Configure the Switch for SSH Access
Part 6: SSH from the CLI on the Switch
Background / Scenario
In the past, Telnet was the most common network protocol used to remotely configure network devices.
However, protocols such as Telnet do not authenticate or encrypt the information between the client and server. This allows a network sniffer to intercept passwords and configuration information.
Secure Shell (SSH) is a network protocol that establishes a secure terminal emulation connection to a router or other networking device. SSH encrypts all information that passes over the network link and provides authentication of the remote computer. SSH is rapidly replacing Telnet as the remote login tool of choice for network professionals. SSH is most often used to log in to a remote device and execute commands; however, it can also transfer files using the associated Secure FTP (SFTP) or Secure Copy (SCP) protocols.
For SSH to function, the network devices communicating must be configured to support it. In this lab, you will enable the SSH server on a router and then connect to that router using a PC with an SSH client installed. On a local network, the connection is normally made using Ethernet and IP.
In this lab, you will configure a router to accept SSH connectivity, and use Wireshark to capture and view
Telnet and SSH sessions. This will demonstrate the importance of encryption with SSH. You will also be challenged to configure a switch for SSH connectivity on your own.
Note: The routers used with CCNA
Topology
Addressing Table
Device
Interface
IP Address
Subnet Mask
Default Gateway
R1
G0/1
192.168.1.1
255.255.255.0
N/A
S1
VLAN 1
192.168.1.11
255.255.255.0
192.168.1.1
PC-A
NIC
192.168.1.3
255.255.255.0
192.168.1.1
Objectives
Part 1: Configure Basic Device Settings
Part 2: Configure the Router for SSH Access
Part 3: Examine a Telnet Session with Wireshark
Part 4: Examine a SSH Session with Wireshark
Part 5: Configure the Switch for SSH Access
Part 6: SSH from the CLI on the Switch
Background / Scenario
In the past, Telnet was the most common network protocol used to remotely configure network devices.
However, protocols such as Telnet do not authenticate or encrypt the information between the client and server. This allows a network sniffer to intercept passwords and configuration information.
Secure Shell (SSH) is a network protocol that establishes a secure terminal emulation connection to a router or other networking device. SSH encrypts all information that passes over the network link and provides authentication of the remote computer. SSH is rapidly replacing Telnet as the remote login tool of choice for network professionals. SSH is most often used to log in to a remote device and execute commands; however, it can also transfer files using the associated Secure FTP (SFTP) or Secure Copy (SCP) protocols.
For SSH to function, the network devices communicating must be configured to support it. In this lab, you will enable the SSH server on a router and then connect to that router using a PC with an SSH client installed. On a local network, the connection is normally made using Ethernet and IP.
In this lab, you will configure a router to accept SSH connectivity, and use Wireshark to capture and view
Telnet and SSH sessions. This will demonstrate the importance of encryption with SSH. You will also be challenged to configure a switch for SSH connectivity on your own.
Note: The routers used with CCNA