Netonix Forums

Please post comments and report bugs with v1.4.5 in this thread.

If you have issues with v1.4.5 please try v1.4.6rcX if available and see if your issues has been fixed.

PLEASE DO NOT REPORT ISSUES UNLESS YOU HAVE TRIED THE LATEST VERSION AVAILABLE FIRST.

v1.4.5 wrote:FIXED/CHANGED
- Fixed voltage fluctuation that affected a small percentage of WS-6-MINI, WS-8-150-AC, WS-8-150-DC
- Updated SSH daemon to get more modern key exchange algorithm
- Watchdog no longer checks for link on port to be bounced
- Ignore the SFP ports when checking Priority values
- Changed throttle limits between switch core and CPU
- Fixed web UI login only using the first 8 characters of the password
- Removed Address from MODBUS configuration
- Fixed reset button on WS-6-MINI broken since v1.4.1
- Fixed web UI display for mobile devices
- Fixed dot1dStpRootCost SNMP stat being off by one

ENHANCEMENTS
- Added option to bounce link instead of POE for watchdog rules
- Added support for 1000BASE-BX SFP modules (including Fiberstore SFP-GE-BX)
- Added ability to configure QoS based on packet headers (MAC, IP, TCP ports, etc)
- Added support for Mikrotik S-RJ01 SFP module
- Show the SFP model number in UI
- Skip PoE watchdog if PoE is not turned on for a port
- Changed default Revert Timer value from 60 to 180 seconds
- Added range for DSCP and PCP values in QoS rules
- Removed DSCP and PCP mappings from QoS config

KNOWN ISSUES
- Some language templates need help - please contact us to help

Released 11/15/2016

I have upgraded to 1.4.5 from 1.4.4. Previously I had configured QOS port mappings. After the upgrade, all QOS settings were gone and I had to set it again. But before I entered any rule all ports already counted packtes to Q7? For me sounds like the similar bug like previously this "- Fixed utility packets using Tx Q1 instead of Q0" ?

There is still persist the issue with mobile device view - it is not possible to click option per port in main status page. I have reported this at least one time in the past before the mobile view was broken at all.

View is broken when using a width less than the with background with Chrome on Linux. I realized it while splitting monitor in half (two windows side by side) on a full HD monitor. That probably related to mobile device view problem. I try several switch with 1.3.7, 1.3.8 and 1.4.2. The 1.4.5 was the only one with this behavior. Yes, I know I should update but we must also not fix what not broken and I didn't really need any feature added since now (QoS) and MSTP comming next.


I added some picture, 1.4.5 at first with large enough width. 1.4.5 view when width of the window is too short, 1.4.5 view that don't came back fine after resing large enough (only the tab that as affect view with behavior like this so if it was to small at status and you resize large enough and move to a other tab, only status will still be wrong, even if you change tab and come back). I also add a picture of 1.4.2 with too short width not affected by the view bug.

Added checkbox to enable and disable QoS rules is a nice option. That will help teest QoS.

Edit: Just saw that resing large the window width large enough fix the view problem most of the time but not alway like shown on attached picture (1.4.5 large enough width after not large enough view bug.PNG). Testing more, it seem like the tab always broke in 2 lines with resising not large enough but the port show won't always beavior the same way. Sometime broke in 2 lines, but most of the time, not.

I created a random password for the switch that uses !! in the password and telnet login does not work. All the other logins work fine

slowe wrote:I created a random password for the switch that uses !! in the password and telnet login does not work. All the other logins work fine

I couldn't duplicate this. I tried "foo!!bar", "foobar!!" and "!!foobar" and they all worked fine with the UI, ssh and telnet.

IntL-Daniel wrote:I have upgraded to 1.4.5 from 1.4.4. Previously I had configured QOS port mappings. After the upgrade, all QOS settings were gone and I had to set it again. But before I entered any rule all ports already counted packtes to Q7? For me sounds like the similar bug like previously this "- Fixed utility packets using Tx Q1 instead of Q0" ?

And wahat about this, could you replicate?

1.4.5 good so far except for some switches which have previously been overlooked as having DS ticked possibly by default, suddenly started having effect after upgrade as it stopped some of our VoiP clients recieving dhcp from our asterisk box untill unticked. We have had other upgrades enable stp as well.
otherwise they still get better and better thanks for all your efforts

Eric Stern wrote:

slowe wrote:I created a random password for the switch that uses !! in the password and telnet login does not work. All the other logins work fine

I couldn't duplicate this. I tried "foo!!bar", "foobar!!" and "!!foobar" and they all worked fine with the UI, ssh and telnet.

I factory reset the device and now it works.

Is there any command to enable telnet from the cli?