Opengear - How to change user/root password from CLI. [SOLVED]

Here is a real example - I got a SSH access to my remote terminal concentrator and wanted to change password for root user from CLI. It is possible to do according to the official recommendation, this method you can use for root or any other user.

Check the FW version (the latest one):

# cat /etc/version
OpenGear/CM41xx Version 3.15.2 0de50f6e --  Thu Apr 30 14:17:14 EST 2015
#

Get the current user configuration (there was only root user configured):

#  /bin/config --get=config.users
config.users.total 1
config.users.user1.description Root User
config.users.user1.groups.total 6
config.users.user1.password_nvflash on
config.users.user1.username root
#

Then change the password for the username root (user1) then run the configurator:

# /bin/config -s config.users.user1.plaintext_password=NEWPASSWORD
# /bin/config -r users

Done.

From Huawei to HP… [REPOST]

Original port can be found here (Posted on May 12, 2010 by tnk).

This post will be slightly atypical for this blog, but I think it is rather important to sum up what happened in last approximately three years. I’ll try summarize some history behind the Huawei/H3C/3Com/HP products. The reason for this “history” lesson is that quite a lot of people is confused of what was/is/will be and that is mostly thanks to communication from biased sales representatives and some strange articles that could be found on the Internet. So without further delays – let’s get to the history.

• 2003 – H3C Joint Venture

A this date emerging Chinese company (outside China mostly known just for its copyright war with Cisco systems) created a joint venture with and declining US company 3Com. This enterprise has a lucky beginnings – 3Com’s name was still widely known (even though the company didn’t have a new product in ages at this point) and the $160M was a great contribution to the starting point. Huawei provided R&D, human resources and an entry point to the massive and ever hungry Chinese market. This joint venture was named H3C. There was one important glitch in the agreement though – 3com will have the option to buy majority in H3C after two years.

• 2006 – From Huawei to 3Com

After some negotiations the controlling 2% share in the company was bought by 3Com for $28M and later also the rest of the shares owned by Huawei were bought. And that is how 3Com became the only owner of H3C company. The sell of the remaining shares was approved on November 29, 2006. In an attempt to keep at least some control in the company Huawei tried to buy 16% share in 3Com itself. This was stopped by US authorities as they were afraid of the possibility that some strategically important data might be revealed as 3Com equipment was used by Pentagon.

After this attempt it became obvious that the relationships between Huawei and H3C will decline (even though Huawei was still the biggest customer of H3c with over 50% share). So that is the time when VRP stopped to be VRP on H3C and became Commware and that is also the time of the launch of the “metro” switching platform (also known as PTN in Huawei Optix line). To be exact last “Huawei” VRP is VRP4.x all marked as VRP5.x is Commware. This is beginning of significant technological difference (not that there wouldn’t be any differences before – there were but rather minor in both HW so as SW) between Huawei and 3Com/H3C products.

• 2008 – 2010 from 3Com to HP

The H3C company helped 3Com to return into the high-end segment but also left the company without much needed cash which gradually led to talks about buyout from somebody else (in 2009 it was sure that that “somebody” will be HP). At this point Huawei started with replacement of all H3C low-end and mid-end datacom devices in its portfolio and thus returned at least two years back in development. The other thing that happened is that HP moved the unfortunate Procurve line where it belonged long time ago (via “merging the portfolios”).

Well you might ask why I wrote this article (even though I already described the reasons at the beginning). I think it is necessary to clear out all the sales crap-talk about “continuity”, “compatibility” etc. So basically what has happened is:

Huawei has new (low-end and mid-end) datacom lines are totally separately developed and have nothing in common with their previous equipment (even though the CLI looks similar on some devices).

HP integrated the H3C/3Com portfolios and is leaving the Procurve line behind. Which means (at least from the looks of it) that there will be continuity of the H3C products but there seems to be no further development of the “ProCurve” line planned.

Well I hope this was informative and I promise that next time I will post something more interesting – preferably some config tutorial of some sort :)

FireFox - “Error code: ssl_error_no_cypher_overlap”. [SOLVED]

• Open a new tab in Firefox and type “about:config” in the URL bar.
• You’ll get the following warning message “This might void your warranty!”, just skip it by pressing “I’ll be careful, I promise!” button.
• Copy/paste the following to the search field:

/^security.tls.version.min|security.tls.version.fallback-limit/

• You’ll get two options that need to be changed from 1 to 0. Double click on each, change to 0, then restart FireFox. Opening the second instance of FireFox while having previous one opened will NOT work.
• Enjoy!

LibreNMS / Observium.

Few month ago I was needed to install Observium on CentOS 7. This product has interesting history and it’s under developing since 2006.

Today I’ve read a blog note written by Paul Gear about why he did create a fork the final GPL licensed release of Observium from March 2012 to create LibreNMS. The note called Observium and GPL misconceptions.

What I can say is it’s inspiring to do a good things, I think Paul is doing right thing. Since now I will use LibreNMS instead of Observium. Here you can find a starting point how to start contribution quickly.

Admin area