v1.5.22 Bug Reports and Comments

[Stephen]

Latest WS Stable Release: v1.5.22


***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. [color=#000000](THIS IS CHRIS, I THINK BEST EVER)
[/color]
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
- DHCP fixed - 1.5.22
- web conf check command fixed - 1.5.22
- SMTP From Address now used when populated, otherwise defaults to switch ip - 1.5.22
- Ingress/Egress Throughput samples now account for delays lasting longer than a second, preventing weird spikes on port status - 1.5.22
- Memory corruption spikes on smart DC switch Input Voltage graphs looks fixed after 24 hour testing, please report if more are seen - 1.5.22

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 12/5/2024

[yahel]

So far, two DC switches in the lab are doing fine - no voltage surges - yay!
We'll start upgrading the first 5-10 switches tonight between 2am and 5am (easy to reach locations) and give it a few days before we continue to roll...

Highly appreciative of your efforts Netonix-team !!

[sirhc]

I upgraded all my WISP switches last night to v1.5.22, ALL went SMOOTH.

The biggest thing I like about this new version is the SFP fixes as every now and then an SFP would not come back and I had to roll a truck to pull and re-insert SFP.

Now in a previous version like v1.5.18+/- I had 1 SFP that did not come up. I went to Ports Tab and disabled saved applied then enabled saved applied and it came up. I replaced the SFP anyway and since then no issue.

I also had an SFP around v1.5.18+/- that did not come back up and enable disable, no love, so I replaced it, and again no issues after that and have done several upgrades with no issues since.

Really hope to get get more positive feed back on this to give people confidence to upgrade and eliminate older versions with the hackable code. BUT EVEN SO IT IS HIGHLY RECOMMENDED TO ALWAYS USE THE ACCESS CONTROL LIST.

[Dawizman]

The SFP issue was a huge frustration for us in the past. Glad to hear that bug is resolved.

[bipbaep]

Yeah so upgrade did not go so smoothly.
LAB upgraded a couple of WS-6-MINI, WS-8-150-DC, WS-12-250-DC that all went fine.
So upgraded a WS-12-250-AC that did not come up. The PtP-link that is connected to it gets power and there is link on the ethernet, but don't see any MAC-address on the connected antenna.
Test upgraded a WS-12-400-AC on the bench, same happened. Switch boots as everything is normal. Connecting serial and reading the config, everything seems okay, but don't respond to ping/HTTPS/SSH etc.
Factory defaulting the switch and it starts responding at 192.168.1.20 as soon as it boots.
Back to the WS-12-250-AC that did not come back up: As this is a ferry travel away, that was a real bummer to upgrade. But since it worked so good on the first switched we took the chance to upgrade it. Since we thought that there was highest risk of upgrading DC switches.

Any idea whats going on?

[sirhc]

Yeah so upgrade did not go so smoothly.
LAB upgraded a couple of WS-6-MINI, WS-8-150-DC, WS-12-250-DC that all went fine.
So upgraded a WS-12-250-AC that did not come up. The PtP-link that is connected to it gets power and there is link on the ethernet, but don't see any MAC-address on the connected antenna.
Test upgraded a WS-12-400-AC on the bench, same happened. Switch boots as everything is normal. Connecting serial and reading the config, everything seems okay, but don't respond to ping/HTTPS/SSH etc.
Factory defaulting the switch and it starts responding at 192.168.1.20 as soon as it boots.
Back to the WS-12-250-AC that did not come back up: As this is a ferry travel away, that was a real bummer to upgrade. But since it worked so good on the first switched we took the chance to upgrade it. Since we thought that there was highest risk of upgrading DC switches.

Any idea whats going on?

So you have a PTP link
Radio on far side was plugged into a WS-12-250-AC

You upgraded said WS-12-250-AC (what version was it running) (How long was it up) (How much memory was being used as older versions had a memory leak)
What services were you using such as SNMP
I always check memory usage before upgrade especially with older version with memory leak when using SNMP
No idea unless OLD version up for long time low on memory especially if using SNMP which has been discussed on forums

On WS-12-400-AC have no idea other than very old firmware with no issues EXCEPT with certain SFP modules however once upgraded to v1.5.22 the number of SFP modules that can cause an issue is very very low.

SFP modules that are bad or dont follow spec can cause boot loops. Much less common once up to v1.5.22 but I always still test off brand SFP modules with a firmware upgrade and a couple warm boots and disable save apply enable save apply in UI. If any issues I don't use them.

When you get to unit plug in console cable and observe what's happening and please report back.

Sadly if 100 people upgrade and have no issues your lucky if a couple take time to report it.

But every single person with a problem will report back and there are hundreds of thousands of these units out there.

Based on download of v1.5.22 I would "guess" hundreds if not thousands have been upgraded just fine.

But that does not help you. Please report back once you console into far side unit. I would take extra SFP modules if your using them.

[ripv]

Just finished upgrading all of our WISP switches and am delighted to report, all went perfectly.

All were DC units, small number of WS8-150DC, mostly WS12-250DC and a small number of WS26-DC. Most units have SFP modules installed mixed brands and models. All were on v1.5.14 and had ACL enabled but wanted to upgrade anyway to be on the latest v1.5.22 firmware, for all the obvious reasons.

We don't use SNMP, I did check memory before upgrading and all were good, most of these switches had 2+ years of uptime, probably since we installed v1.5.14 - all have been rock solid in production.

The only thing I had to be careful of was to remember to reset the password on each switch after the upgrade completed !

[sirhc]

Just finished upgrading all of our WISP switches and am delighted to report, all went perfectly.

All were DC units, small number of WS8-150DC, mostly WS12-250DC and a small number of WS26-DC. Most units have SFP modules installed mixed brands and models. All were on v1.5.14 and had ACL enabled but wanted to upgrade anyway to be on the latest v1.5.22 firmware, for all the obvious reasons.

We don't use SNMP, I did check memory before upgrading and all were good, most of these switches had 2+ years of uptime, probably since we installed v1.5.14 - all have been rock solid in production.

The only thing I had to be careful of was to remember to reset the password on each switch after the upgrade completed !

Thank you very much ripv, most who have no issues don't bother reporting, but all who have issues do so it creates a false sense of unstable or bad firmware so many people don't upgrade.

THANK YOU AGAIN VERY MUCH!

[josh@belwave.com]

I've upgraded a few of our units and have noticed that LLDP/CDP data is not being forwarded to the trunk ports as previously happened. The device can see them via the discovery tab, but the connected devices do not see each other via LLDP/CDP.

I have not had any units higher than 1.5.14 so i'm not sure which firmware presented this change.

[sirhc]

I've upgraded a few of our units and have noticed that LLDP/CDP data is not being forwarded to the trunk ports as previously happened. The device can see them via the discovery tab, but the connected devices do not see each other via LLDP/CDP.

I have not had any units higher than 1.5.14 so i'm not sure which firmware presented this change.

Please diagram this out with more details.