Page 1 of 8
v1.4.6 Bug reports and Comments
Posted: Fri Nov 25, 2016 2:01 pm
by sirhc
Please post comments and report bugs with v1.4.6 in this thread.
PLEASE DO NOT REPORT ISSUES UNLESS YOU HAVE TRIED THE LATEST VERSION AVAILABLE FIRST.
v1.4.6 wrote:FIXED/CHANGED
- Fixed dot1dStpRootPort SNMP stat showing the wrong port number
- Fixed layout on small windows (mobile and desktop)
ENHANCEMENTS
KNOWN ISSUES
- Some language templates need help - please contact us to help
Released 11/25/2016
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
Re: v1.4.6 Bug reports and Comments
Posted: Fri Nov 25, 2016 7:46 pm
by IntL-Daniel
Is there a fix in 1.4.6 for the issue reported for 1.4.5 about the Q7?
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" ?
Re: v1.4.6 Bug reports and Comments
Posted: Sat Nov 26, 2016 12:34 pm
by Eric Stern
No changes regarding that. Could be that some packets slipped into Q7 before QoS was completely configured.
Re: v1.4.6 Bug reports and Comments
Posted: Sun Nov 27, 2016 6:14 am
by IntL-Daniel
So I decided do a test again. I disabled all QOS rules for Q7, then reset port counters and this is the result 1 minute later (just remeber I am on 1.4.6 and the same was in 1.4.5, not in 1.4.4):
Another reported issue with mobile view and imposibility to click options "per port" on main status page also still persist :-( Does anyone care about my reports?
Re: v1.4.6 Bug reports and Comments
Posted: Sun Nov 27, 2016 11:33 am
by Ludvik
I agree. I have one switch, one uplink, none other ports connected (traffic from and to switch is only management - SNMP, web, ssh and sometimes OSPF hello packet). TX Q7 is big number ... fifth times more than TX Q0. Scheduler is WRR.
RX Q7 is ZERO.
Re: v1.4.6 Bug reports and Comments
Posted: Sun Nov 27, 2016 12:45 pm
by Eric Stern
IntL-Daniel wrote:So I decided do a test again. I disabled all QOS rules for Q7, then reset port counters and this is the result 1 minute later (just remeber I am on 1.4.6 and the same was in 1.4.5, not in 1.4.4):
Q7 is used for sending LACP and STP packets to give them the highest priority.
IntL-Daniel wrote:Another reported issue with mobile view and imposibility to click options "per port" on main status page also still persist :-( Does anyone care about my reports?
It works on my android phone and tablet. Try again, maybe clear the cache or force a reload to make sure it hasn't cached anything from the previous version.
Re: v1.4.6 Bug reports and Comments
Posted: Sun Nov 27, 2016 1:12 pm
by Ludvik
Eric Stern wrote:Q7 is used for sending LACP and STP packets to give them the highest priority.
It's good idea :-) Sorry for bug in my brain ... In my example it is about 1 packet in Q7 per two second.
Re: v1.4.6 Bug reports and Comments
Posted: Sun Nov 27, 2016 3:17 pm
by IntL-Daniel
Eric Stern wrote:Q7 is used for sending LACP and STP packets to give them the highest priority.
We have STP and LACP disabled od Netonix and in the whole network but Q7 still counting, is that still correct?
Re: v1.4.6 Bug reports and Comments
Posted: Mon Nov 28, 2016 11:28 am
by mike99
sirhc wrote:- Fixed layout on small windows (mobile and desktop)
Just tested what I reported for desktop on 1.4.5 and it seem to work fine now.
Thanks.
Re: v1.4.6 Bug reports and Comments
Posted: Mon Nov 28, 2016 11:35 am
by IntL-Daniel
Eric Stern wrote:IntL-Daniel wrote:Another reported issue with mobile view and imposibility to click options "per port" on main status page also still persist :-( Does anyone care about my reports?
It works on my android phone and tablet. Try again, maybe clear the cache or force a reload to make sure it hasn't cached anything from the previous version.
Tested again with these results:
1/ WEB UI is useable only on very fast device (mobile) - i.e. Samsung SIII mini (i8190) is not enough, Samsung S6 is so far so good
2/ Options per port are correctly available only up to specific zoom level or without zoom. Below some zoom level the per port options are appeared somewhere down below your selcted port...you have to unzoom to see them (tested with Firefox and embeded Samsung browser).
Options per all ports works correctly in any zoom.