Skip to main content

Enabling SSH on a Cisco Router for Secure Remote Login

  1. Ensure you have a hostname configured on your router:
    Router#conf t 
  2. Router(config)#hostname router23
  3. You must also configure a domain name:
    Router(config)#ip domain-name jpt
  4. Generate an RSA keypair with a key length of 1024 bits using the following sequence of commands:
    router(config)#
    router(config)#crypto key generate rsa
  5. The name for the keys will be: routername.soundtraining.class (where routername is your router's hostname)
  6. Choose the size of the key modulus in the range of 360 to 2048 for your
      General Purpose Keys. Choosing a key modulus greater than 512 may take a few minutes.
  7. How many bits in the modulus [512]: 1024% Generating 1024 bit RSA keys ...[OK]
  8. Create a username in the router’s local database for SSH authentication using the following command (for the purpose of the exercise, use the username “user15”):
    router01(config)#username user15 privilege 15 secret p@ssword
  9. Enable login authentication against the local database when logging in to a terminal line with the following commands:
    router01(config)#line vty 0 15
  10. router01(config-line)#login local
  11. router01(config-line)#exec-timeout 0 0
  12. router01(config-line)#logging synchronous
  13.  router01(config-line)#transport input ssh

Comments

Post a Comment

Popular posts from this blog

Cisco SG300 CLI Commands

Cisco SG300 CLI Commands Other parts were obtained using the CLI PDF provided by Cisco Remove a Trunk and switch to access config t int gi44 switchport trunk allowed vlan remove 2 switchport mode access switchport access vlan 2 or config t int gi44 switchport mode general switchport general allowed vlan remove 2 switchport mode access switchport access vlan 2 Change CDP Device ID Format to Hostname opposed to default MAC address s-sg300#sh cdp Global CDP information:         CDP is globally enabled         CDP log duplex mismatch is globally enabled         CDP log voice VLAN mismatch is globally enabled         CDP log native VLAN mismatch is globally enabled         Mandatory TLVs validation is disabled         Sending CDPv2 advertisements is enabled         Sending Appliance TLV is enabled       ...
Post a Comment
Read more

Policy Based Routing on a Cisco ASA

Cisco ASA 9.4 (and later) is now supporting Policy Based Routing. Yeah. Great news, since many customers are requesting something like “HTTP traffic to the left – VoIP traffic to the right”. Coming with a new Cisco ASA 5506-X I was happy to try the policy based routing feature. The configuration steps through the ASDM GUI are not easy and full of errors so I am trying to give some hints within this blog post. The main document from Cisco for policy based routing on a ASA is here . It describes the use-cases for PBR and gives examples. Configuration I am doing all of my configurations through the GUI ASDM. (I know, some people really love the CLI even for configurations, but I don’t. I am using it only for troubleshooting issues.) For this lab I am using a Cisco ASA 5506-X with ASA version 9.5(1), while ASDM is version 7.5(1) . In my lab, I have a default route to ISP 1 (gi1/1) and a different connection to ISP 2 (gi1/2). There is no route to ISP 2 in the ro...
Post a Comment
Read more

Patch Workflows

Thus far, all of the collaboration workflows we’ve seen rely heavily on branches. For example, in the last module, a contributor had to publish an entire branch for us to merge into our project. However, it’s also possible to communicate directly on the commit level using a patch . A patch file represents a single set of changes (i.e., a commit) that can be applied to any branch, in any order. In this sense, the patch workflow is akin to interactive rebasing, except you can easily share patches with other developers. This kind of communication lessens the importance of a project’s branch structure and gives complete control to the project maintainer (at least with regards to incorporating contributions). Integrating on the commit level will also give us a deeper understanding of how a Git repository records project history. Download the repositories for this module If you’ve been following along from the previous module, you already have everything you need. Otherwise, d...
Post a Comment
Read more