Netonix Forums

Latest WS Stable Release: v1.5.19

***NOTE:
If you have more than 30 VLANs, PingWatchdogs, PortBounces, QOS Rules, AccessControl Entries, or SSH Keys, please don't use this version, another is in progress to fix issue's with upgrade for very large config's.

**UPDATE, we have determined what the problem is and will be releasing a new release shortly to fix this issue.



***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


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

Wow you guys are giving new definition to the word "agile", especially on a Sunday. Thanks for 1.5.19 - I can confirm SSH is fixed and now needs credentials to authenticate. Maybe you took "OpenSSL" a bit too literally ;)

Joking aside, I'm genuinely impressed how a core team of only two people could produce something of this quality. A few bugs are always to be expected on any big codebase change and hats off to you both for fixing them so quickly. Thanks for all your hard work and for continuing to support the world of WISPs.

Glenn

What would you consider to be a "large number" of VLANs?

For the time being, if you have more than 30 you probably want to hold off.

> I'm not sure who said that, I use ssh key's on all my device's in my network, including our switches.

see the post below:

viewtopic.php?f=17&t=7359&start=20#p36445

> Can you explain in more detail the steps you take to add a key? I tested this a moment ago and it worked fine.

I'm adding normal keys with similar process, with firefox and chrome, and it doesn't work properly.

I managed to reset my WS-12-250-DC bricked by 1.5.17, upgraded to 1.5.19 and it is running ok,,, so far,,,

tcknudson wrote:I managed to reset my WS-12-250-DC bricked by 1.5.17, upgraded to 1.5.19 and it is running ok,,, so far,,,

How did you "reset" it? My flat stack DC switch is jacked big time. I checked out the config as our buddy Chris mentions, but it shows revision D, and the correct MAC, but won't boot up. I'll have to try and tackle it another day.

@stephen - - 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
What does "Be cautious" mean exactly? Nearly every site has more than one WS-12-250-DC, and I'm trying to go from 1.5.14 up to 1.5.19 for the SFP disable/enable bug fix in particular but gun shy after bricking a the flat stack DC switch that I had up on a hilltop.

Minor issue with UI I think. I just happen to notice on initial page load after login that the option for Discovery tab will be greyed if not previously enabled when any of the LLDP, CDP, Ubiquiti options have been enabled. Enabling or reenabling one of these options will allow the Discovery Tab option to be selectable.

I just happen to know notice after upgrading one switch to 1.5.19. I went and looked at some of our other netonix switches on 1.5.16 and same thing happens there.

WisTech wrote:@stephen - - 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
What does "Be cautious" mean exactly? Nearly every site has more than one WS-12-250-DC, and I'm trying to go from 1.5.14 up to 1.5.19 for the SFP disable/enable bug fix in particular but gun shy after bricking a the flat stack DC switch that I had up on a hilltop.

Generally speaking, when we say that we mean to rollout only to ideally a lab switch first to make sure the upgrade is OK. Or if that's not possible, ideally rollout to a single site to start with that is easy to reach if something goes wrong.

For this particular issue, you should be able to get the switch to boot on 1.5.17 by powering it down, opening the case, disconnect the I2C cable connected to the power supply and the power it up and let it boot normally. At that point you can upgrade to 1.5.19, reconnect the I2C cable and let it boot again to make sure it come's back. Based on feedback and testing it should be OK after that.

But as noted in this release, if you have more than 30 VLANs you probably want to go back to 1.5.16 or 1.5.17rc2 until we're able to complete restructuring some things to handle large configs. This is in progress, but will take a bit more time than other fixes we pushed over the weekend.

If the DC switch that is failing had more than 30 VLANs on it, it is failing for a different reason and you can fix this by using a console cable to default it, run:

Code: Select all

 reload defaults

Let it boot and upload different firmware (1.5.16 or 1.5.17rc2) and apply a backup to bring it back to working order until the newer version is released.