v1.5.21 Bug Reports and Comments

[Stephen]

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
- If greater than 30 VLAN they will now be applied correctly - 1.5.21
- Radius login fixed - NOTE, POSSIBLE SECURITY HOLE FOUND IN ORIGINAL IMPLEMENATION (pre-1.5.17) - 1.5.21
- Autobackup filenames fixed - 1.5.21

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/22/2024

[Acentek_NetOps]

I upgraded my test unit to 1.5.21 and cant seem to get radius to work. I went back to 1.5.16 and verified its working on that load still.

[yahel]

At the risk of not posting in the right place, we noticed a new issue that was introduced when upgrading from 1.5.14 to 1.5.16.
The issue is voltage graphs on DC switches (specifically WS-12-250-DC ).
The graph looks like that - essentially making it useless.

https://photos.app.goo.gl/bEkn2w9etwtHm5Ye7
We had to downgrade multiple switches back to 1.5.14 to avoid this issue.
I would love to know if this was reported/addressed in later firmwares.

To further clarify - these are NOT REAL surges - this is happening consistently on multiple switches (>40) and is not happening when downgrading to 1.5.14

Thanks,

Yahel.

[sirhc]

Try version 1.5.21

Not interested in bugs found in OLD versions.

[yahel]

Do you have ANY reason to believe this bug (which was introduced between 1.5.14 and 1.5.16) has been addressed later?
If there is any such chance, I would gladly try it out - but nothing of that sort in the release-notes that I could find.

[sirhc]

Well we fixed a lot of stuff and it very stable.

Try it then report if not fixed.

Trust me it fixes a lot and is very stable.

If problem still there report and we'll fix.

Trust me bad issues including hackable and sfp issues and random boot loops and memory leaks all fixed.

[Stephen]

I upgraded my test unit to 1.5.21 and cant seem to get radius to work. I went back to 1.5.16 and verified its working on that load still.

I tested this before this version was released. We definitely fixed it.

However, like with many things, different flavors of systems may or may not introduce other issue's.

Here are a couple things to check that could help:

- What version of freeradius is your server running?
- Can you verify the freeradius server is pingable (assuming icmp is allowed on your network) and that STP is not blocking it.
- If all this checks out, can you send me your config in a PM?
- For testing radius, I also need to have the clients.conf and authorize radius files. (feel free to modify these as needed for privacy, I just need something I can test locally, that works on 1.5.16 but fails on 1.5.21)

Also, can you describe in a bit more detail what is going wrong?

For example, does ssh login and webui login both fail with the radius password. Or is it just ssh that fails? etc.

[mayheart]

Upgraded a core switch (WS-24-IDC) with about 130 vlans to 1.5.21 from 1.5.15rc3. Everything looks good. Reporting no issues.

TFTP backup is working like it should.

[yahel]

Ok - I've upgraded two switches to 1.5.21 and sadly - I can report that the voltage surges from 1.5.16 remain !! (See my post above in this same thread).
(To clarify - these same switches do not have voltage surges in 1.5.14).
Please do a deep dive at what must have been introduced between 1.5.14 and 1.5.16 --- I'm guessing some I2C bus related code.

Thanks!!

Yahel.

[IntL-Daniel]

There is a bug in SMTP email configuration. The "From Address" field is ignored and the sender is always "switch@localhost".