v1.5.25 Bug Reports and Comments

[shahan]

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.

Upgraded to 1.5.25. Some of the switches do not have the reconfirm password option in the GUI.
I can successfully SSH into the device and enter configure mode.
When trying to set the credentials by typing credentials - enter. It spits back an invalid command. I have tried all the variations of credentials that I can think of and even tried the ? to make sure everything was spelled correctly. Is there a fix for this?
I also tried a few other commands to see if "credentials" was the only having issues, but most of the other ones are outputting the same invalid command. Any help would be appreciated.

[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.

Upgraded to 1.5.25. Some of the switches do not have the reconfirm password option in the GUI.
I can successfully SSH into the device and enter configure mode.
When trying to set the credentials by typing credentials - enter. It spits back an invalid command. I have tried all the variations of credentials that I can think of and even tried the ? to make sure everything was spelled correctly. Is there a fix for this?
I also tried a few other commands to see if "credentials" was the only having issues, but most of the other ones are outputting the same invalid command. Any help would be appreciated.

login via SSH
type "config t" [Enter]
type "credentials user "what you want user to be" [Enter]
type Credentials password "what you want password to be" [Enter]
press [Enter] again to confirm or revert in a few minutes

That's what you do, always worked for me. Considering 10s of thousands of users upgraded with no issues and only a few have issues this would indicate either user error or possibly a corrupted configuration file???

If above don't work then factory default unit and set back up manually.

[Dawizman]

Why are you so negative towards people reporting bugs to you?

I have a reproducible bug, and "must be user error".

I setup a brand new switch yesterday. Right out of the box from Netonix. Loaded 1.5.25 on it immediately. Reset to factory defaults. Configured the switch including setting an admin password.

Logged in to it today. "Invalid username or password ".

My configured password works on ssh, as well as admin/admin. admin/admin works on web ui.

Clearly this is an issue.

[sakita]

This password revert seems like one of those annoying things that only affects some people and doesn't affect others making it difficult to figure out what is happening to those it does affect.

I have not seen any revert. I do sometimes (not always?) log back into a device immediately after I change the password (to make sure I didn't mess up and not leave myself a surprise for later). Maybe that is guaranteeing it doesn't revert for me? Then again, others may not do that and don't get affected.

I read back through the last few pages of this thread and don't recall which browser(s) were being used or if anyone has done a cache flush on their browser? It's the "turn it off / back on" of browser operation but does help sometimes. Currently I'm using Chrome 135.0.7049.97 (64-bit) on Windows 10.

[sirhc]

Why are you so negative towards people reporting bugs to you?

I have a reproducible bug, and "must be user error".

I setup a brand new switch yesterday. Right out of the box from Netonix. Loaded 1.5.25 on it immediately. Reset to factory defaults. Configured the switch including setting an admin password.

Logged in to it today. "Invalid username or password ".

My configured password works on ssh, as well as admin/admin. admin/admin works on web ui.

Clearly this is an issue.

Not being negative
Stating only a few report this.
You say replicateable but I can not.

Do I think your seeing something odd that most do not, YES.

The question is WHY.

There are so many OS's, browsers, versions, and so on.

Have you tried using different browsers, or if using Linux variant tried windows.

Narrow it down.

I do testing like you have no idea, I have upgraded, changed passwords HUNDREDS of times.

I've used mozzarella, edge, chrome...

Now I did see this back around v1.5.22 once or twice but each time SSH into using credentials cleared issue.

Right now over 20,000 installations of v1.5.25 and a "few" reports of this issue.

We are months behind WS4 release, should we dropped everything and go back into this blind or keep pushing WS4?

We are a small company devastated by Covid and Biden delaing $5 million in products delivery by 3 years that we have to sell (1G only) but everyone wants 10G and 2.5G copper.

The WS4 line is so much more advanced its like comparing a cassett Walkman to your cell with ear buds.

If this issue was wide spread there would be hundreds of people reporting issues not 2 or 3.

If you can nail it down by detailing hey if I use this os and browser and versions it works fine, but if I use this os and browser version boom there it is. But then is it our fault or the os/browser?

[mfwbooks]

Recently upgraded from 1.5.2 to this latest version and it seems to work fine but then all out of no where it kicks us out of the gui and we cant log in it will say tryign to re-establish connection and sometimes gives us the login page but wont accept anything? We can log in via CLI/ssh and access everything just fine. One 8 port DC switch is at a tower the other one a 12 port dc switch is here in the office waiting to be deployed with the same issue.

If we log in via CLI and do a cold reboot, it seems to fixe the issue for a time but then some random time later we cant log back into the gui again.

Any help or suggestions is appreciated.

Thanks

We upgraded to 1.5.25 back in January.

We have seen this issue 2 times (one time on each on 2 different switches).
The switch itself is working and all traffic flows as expected. The GUI does not work. SSH works fine. For the GUI -- You load the page, login and then it kicks us out. Or we may get connected and navigate one or two pages and then we get kicked out. We have Netonix Manager running and when this happens Netonix Manager starts reporting the swtich is offline, then online, then offline, then online, etc.


We found that if we ssh to the unit and issue these commands:
cmdline
/etc/init.d/lighttpd restart

Then the GUI returns to normal and works fine.

One switch is WS-12-250-AC and the other one is WS-26-400-AC.

Since this has not impacted the function of the switch, only the GUI, and the fix of restarting lighttpd is pretty simple it has not been a concern for us. When I saw someone post with what appears to be the same issue, I thought I'd post the commands we found that resolved the issue for us without a reboot.

[JeffreyS]

Recently upgraded from 1.5.2 to this latest version and it seems to work fine but then all out of no where it kicks us out of the gui and we cant log in it will say tryign to re-establish connection and sometimes gives us the login page but wont accept anything? We can log in via CLI/ssh and access everything just fine. One 8 port DC switch is at a tower the other one a 12 port dc switch is here in the office waiting to be deployed with the same issue.

If we log in via CLI and do a cold reboot, it seems to fixe the issue for a time but then some random time later we cant log back into the gui again.

Any help or suggestions is appreciated.

Thanks

We upgraded to 1.5.25 back in January.

We have seen this issue 2 times (one time on each on 2 different switches).
The switch itself is working and all traffic flows as expected. The GUI does not work. SSH works fine. For the GUI -- You load the page, login and then it kicks us out. Or we may get connected and navigate one or two pages and then we get kicked out. We have Netonix Manager running and when this happens Netonix Manager starts reporting the swtich is offline, then online, then offline, then online, etc.


We found that if we ssh to the unit and issue these commands:
cmdline
/etc/init.d/lighttpd restart

Then the GUI returns to normal and works fine.

One switch is WS-12-250-AC and the other one is WS-26-400-AC.

Since this has not impacted the function of the switch, only the GUI, and the fix of restarting lighttpd is pretty simple it has not been a concern for us. When I saw someone post with what appears to be the same issue, I thought I'd post the commands we found that resolved the issue for us without a reboot.

I have also been experiencing this. It has effected a WS-12-250-AC and two WS-12-250-DC on our network so far.

For additional info we are running Network Manager on a Windows 10 VM on a separate VLAN from the management vlan of these switches. SSH and HTTPS are allowed through our firewalls between switches and Manager. VM is up to date on Windows Updates. Switches are on 1.5.25.

[Hobbes]

Updated two mini switches -- on both, the IGMP status page is now blank. Tried toggling IGMP on and off without any change.

[sirhc]

Our current focus is to concentrate on v3.0.0 for WS3 in about 3 weeks.

This is stepping stone to WS4 pre release around September.

After that we will take a week or so and address accumulated issues with WS line and release v1.5.26

[gadavis]

There appears to still be a bug with the NTP client on the Netonix v.1.5.25 firmware.

I have a couple of edge sites that go into low-voltage disconnect nightly ( ) due to worn-out batteries. When the come back online, their upstream-facing radio (powered by the Netonix) takes about 5 minutes to boot up and start passing traffic.

While that upstream-facing radio is down, the switch can't reach the NTP server at the hub site.

What I see in the logs is that ntp tries three times to get the time within the first 2 minutes of being powered on, and then gives up. I have to log into the switch UI and manually disable then re-enable NTP to get it to sync with the upstream hub site NTP server.

Here's a log snippet showing the three query attempts.

No further NTP messages are found in the logs after 16:01:27. The radio link comes up four minutes after that last NTP attempt at 16:05:27. No further entries in the log between 16:05:27 and 18:41:15. Time is still unset at 18:41:15, until I finally log in as admin and toggle the NTP configuration off and then on again.

Code: Select all

Dec 31 16:00:06 admin: stopped ntp daemon
Dec 31 16:00:06 admin: started ntp daemon
Dec 31 16:00:07 admin: sync time via ntp
Dec 31 16:00:11 system: Setting MAC address from flash configuration: EC:13:B2:84:61:6E
Dec 31 16:00:13 admin: stopped ntp daemon
Dec 31 16:00:13 admin: started ntp daemon
Dec 31 16:00:13 admin: sync time via ntp
Dec 31 16:00:14 admin: adding lan (eth0.128) to firewall zone lan
Dec 31 16:00:14 dropbear[706]: Running in background
Dec 31 16:00:15 netonix: 1.5.25 on WS-12-250-DC
Dec 31 16:00:22 STP: msti 0 set port 5 to discarding
Dec 31 16:00:25 STP: msti 0 set port 5 to learning
Dec 31 16:00:25 STP: msti 0 set port 5 to forwarding
Dec 31 16:01:22 switch[865]: Detected cold boot
Dec 31 16:01:23 switch[865]: PoE enabled on port 1, PoE Smart is starting cable check
Dec 31 16:01:24 switch[865]: PoE enabled on port 4, PoE Smart is starting cable check
Dec 31 16:01:24 switch[865]: PoE enabled on port 6, PoE Smart is starting cable check
Dec 31 16:01:24 switch[865]: PoE enabled on port 7, PoE Smart is starting cable check
Dec 31 16:01:24 switch[865]: PoE enabled on port 8, PoE Smart is starting cable check
Dec 31 16:01:24 switch[865]: PoE enabled on port 9, PoE Smart is starting cable check
Dec 31 16:01:24 switch[865]: PoE enabled on port 10, PoE Smart is starting cable check
Dec 31 16:01:24 switch[865]: PoE enabled on port 11, PoE Smart is starting cable check
Dec 31 16:01:25 switch[863]: temp sensor version 1
Dec 31 16:01:26 admin: stopped ntp daemon
Dec 31 16:01:27 admin: started ntp daemon
Dec 31 16:01:27 admin: sync time via ntp
...SNIP a bunch of MST and link state messages...
Dec 31 16:05:27 STP: MSTI0: New root on port 1, root path cost is 40000, root bridge id is 8192.2C-C8-1B-88-6F-1B

Dec 31 18:41:09 UI[803]: Configuration changed by admin (172.16.76.198)
Dec 31 18:41:09 UI[803]: Config_Version: 108 => 109
Dec 31 18:41:09 UI[803]: NTP_Enable: true => false
Dec 31 18:41:14 UI[803]: Configuration changed by admin (172.16.76.198)
Dec 31 18:41:14 UI[803]: Config_Version: 109 => 110
Dec 31 18:41:14 UI[803]: NTP_Enable: false => true
Dec 31 18:41:15 admin: stopped ntp daemon
Dec 31 18:41:15 admin: started ntp daemon
Dec 31 18:41:15 admin: sync time via ntp