v1.5.25 Bug Reports and Comments

[Dawizman]

At first I thought I was crazy and thought I changed a switch password, but actually didn't after the upgrade. But now I am not so sure.

I seem to be having random reversion to the default admin password.

I have had this happen several times now, when I change a switch password post upgrade to 1.5.25. Some time later I go to login, and get incorrect password. I login with admin/admin, and it works. I then update the password, and it takes. Although I am sure I have had to do this more than once on the same switch now.

A follow up on this. I am having this occur on virtually every single switch I update to 1.5.25.

I update the software, change the password after first login. Some time later I try to access the switch, and the gui password has reverted to admin.

But, here's the thing, the ssh password is still the password I set after the first login post update.

I have one switch in this state at the moment that I will hold off on fixing the password again. Is there anything off the switch I can get for Stephen to better diagnose this issue? It seems very severe that all my switched could be sitting there with a default password for ui access.

[RTGLW]

At first I thought I was crazy and thought I changed a switch password, but actually didn't after the upgrade. But now I am not so sure.

I seem to be having random reversion to the default admin password.

I have had this happen several times now, when I change a switch password post upgrade to 1.5.25. Some time later I go to login, and get incorrect password. I login with admin/admin, and it works. I then update the password, and it takes. Although I am sure I have had to do this more than once on the same switch now.

A follow up on this. I am having this occur on virtually every single switch I update to 1.5.25.

I update the software, change the password after first login. Some time later I try to access the switch, and the gui password has reverted to admin.

But, here's the thing, the ssh password is still the password I set after the first login post update.

I have one switch in this state at the moment that I will hold off on fixing the password again. Is there anything off the switch I can get for Stephen to better diagnose this issue? It seems very severe that all my switched could be sitting there with a default password for ui access.

I have now also run into this with one of the first switches we upgraded (back on Jan 23rd). The GUI will no longer accept the password we set after upgrading to 1.5.25, only "admin". When using a password via SSH, it's accepting both "admin" and the password we set after the firmware upgrade. @Dawizman is this the same for you?

This is the first instance of this issue I've encountered, but we are still doing a slow roll out (for this exact reason).

FWIW, and completely anecdotal, we wouldn't have logged into this switch since when we upgraded it, where as our other initial switches put on 1.5.25 get logged into on a more frequent basis. I am going to leave it as is, so if anything useful for troubleshooting could be pulled from it let us know. Will see if any others show this problem in the coming weeks.

[Dawizman]

At first I thought I was crazy and thought I changed a switch password, but actually didn't after the upgrade. But now I am not so sure.

I seem to be having random reversion to the default admin password.

I have had this happen several times now, when I change a switch password post upgrade to 1.5.25. Some time later I go to login, and get incorrect password. I login with admin/admin, and it works. I then update the password, and it takes. Although I am sure I have had to do this more than once on the same switch now.

A follow up on this. I am having this occur on virtually every single switch I update to 1.5.25.

I update the software, change the password after first login. Some time later I try to access the switch, and the gui password has reverted to admin.

But, here's the thing, the ssh password is still the password I set after the first login post update.

I have one switch in this state at the moment that I will hold off on fixing the password again. Is there anything off the switch I can get for Stephen to better diagnose this issue? It seems very severe that all my switched could be sitting there with a default password for ui access.

I have now also run into this with one of the first switches we upgraded (back on Jan 23rd). The GUI will no longer accept the password we set after upgrading to 1.5.25, only "admin". When using a password via SSH, it's accepting both "admin" and the password we set after the firmware upgrade. @Dawizman is this the same for you?

This is the first instance of this issue I've encountered, but we are still doing a slow roll out (for this exact reason).

FWIW, and completely anecdotal, we wouldn't have logged into this switch since when we upgraded it, where as our other initial switches put on 1.5.25 get logged into on a more frequent basis. I am going to leave it as is, so if anything useful for troubleshooting could be pulled from it let us know. Will see if any others show this problem in the coming weeks.

I can confirm, ssh will accept admin, or my configured password.

[sakita]

So far I haven't seen any passwords revert. However, the few switches I've deployed 1.5.25 on have not been running it very long.

Unless I missed it, the ones mentioned above had been running it since January. Do any of you have other switches that maybe have been running it for less time that have reverted?

I'll keep checking on the ones I have to see if any revert...

[Dawizman]

I've had several revert by the next day. The first time I thought I forgot to update. Second time thought I was losing it. Then I started looking back through logs every time it happened, and sure enough I had updated credentials every time, and they reverted.

[CrackerRiley]

This is my first attempt at radius auth with Netonix, so far I am striking out. Response in ssh is Access Denied, I added the line to my clients.conf file and I also enabled require_message_authenticator for my global rule as well. I guess where I am lacking the experience/knowledge on this is what kind of reply should radius be sending?


Freeradius 3.0
# allowed values: yes, no
require_message_authenticator = yes
client private-network-1 {
### I also tried just the ip of the switch rather than a range yyy.yyy.yyy/32
ipaddr = 10.0.0.0/8
secret = somethingsecret
require_message_authenticator = yes


Currently I have a user in my database- (not real info here)
Check Attributes
user User1
Cleartext-Password := User1234

Reply Attributes
Auth-Type := Accept

## I also tried with a GROUP reply with Auth-type := Accept

I have the switch ip in my NAS as well with correct secret, radius port is also default and correct 1812

Netonix v 1.5.25
"RADIUS_Enable":true,
"RADIUS_Host":"xxx.xxx.xxx.xxx",
"RADIUS_Port":"1812",
"RADIUS_Secret":"somethingsecret",
My tiks all auth just fine, granted they use a different reply though such as FULL or READ

When I run radclient from the Netonix-
admin@T222:/etc/freeradius2# echo "User-Name = validuser,User-Password=validpass" | radclient xxx.xxx.xxx.xxx auth somethingsecret
Received response ID 144, code 2, length = 20

This is not really where you should post this as Free Radius has been proven to work so not a bug,. and you state this is your first attempt at using so guessing its something in your configuration or setup.

I would like to help you, but I don't use Radius Auth and testing was done by Stephen on this.

Stephen may catch this and help and or another user using Radius but if it's not a bug should find a similar thread on radius with search function or even start a new thread. If you read this thread you can determine that it does work if configured correctly so not a bug.

We have confirmed there is a bug with freeRadius auth with 1.5.25. I posted about it a page back in this thread. Patiently waiting for fix myself...

Looks like radius authentication isn't working for me on 1.5.25. Worked on a switch with 1.5.14, upgraded it to 1.5.25 and it stopped working. Just says "Invalid username or password"

freeRadius server doesn't throw any errors when running debugger.

Can anyone else confirm it works for them or is broken for them.

Based on answers I may pull Stephen to fix it.

Confirmed BROKEN.

Switch with 1.5.17rc1 and RADIUS config (also FreeRADIUS). Logged in with my RADIUS credentials to verify working.

Rebooted switch first (had been up for a long time) then updated it to 1.5.25. Logged back in and reset admin password.

Logged out and tried my RADIUS password... "Invalid username or password." Can still login with local admin (thankfully).

Also note that the log no longer shows user login events. The previous version was showing both admin and my user name logins when I tested it. 1.5.25 does not.

[sirhc]

How are people setting the password?

You either use the UI or CLI (Netonix CLI) NOT the Linux cmd line. DO NOT DROP TO LINUX SHELL AND SET PASSWORD.

All of my switches have been running since v1.5.25 was released and all login correctly via UI and SSH.

DO NO CHANGE OR SET PASSWORD AT LINUX AS THIS WILL NOT GET UPDATED TO SWITCH CONFIG.

Anything done at Linux shell is not transferred to our config.

If you SSH into the switch press "?" [Enter]

Credentials
Credentials user "what you want user to be"
Credentials password "what you want password to be"

Now you MUST press [ENTER] after the command once or twice and you get a message config validated or accepted. If you don't press [ENTER] after command it will revert back after period set, default i think is 6 minutes.

[sirhc]

I know this works as I have many in service and login to them almost daily.

I even changed the passwords several weeks ago as I got rid of an employee.

Again I don't see this but did see a post earlier where a user detailed how he updated switch. SSH in, typed "cmd" then changed the password. This will not work. It may change it for a short while but will eventually revert to what's in our config and anything done in Linux shell level is NOT updated to our config.

[Dawizman]

I set the password in the web ui after the upgrade. I'm relatively certain I can reproduce this if you have a means to collect data during my process. I am at a 50% rate of this happening after a 1.5.25 update.

I am updating from 1.5.14 for the most part, as there were way too many issues in between. Not sure what your update path has been Chris.

[sirhc]

I upgraded most from v1.5.14 or v1.5.16 as I only upgraded a few as we were driving through those rapid changes.