Case Study User Accounts User SSH

densmadensma Member Posts: 40 ■■□□□□□□□□
I have question on the JNCIP initial chap case study / user acct section.

Table 1.2: Case Study User Accounts User/Password
Permissions
Notes

lab
superuser
Telnet, SSH version 2 only with password, and console

root
superuser
Console only

noc
View only
Telnet, SSH version 2 only with password, and console


how do you test or verify that user noc and lab can ssh in?
i tried from R1 to R2 and all i got is prompted for (root) password only not user name.
i can only ssh in with root acct. root password will work if i issue under system "delete services ssh root-login deny"

does thet provided solution meet this requirement? anyone notice that noc and lab user cant ssh in?

[email protected]# run ssh 10.0.6.2
The authenticity of host '10.0.6.2 (10.0.6.2)' can't be established.
RSA key fingerprint is c1:28:60:f6:d7:87:13:4f:bb:71:a2:15:0f:aa:20:fb.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '10.0.6.2' (RSA) to the list of known hosts.
[email protected]'s password:
Permission denied, please try again.
[email protected]'s password:

Comments

  • brocbroc Member Posts: 167
    Did you try ssh -l <username> <ip address>?
    "Not everything that counts can be counted, and not everything that can be counted counts.”
  • densmadensma Member Posts: 40 ■■□□□□□□□□
    [email protected]# run ssh -l ?
    Possible completions:
    <[Enter]> Execute this command
    bypass-routing Bypass routing table, use specified interface
    inet Force ssh to IPv4 destination
    inet6 Force ssh to IPv6 destination
    interface Name of interface for outgoing traffic
    logical-router Name of logical router
    routing-instance Name of routing instance for ssh session
    source Source address for ssh session
    v1 Force ssh to try protocol version 1 only
    v2 Force ssh to try protocol version 2 only
    | Pipe through a command
    [edit]
    [email protected]# run ssh -l lab?
    No valid completions
    [edit]
    [email protected]# run ssh -l lab
Sign In or Register to comment.