CCNA v2.0, section 4.0, lab 1, in slides: give R1 an enable secret, a local user and SSH only in Packet Tracer; turn on SRV1's AAA service and check R1's logins over TACACS+ and R2's over RADIUS, with the local users as the fallback; copy the configurations to SRV1 over TFTP and FTP; on your own computer, copy a configuration over SCP and SFTP to a Linux container and capture the copy; then break the logins in five ways (a wrong key, the server off, Telnet only, no domain name, the local users first) and find each one.
The slides
The lab is twenty-two slides in six parts, after an introduction, one step each.
- Introduction: what the lab does, and what it needs.
- 1. Local users and SSH on R1: Telnet refused, the enable secret against the enable password, SSH turned on, and a login as
admin. - 2. AAA with TACACS+ on R1: SRV1's AAA service, R1's TACACS+ server and method list, and a login with each password.
- 3. RADIUS on R2: SSH on R2, and its logins checked by SRV1 over RADIUS.
- 4. Configuration files: R1's configuration copied to SRV1 over TFTP, R2's over FTP, and the network saved.
- 5. SCP and SFTP on your computer: an SSH server in a container, a copy with
scp and sftp, a capture of the copy, and SCP read on a real router. - 6. Breaking the logins: a wrong TACACS+ key, SRV1's AAA service off, Telnet only, no domain name, and the local users first.
The files
- The network it starts from:
lab3-4.pkt, saved in
Lab 3.4, at the end of section 3.0; only its HQ LAN is used. - The network it saves:
lab4-1.pkt. - The configurations it builds: each device's configuration, as plain text, in the
ccna repository.
- What Packet Tracer lacks: an SCP server, so part 5 runs on your own computer, with Docker, and reads a real router's SCP output.
- The lesson:
Device Access: Users, AAA and Files.