Changes between Version 29 and Version 30 of ipv6v4config

Timestamp:

May 18, 2017, 7:05:08 AM (8 years ago)

Author:

admin

Comment:

--

ipv6v4config

@@ -134 +134 @@
 
 '''Note''' : Hostname is different in each device
+
+=== Recover from a forgotten password ===
+This is one of our favorite situations. In some cases one student might change a password on a device and then not be in class after they have done this. Or, a student does not use the suggested class password and forgets what they typed. Or, a student makes a typo while configuring a device's password and save the configuration and exits from the console.
+
+This recovery method simulates what you would do on an actual Cisco router with a console cable were this to happen.
+
+First go to dynagen and type:
+{{{
+=> confreg <DEVICE NAME> 0x2142
+}}}
+0x2142 is the default register on cisco devices to tell the router to ignore the saved config, but not lose the configuration.
+
+Next connect to your device via the console. That is telnet to localhost on the correct port for the device. 
+{{{
+telnet localhost <PORT OF THE DEVICE>
+}}}
+You will see something like this. Press ENTER as requested:
+{{{
+Would you like to enter the initial configuration dialog? [yes/no]:
+}}}
+Answer '''no''' to the above question and you will see a bunch of informational text. Press ENTER one more time and you will arrive to the device prompt:
+{{{
+Router>
+}}}
+Now go in to administrative mode with enable
+{{{
+Router> en
+}}}
+If you do:
+{{{
+Router# show run
+}}}
+Now you can set your enable password (Or you can add any config). An example of this would look like:
+{{{
+Router# conf t
+Router(config)#service password-en
+Router(config)#service password-encryption
+Routerconfig)#enable secret <CLASS PASSWORD>
+Router(config)#exit
+Router#wr mem
+}}}
+Now exit from the Telnet session:
+{{{
+ctrl-]
+telnet> quit
+}}}
+Now return to the dynagen prompt and do:
+{{{
+=> confreg <DEVICE NAME>0x2102
+=> reload DEVICE NAME>
+}}}
+And test that your new user and password are working as expected using telnet again to the correct port on localhost or telnet directly to the router's IP address if one has been set.
+
+If ssh access had been configured you may need to reconfigure that as well at this point.
 
 === Network Configurations ===
@@ -708 +762 @@
  - type '''wireshark''' and press enter
  - On the wireshark interface select the '''enp0s3''' interface and click '''Capture packets''' button
- - You will see plenty of broadcast packets
+ - You will see plenty of broadcast packets. They will look like following
+{{{
+NO      Time            Source                  Destination     Protocol        Length  Info
+9       0.579325000     00:fe:c9:3e:13:a0       Broadcast       ARP             60      Who has x.x.x.x?  Tell y.y.y.y
+}}}