Part Two - Networking

Add a new network interface to server2. 1. As userp1s2 with sudo, run ip a and verify the presence of the new interface (e.g., enp0s8).

2. Use the nmcli command and assign IP x.x.x.212/24 and gateway x.x.x.1. a. Identify the network octets (x's) using preparation steps.

3. Set the network connection to auto-activate on system reboots.

Add a new network interface to server3. 1. As userp1s3 with sudo, run ip a and verify the presence of the new interface (e.g., enp0s8).

2. Use the nmcli command and assign IP x.x.x.213/24 and gateway x.x.x.1. a. Identify the network octets (x's) using preparation steps.

3. Set the network connection to auto-activate on system reboots.

Part Three - Security through SSH

1. As root on server2, generate a private/public key pair without a passphrase using the sshkeygen command.

2. Distribute the public key to server3 with the ssh-copy-id command.

3. Use SSH (ssh server3 or server3's IP address) to log on to server3 and accept the fingerprints for the server if presented.

4. On subsequent log in attempts from server2 to server3, you should not be prompted for a password. If you are prompted or encounter an error, include that in your work product submission.

5. As root with sudo on server3, edit the /etc/ssh/sshd_config file and change the value of the directive PermitRootLogin to "no".

6. Use the systemctl command to activate the change.

7. As root on server2, run ssh server3 (or its IP address). a. Note: It is expected that you'll get permission denied message.

8. Reverse the change on server3 and retry ssh server3.

a. Note: It is expected that you should be able to log in again.