Netonix Forums

FIXED/CHANGED
- Updated support for TLS v1.2 for new browser updates including WS-8-150-DC and WS-8-150-DC - NCS
- Updated support for TLS v1.2 for email alerts
- Fixed the Dropbear vulnerability in Tenable.io (Nessus)

ENHANCEMENTS

KNOWN ISSUES
- SSH KEYs broken
- POE options per port messed up for models WS-12-DC / WS-12-250-AC - NCS / WS-12-400-AC - NCS
- WEB UI issues when not at 100% Zoom on browser especially on VLAN TAB
- Some language templates need help

Released 2/18/2022

I reported v1.5.10 did not work properly with the WS-8-150-DC.

I can now report v1.5.11 does appear to work properly with the WS-8-150-DC.

All good here also.

After installing the new firmware 1.5.11 on the WS-8-150-DC it resolved the mismatch error but did receive the below warning


Warning: expected 1 fans but found 0 - from Netonix Switch

Have updated 3 switches and this has occurred on 2 of them already - Updated from 1.5.0 to 1.5.11. on the switches that this error has occurred

JockGraham wrote:After installing the new firmware 1.5.11 on the WS-8-150-DC it resolved the mismatch error but did receive the below warning


Warning: expected 1 fans but found 0 - from Netonix Switch

Well I and several others have tested this to work with the WS-8-150-DC.

The error you are reporting is a fan error.

Could be you have a failing fan?
You can go to the Device/Status tab and click the button in the fan section to try and test/detect the fan.
You could also try a reboot.
If the unit is nearby you might want to go verify the fan is running and sounds OK.

Further to this fan error - I've updated the firmware from 1.5.6 and 1.5.9rc1 on the WS-8-150-DC and i did not receive the fan error, but when i upgrade from 1.5.0 the fan error has happened on both occasions.
I've tried downgrading to 1.5.9rc1 1.5.5 and 1.5.0 and error is still present

Running fan test - red exclamation mark appears next to RPM and FAN1 speed: ERR

Will try and verify fan sound, in later post

Other than a hard reboot on site, i'm not sure what else i can do?

Well v1.5.0 is VERY OLD firmware released 6/4/2018, so is possible this unit's fan could be failing or has excessive dust/dirt build up???

In late 2018 to early 2019 we changed fans which required new code/firmware but this should not require an incremental upgrade and pressing the fan detect/test button would recover that info anyway.

I will double check v1.5.11 again with a WS-8-150-DC specifically for fan control but will have to wait until later tonight until I can get someone to swing into the facility and setup a WS-8-150-DC in a testing station so I can access it from home.

Now the unit they will setup for testing will obviously have a NEW fan in it so another test would be to test the unit with an OLD style fan which I can not do until tomorrow as I will have to find one and swap it out.

If it is a failing fan we do sell replacement fans on the site.

OK I tested WS-8-150-DC specifically looking at fan control with v1.5.11, it appears to work just fine.

The caveat is this WS-8-150-DC is Board Rev F with a NEW style fan.

Please provide the MAC address(s), with that I can determine your board Rev, date of MFG, and fan type as we keep detailed records of every unit built including board info, power supply info, fan(s) used, basically every aspect of what is in each unit, which production line it came from, and who tested / serialized it.

Update:
Tested WS-8-150-DC Rev F with both NEW and OLD style fans and v1.5.11 worked with both fans and all other aspects of the WS-8-150-DC also tested OK with v1.5.11

Going to have to go with fan is failing at this point.

from the log of WS-10-250-AC just after the upgrade and reboot:

Code: Select all


Jan 1 00:00:14 system: Setting MAC address from flash configuration: EC:13:B2:XX:XX:XX
Jan 1 00:00:17 switch: adding lan (eth0) to firewall zone lan
Jan 1 00:00:18 dropbear[780]: Running in background
Jan 1 00:00:19 netonix: 1.5.11 on WS-10-250-AC
Jan 1 00:00:21 UI: web config OK
Jan 1 01:00:38 switch: removing lan (eth0) from firewall zone lan
Jan 1 01:00:41 switch: adding lan (eth0) to firewall zone lan
Jan 1 01:00:43 switch: removing lan (eth0) from firewall zone lan
Jan 1 01:00:46 switch: adding lan (eth0) to firewall zone lan
Jan 1 01:00:55 switch: adding lan (eth0) to firewall zone lan
Jan 1 01:00:56 dropbear[1706]: Failed listening on '22': Error listening: Address already in use
Jan 1 01:00:56 dropbear[1706]: Early exit: No listening ports available.
Jan 1 01:00:56 dropbear[1713]: Running in background
Jan 1 01:00:56 system: starting ntpclient
Feb 21 10:31:21 switch[1780]: temp sensor version 3
Feb 21 10:31:22 switch[1782]: Detected warm boot


??? Failed listening on '22': Error listening: Address already in use

IntL-Daniel wrote:from the log of WS-10-250-AC just after the upgrade and reboot:

Jan 1 01:00:56 dropbear[1706]: Failed listening on '22': Error listening: Address already in use
Jan 1 01:00:56 dropbear[1706]: Early exit: No listening ports available.
Jan 1 01:00:56 dropbear[1713]: Running in background

Could you please provide the MAC address so I can check records. I am not sure why people are always concerned with providing the MAC as it is not a security hole except within the same subnet because you can not address a device on the hardware layer (MAC) from outside the routed subnet only from within the subnet on same flat network segment.

The WS-10-250-AC was EOL and last manufactured in October of 2017, First Manufactured in October 2015.

The WS-10-250-AC spans 3 board Revs - D, E, F

This is important as a Board Rev only increases because something changed in hardware, sometimes it is innocuous sometimes not.

Also it is important to tell what firmware version you are upgrading from.

Updated:
We went ahead and tested the WS-10-250-AC Rev D,E,F since we did not know what yours was.
We obviously updated from whatever firmware version was on the units again that info was not provided.

Results of our tests showed that v1.5.11 worked on all 3 board revisions (D,E,F) and we did not see your error.

The error message being reported is dropbear which is the service for SSH and Telenet, the 22 is the port it is attempting to listen on.

Since you can only get the boot log/scroll from the console I assume your serial port is working just fine. Question is why is dropbear complaining that port 22 is already in use?

"My" theory since I have not yet talked to one of the programmers.
Depending on how OLD your firmware was there were security issues in OLD firmware pertaining to dropbear that were patched in previous releases which could allow a hacker to upload malware/viruses to your flash which you could clear with a power on factory default and I think it would also clear with a normal software default and I assume a firmware upgrade would also clear this but not sure. Again I want to stress this is "My" theory and I am not the programmers so I could be completely wrong on this. I have put in a request for the programmers to give me their theory as to why and will pass this on to you when I hear back from them.

However I want to reiterate that we have tested WS-10-250-AC Rev D,E,F and did not see this error, and all board functions worked properly on all three board Revs.