Netonix Forums

THIS THREAD IS CLOSED AND LOCKED
Latest WS Stable Release: v1.5.21


***NOTE:
WILL RESET PASSWORD BACK TO DEFAULT PASSWORD "admin" WHEN UPGRADING SO YOU MUST RESET PASSWORD AFTER UPGRADE IF UPGRADING FROM BELOW 1.5.17
(including 1.5.17rc2)


Personally we feel this is the most stable and best firmware since v1.4.8.

We have been testing this intensely for weeks.


***NOTE:
Some people use a smart power strip that will reboot a switch if pings stop.
This upgrade process can take longer than normal due to a lot of house
keeping from the vast changes in code. So if the unit is power cycled
during the upgrade it is bricked. Make sure to disable this or increase
time missing pings till reboot 10 minutes or more.


***NOTE (Smart DC Switches):
On the original 1.5.17 release, it was noted that certain DC models could get bricked.
It appears that during firmware ugprade, sometimes it will also upgrade the firmware on the power supply which was being blocked by a failed semaphore init. This could easily have been corruption on download or possibly upload. But we have also added additional checks in an attempt to circumvent this issue should it appear again.
HOWEVER,
especially for smart DC models. We suggest you upgrade one that is easy for you to access in case anything goes wrong FIRST. Then continue
rollout if all goes well.




FIXED/CHANGED
- lighttpd upgraded - 1.5.17rc1
- Openssl upgraded - 1.5.17rc2
- Upgrade failure on very old WS models -1.5.17rc2
- Patched security holes to prevent hacking, however you should always use the Access Control List as good practice. - 1.5.17
- Removed PHP replaced with compiled binaries (approximately 60,000 lines of code needed re-written) - 1.5.17
- Greatly improved SFP compatibility and Stability where you saw SFPs not come up after upgrades and reboots - 1.5.17
- Fixed potential multi reboots due to certian configurations during warm boots and firmware upgrades - 1.5.17
- Fixed NTP - 1.5.17
- Fixed SNMP memory leak - 1.5.17
- Upgraded password hash (WILL RESET PASSWORD BACK TO DEFAULT "admin"
WHEN UPGRADING REQUIRES PASSWORD RESET AFTER UPGRADE IF PREVIOUS VERSION
IS BELOW 1.5.17) - 1.5.17
- Upgraded session hash algorithm - 1.5.17
- Fixed MAC table lookup and updated to latest vendor list - 1.5.17
- NTP scripts fixed - 1.5.18
- fixed special characters (aka !#@, etc) during login - 1.5.18
- checks added during boot for smart i2c supply BE CAUTIOUS WHEN UPGRADING SMART DC SWITCH'S (WS-12-250-DC, WS-8-150-DC, etc) - 1.5.18
- ssh login now only accepts correct password - 1.5.19
- VLAN's and other variable length conf items no longer limited - 1.5.20


ENHANCEMENTS
- UI works faster as it is binary verses PHP - 1.5.17

KNOWN ISSUES
- WEB UI issues when not at 100% Zoom on browser especially on VLAN TAB
- Some language templates need help

Released 11/19/2024

Huge thanks for the push on these latest FW revisions Stephen (and Chris). Will start lab testing this release over the coming weeks and report back.

Unfortunately first deployment failed - WS 8 AC never came back from the install.

It was on 1.5.16
It had 100+ vlans configured
No watchdog

I've got the serial recovery tool running on it now, it gave no console output after waiting an hour to power cycle.

Port lights come on once it boots

(this was a bench switch for configuring gear, it had ALL of the vlans configured not just the ones it 'needed')

dfusselmanTurnkey wrote:Unfortunately first deployment failed - WS 8 AC never came back from the install.

It was on 1.5.16
It had 100+ vlans configured
No watchdog

I've got the serial recovery tool running on it now, it gave no console output after waiting an hour to power cycle.

Port lights come on once it boots

(this was a bench switch for configuring gear, it had ALL of the vlans configured not just the ones it 'needed')

If possible please provide me with a backup config and I will check this version. The last one who reported the issue originally had around 50 VLANs, but the limit should be about a 1000 now. So may be a different issue presenting itself.

For clarification so I can do proper testing, is this a WS-8-150-AC and what is the board rev? Or if easier I can extract this information from the units MAC address if you want to send that over.

To clarify, is there an upgrade path which will preserve the password?

Dawizman wrote:To clarify, is there an upgrade path which will preserve the password?

To fully clarify:

Upgrading to 1.5.20 from older firmware (pre 1.5.17, 1.5.18 or 1.5.19)

If you have already upgraded to the new iteration of the firmware (aka 1.5.17, 1.5.18, 1.5.19, or now 1.5.20) the password will be preserved going forward.


If not, unfortunately, we do not have a way to preserving it because the old algorithm used to generate the old hash has been deprecated due to security concerns, and obviously, we don't keep the clear-text password anywhere in the system when the password is changed by the user.

Downgrading from 1.5.17, 1.5.18, 1.5.19, or 1.5.20 to a lower version

These downgrades are possible, but due to the old firmware utilizing the deprecated algorithm, the password will be reset to "admin" again.
In this case though the firmware analysis step will warn you before proceeding so you can block the downgrade if you prefer.



Restoring an old config

If you restore an old config (made before 1.5.17) it will use the current password on the switch not the password in the restore point, so for example.

1. Say you upgrade to 1.5.20 from 1.5.14 (or anything before 1.5.17)
2. password is changed to "admin" by the upgrade.
3. Then password is modified to a preferred password
4. backup made from 1.5.14 is applied
5. backup password will be ignored and the current password will be used to ensure access is possible after reboot.

However, in this case also there is a popup that will occur to warn you about this and allow you to exit the action before proceeding if you prefer.

There is still a vLAN bug, only the first 33 vLAN is making traffic, all vLAN after table line 34 is ignored in the switch and no traffic!?

Br.
Carsten

Hightech wrote:There is still a vLAN bug, only the first 33 vLAN is making traffic, all vLAN after table line 34 is ignored in the switch and no traffic!?

Br.
Carsten

Hello Hightech, I have the config you sent me - we are testing this now.

There appears to be a bug with Radius. Radius authentication no longer works for me after upgrading to 1.5.20 from 1.5.16

Stephen wrote:

dfusselmanTurnkey wrote:Unfortunately first deployment failed - WS 8 AC never came back from the install.

It was on 1.5.16
It had 100+ vlans configured
No watchdog

I've got the serial recovery tool running on it now, it gave no console output after waiting an hour to power cycle.

Port lights come on once it boots

(this was a bench switch for configuring gear, it had ALL of the vlans configured not just the ones it 'needed')

If possible please provide me with a backup config and I will check this version. The last one who reported the issue originally had around 50 VLANs, but the limit should be about a 1000 now. So may be a different issue presenting itself.

For clarification so I can do proper testing, is this a WS-8-150-AC and what is the board rev? Or if easier I can extract this information from the units MAC address if you want to send that over.

Had serial console incorrect, didn't have a null in - this switch was able to come up after doing the long press restore. Unfortunately I dont have a backup config in the folder for this one.

Mac address is EC:13:B2:D2:F9:F8