Netonix Forums

Hello all,

We have found a peculiar issue with our Netonix WS-12-250A switches running firmware v1.2.0, regarding the changing of username credentials and being able to login to the CLI with the new username via SSH.

Both the web interface and the CLI allow you to change the username and password credentials independently – or so it appears!
If only the password alone is changed from either the web interface or the CLI, the password change is effected and you can login to either interface with the current username and new password - good.

However, if only the username alone is changed from either the web interface or the CLI, the username change is only effected via the web interface. The web interface allows login with the new username and existing password.

Attempting to login to the CLI with the new username and existing password will fail and result in 'access denied' (via SSH). The CLI will only accept a login with the previous username and existing password.

Thus the only way to ensure access consistency between the web interface and CLI is whenever making any changes to the username via the web interface or CLI, is for both credentials to be entered, that is the password, which is to remain the same, has to be re-entered.

In most cases, I guess this issue wouldn't be encountered as the username would be fairly static, its more likely that a change in password would occur after initial config, however, it appears in our initial configuration of the switches, there was a change required to correct the username before they went out to site and we found that there was a difference between access with the correct credentials via the web interface and CLI which we investigated and replicated with our lab Netonix switch.

After searching the forums, I couldn not find a post with this issue nor it being resolved in one of the more recent firmware releases so just highlighting here for information and consideration for a fix.

Many Thanks,

Professor_K

I believe that was fixed along time ago.

We only address bug reports on the current firmware version.

Please upgrade to the current firmware and see if the bug is still there. If you find it there we will get right on it and make sure the fix is in v1.3.5 which is do out SOON.

Hi sirhc,

Is it possible to downgrade the firmware back to v1.2.0 after upgrading it v1.3.3? We have not yet embarked on our regression testing plans for v1.3.3 and indeed will probably wait till v1.3.5 if it is imminent, so as v1.2.0 is our current baseline, I'd like to be able to downgrade our lab switch back to v1.2.0 after quickly verfiying whether the issue is fixed in v1.3.3 or not and feed back ?

Thanks very much,

Hello,

I "believe" the AC units can be downgraded all the way back to v1.1.8 at least but the DC versions because support was not complete in older firmware or serious bugs were found their downgrade paths are limited.

I am not sure why you want to run outdated firmware that has many known and fixed bugs?

Thanks,
Chris

Hi Chris,

Have upgraded and tested with v1.3.3 and unfortunately the issue is still present, is it possible to get the fix into v1.3.5?

To answer your question on why we are not using most recent firmware, our release process specifies that we must thoroughly regression test a device firmware update against our setup, which takes time and since v1.2.0 we haven't noticed any firmware updates that significantly improve upon the stability and function or has necessitated an upgrade until v1.3.3 which has some interesting features. Now that you say v1.3.5 is on the horizon, we may just plump for that.

Is there any detail on the feature set/fixes for v1.3.5 available now or will we need to wait for the release thread?

Thanks again,

Since you have reported the bug exists in v1.3.3 we are investigating it.

Confirmed, this will be fixed in 1.3.5.

Thankyou Chris and Eric for your support