Archiv der Kategorie: Random

Random stuff which i discovered or found in inet.0.

Reserved for documentation use

Sometimes you have document a network behavior and need example prefixes or AS numbers. Here is a list of some documents and reserved values, which could be useful for this:

  • MAC unicast address (see RFC7042): 00:00:5E:00:53:00 to 00:00:5E:00:53:FF
  • MAC multicast address (see RFC7042): 01:00:5E:90:10:00 to 01:00:5E:90:10:FF
  • IPv4 unicast prefix (see RFC5737)-, and
  • IPv4 multicast prefix (see RFC6676)-
  • IPv6 unicast prefix (see RFC3849)- 2001:DB8::/32
  • IPv6 multicast prefix (see RFC6676)- FF0<any hex value>::DB8:0:0/96
  • AS numbers 16-bit (see RFC5398) – 64496 – 64511
  • AS numbers 32-bit (see RFC5398) – 65536 – 65551
  • Top-Level Domain (see BCP32) – .example


  • Alice and Bob, alternatives for ‚Person A’/’Person B‘ when describing processes in telecommunications; in cryptography Eve (the eavesdropper) is also added.(see Wikipedia)

Huawei Switches – Software Update

This post is not related to Juniper stuff, but nice to know if you work with Huawei switches…

I’ve worked with the S2300 series last year and learned a lot about the „Huawei Versatile Routing Platform Software“ or VRP.  From my point of view the cli felt not very comfortable.  For example: most of the time where I used the tab-completion it fails, because the cli suggested the complete(!) first command instead of only suggest the next characters to the next closest matching word – like Juniper or Cisco cli does 😉 If you are fast in typing this could be very frustating.  However the cli could be very smart, because it doesn’t let you remove a option or command, which is currently in use by another command. This prevent you of wrong configurations.

I also did some software updates on these decives and I would share the procedure with you.:

1) remove old patches

patch delete all

2) take a look at your flash disk and remove old *.cc files

delete /unreserved <name of old .cc file>

3) get your new .cc file, for e.g. via FTP

ftp <ip>
get <name of new .cc file>

4) apply new software image for next startup

startup system-software <name of new .cc file>

5) verify correct startup settings

display startup

6) fire and forget 😉


… and hopefully your switch will now come up with the new software image.

Tunneling HTTP/DNS through SSH – Part 2 – Windows

As a follow-up to my previous post (Tunneling HTTP/DNS through SSH) I will show you how can create a SOCKS proxy with Putty for Windows.

1. You must create a session, enter your hostname or IP address with port and give it a name like „forwarding“:

Create a Profile / Session
Create a Profile / Session

2.  To speed up your tunnel establishment you can enable auto-login for your username, e.g. „root“. This only eliminate username prompt and you must always enter your password.

Enable Auto-Login
Enable Auto-Login

3. Enable compression for your tunnel 😉

Enable compression
Enable compression

4. Then you must add your local source port „D8080“ for Port 8080.

Set local port
Set local port

5. Save your session again and open it!

Save your Session
Save your Session

6. After you entered your password you should see an open port on your host (german windows edition):

Check your local port
Check your local port

7. Thats it!  Now you can change your SOCKS proxy settings to locahost:8080, as described in my previous post.

Howto recover your root password in JunOS (MX-Series works!)

Here is Howto about the recovering procedure of a lost root password in JunOS. You need to reboot!

  1. Power off the router by pressing the power button on the front panel.
  2. Turn off the power to the management device, such as a PC or laptop computer, that you want to use to access the CLI.
  3. Plug one end of the Ethernet rollover cable supplied with the router into the RJ-45–to–DB-9 serial port adapter supplied with the router.
  4. Plug the RJ-45–to–DB-9 serial port adapter into the serial port on the management device.
  5. Connect the other end of the Ethernet rollover cable to the console port on the router.
  6. Turn on the power to the management device.
  7. On the management device, start your asynchronous terminal emulation application (such as Microsoft Windows Hyperterminal) and select the appropriate COM port to use (for example, COM1).
  8. Configure the port settings as follows:
    commit complete
    • Bits per second: 9600
    • Data bits: 8
    • Parity: None
    • Stop bits: 1
    • Flow control: None
  9. Power on the router by pressing the power button on the front panel. Verify that the POWER LED on the front panel turns green.The terminal emulation screen on your management device displays the router’s boot sequence.
  10. When the following prompt appears, press the Spacebar to access the router’s bootstrap loader command prompt:
    Hit [Enter] to boot immediately, or space bar for command prompt.
    Booting [kernel] in 9 seconds...
  11. At the following prompt, enter boot -s to start up the system in single-user mode.
    ok boot -s
  12. At the following prompt, enter recovery to start the root password recovery procedure.
    Enter full pathname of shell or 'recovery' for root password recovery or RETURN for /bin/sh: recovery
  13. Enter configuration mode in the CLI.
  14. Set the root password. For example:
    user@host# set system root-authentication plain-text-password
  15. At the following prompt, enter the new root password. For example:
    New password: juniper1
    Retype new password:
  16. At the second prompt, reenter the new root password.
  17. After you have finished configuring the password, commit the configuration.
    root@host# commit
    commit complete
  18. Exit configuration mode in the CLI.
  19. Exit operational mode in the CLI.
  20. At the prompt, enter y to reboot the router.
    Reboot the system? [y/n] y

Mostly copied from here.