Please post comments and bug reports for v1.2.0rc8 in this thread.
FIXES
- Fixed cable diagnostics (prevent php sessions from timing out)
- Fixed current multiplier on WS-6-MINI (was reporting twice the actual current useage)
- Fixed lightning bolt showing on disabled ports which should have been an "X"
- Fixed copyright notice
KNOWN ISSUES
- DHCP is broken
Released - 4/15/2015
Firmware v1.2.0rc8 bug reports and comments
-
sirhc - Employee
- Posts: 7347
- Joined: Tue Apr 08, 2014 3:48 pm
- Location: Lancaster, PA
- Has thanked: 1597 times
- Been thanked: 1318 times
Firmware v1.2.0rc8 bug reports and comments
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
-
lligetfa - Associate
- Posts: 1186
- Joined: Sun Aug 03, 2014 12:12 pm
- Location: Fort Frances Ont. Canada
- Has thanked: 305 times
- Been thanked: 381 times
Re: Firmware v1.2.0rc8 bug reports and comments
Confirmed.sirhc wrote:Please post comments and bug reports for v1.2.0rc8 in this thread.
FIXES
- Fixed current multiplier on WS-6-MINI (was reporting twice the actual current useage)
No issues. Installed on both the WS24 and MINI.
-
sirhc - Employee
- Posts: 7347
- Joined: Tue Apr 08, 2014 3:48 pm
- Location: Lancaster, PA
- Has thanked: 1597 times
- Been thanked: 1318 times
Re: Firmware v1.2.0rc8 bug reports and comments
So I know you guys are busy but I would like to move forward on getting v1.2.0 finalized as this version is needed to support the new models coming out like the WS-12-250-AC/DC, WS-8-250-DC, and the WS-6-MINI
I have installed it on all of my WISP's switches and see no problems.
I have tested it on about all I can think of.
So if you guys have the time and an extra switch or a low profile install please give it a good once over, particularly VLANs, RSTP, and the new features.
One nice feature with v1.2.0 is that it tells you under the POE configuration how many watts that port is rated at. Since newer revisions of models in the future may support different watts we felt this would be a good way to remind the user of how many watts each port is rated at.
This version also supports a LOT of new features and fixes to existing features that people requested
FIXES
- Fixed scrolling on status page
- Fixed DHCP when changing the management VLAN ID
- Fixed SNMP stats for new models
- Fixed stats for new models in CLI
- Fixed problem with SFP ports not showing correct STP state on 12 port models
- Fixed problem configuring STP Priority
- Fixed MAC table sometimes showing filtered entries
- Ensure flashing 48VH PoE LED remains on during reboot
ENHANCEMENTS
- Added fallback to static IP configuration if DHCP fails
- Added DHCP Snooping
- Added Ubiquiti Discovery
- Added Cisco Discovery
- Added TFTP auto backup for config
- Added buttons to reorder VLANs
- Added support for WS-6-MINI, WS-8-250-DC, WS-12-250-AC and WS-12-250-DC
- Added Power tab for DC models
- Added current ratings to PoE settings in UI
- Added board rev to flash configuration
- Added CLI command to show vlans
- Added CLI command to change ID of VLANs
I love the TFTP Auto Backup feature. Basically if you have a TFTP server setup in your NOC you can have the switch backup it's config each time someone saves/applies any changes.
So basically below I have the URL to the TFTP server and the file name to call the config
TFTP://206.XXX.XXX.9/bb-ws1
The backup file that it will create is "bb-ws1-XXX" where XXX is the unique config number so it does not overwrite the previous config backup.
This way if I lose a switch I can grab the config from the backup server and load it into the replacement switch and I am back up and running. We also have our Cisco routers backup to this same TFTP server so I always have the backup config for the routers as well. So in the event my tower gets hit by lightening and I lose everything I can grab a spare router and switch off the shelf and within minutes have them configured to drop in.
Also this version we but in arrows to move defined VLANs up and down in the list because you might want to reorder the list to make logical sense to the user, neat little creature feature.
And now as far as I know all the CLI commands are in so you can completely configure the switch in the CLI.
I have installed it on all of my WISP's switches and see no problems.
I have tested it on about all I can think of.
So if you guys have the time and an extra switch or a low profile install please give it a good once over, particularly VLANs, RSTP, and the new features.
One nice feature with v1.2.0 is that it tells you under the POE configuration how many watts that port is rated at. Since newer revisions of models in the future may support different watts we felt this would be a good way to remind the user of how many watts each port is rated at.
This version also supports a LOT of new features and fixes to existing features that people requested
FIXES
- Fixed scrolling on status page
- Fixed DHCP when changing the management VLAN ID
- Fixed SNMP stats for new models
- Fixed stats for new models in CLI
- Fixed problem with SFP ports not showing correct STP state on 12 port models
- Fixed problem configuring STP Priority
- Fixed MAC table sometimes showing filtered entries
- Ensure flashing 48VH PoE LED remains on during reboot
ENHANCEMENTS
- Added fallback to static IP configuration if DHCP fails
- Added DHCP Snooping
- Added Ubiquiti Discovery
- Added Cisco Discovery
- Added TFTP auto backup for config
- Added buttons to reorder VLANs
- Added support for WS-6-MINI, WS-8-250-DC, WS-12-250-AC and WS-12-250-DC
- Added Power tab for DC models
- Added current ratings to PoE settings in UI
- Added board rev to flash configuration
- Added CLI command to show vlans
- Added CLI command to change ID of VLANs
I love the TFTP Auto Backup feature. Basically if you have a TFTP server setup in your NOC you can have the switch backup it's config each time someone saves/applies any changes.
So basically below I have the URL to the TFTP server and the file name to call the config
TFTP://206.XXX.XXX.9/bb-ws1
The backup file that it will create is "bb-ws1-XXX" where XXX is the unique config number so it does not overwrite the previous config backup.
This way if I lose a switch I can grab the config from the backup server and load it into the replacement switch and I am back up and running. We also have our Cisco routers backup to this same TFTP server so I always have the backup config for the routers as well. So in the event my tower gets hit by lightening and I lose everything I can grab a spare router and switch off the shelf and within minutes have them configured to drop in.
Also this version we but in arrows to move defined VLANs up and down in the list because you might want to reorder the list to make logical sense to the user, neat little creature feature.
And now as far as I know all the CLI commands are in so you can completely configure the switch in the CLI.
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
-
mike99 - Associate
- Posts: 837
- Joined: Tue Nov 25, 2014 10:53 am
- Location: Quebec, Canada
- Has thanked: 95 times
- Been thanked: 245 times
Re: Firmware v1.2.0rc8 bug reports and comments
I tryed the STP comsmetic bug on SFP port that I reported on the following link and it's now fix.
viewtopic.php?f=17&t=583&p=4171#p4171
Thanks
Not sure about what was the STP priority problem I played a little with ports priority and seem to work fine.
It would be better for debbuging if STP show root switch. I don't see this information anywhere.
Via CLI, VLANs configuration is still buggy. On ports range for tagged port, all following port after the first will be set untagged. Also, minus u,t,e, are still accepted but not change to capital letter and, from my test on 1.1.5 but will retry it on this version, the config only interpret capital letters for tagging.
Edit: Minus letter u,t,e are now accepted in the config (thanks for fixing this), I can now ping a VLAN via a port tagged via a minus t.
PS: minus letter are shown also on WebGUI after setting vlan with minus letter so, for cosmetic relugarity purpose, maybe it would be better to transfer minus tagged letter to capital letter so it look like more professionnal while looking at WebGUI after configuring VLANs via CLI.
Via SSH:
Lost SSH acces to the switch so connected via console:
VLAN tab completetion is also wrong after entering tagging letter.
return
viewtopic.php?f=17&t=583&p=4171#p4171
Thanks
Not sure about what was the STP priority problem I played a little with ports priority and seem to work fine.
It would be better for debbuging if STP show root switch. I don't see this information anywhere.
Via CLI, VLANs configuration is still buggy. On ports range for tagged port, all following port after the first will be set untagged. Also, minus u,t,e, are still accepted but not change to capital letter and, from my test on 1.1.5 but will retry it on this version, the config only interpret capital letters for tagging.
Edit: Minus letter u,t,e are now accepted in the config (thanks for fixing this), I can now ping a VLAN via a port tagged via a minus t.
PS: minus letter are shown also on WebGUI after setting vlan with minus letter so, for cosmetic relugarity purpose, maybe it would be better to transfer minus tagged letter to capital letter so it look like more professionnal while looking at WebGUI after configuring VLANs via CLI.
Via SSH:
- Code: Select all
Netonix Switch(vlan 100)# port
<port> Port number
Netonix Switch(vlan 100)# port 1-12 t
Netonix Switch(vlan 100)# exit
Netonix Switch(config)# exit
Lost SSH acces to the switch so connected via console:
- Code: Select all
Netonix Switch# show vlans
ID Enable Description 1 2 3 4 5 6 7 8 9 10 11 12 13 14
---- ------ ----------- -- -- -- -- -- -- -- -- -- -- -- -- -- --
1 true Management U U U U U U U U U U U U U U
100 true VLAN 100 t U U U U U U U U U U U U U
VLAN tab completetion is also wrong after entering tagging letter.
- Code: Select all
Netonix Switch(vlan 100)# port 1 T[tab]
return
- Code: Select all
Netonix Switch(vlan 100)# port 1 TU,T,E>
Last edited by mike99 on Fri Apr 17, 2015 2:35 pm, edited 4 times in total.
-
mike99 - Associate
- Posts: 837
- Joined: Tue Nov 25, 2014 10:53 am
- Location: Quebec, Canada
- Has thanked: 95 times
- Been thanked: 245 times
Re: Firmware v1.2.0rc8 bug reports and comments
Setting ip address on a vlan crash the switch CLI.
VLAN netmask configuration is also buggy. It seem like it will only accept /24 and also crash the switch CLI when the value is accepted.
Changing the ID of the VLAN also crash CLI:
VLAN name configuration work fine, even with multiple line and even with special character including $.
- Code: Select all
Netonix Switch# configure
Netonix Switch(config)# vlan 100
Netonix Switch(vlan 100)# ip 172.29.28.20
% Invalid command
Netonix Switch(vlan 100)# ip address 172.29.28.20
Segmentation fault
admin@OpenWrt:/# exit
Please press Enter to activate this console.
VLAN netmask configuration is also buggy. It seem like it will only accept /24 and also crash the switch CLI when the value is accepted.
- Code: Select all
Netonix Switch(vlan 100)# ip netmask 255.255.255.128
% Invalid parameter.
Netonix Switch(vlan 100)# ip netmask 255.255.255.224
% Invalid parameter.
Netonix Switch(vlan 100)# ip netmask 255.255.255.0
Segmentation fault
admin@OpenWrt:/www#
Changing the ID of the VLAN also crash CLI:
- Code: Select all
Netonix Switch(vlan 100)# id 101
Segmentation fault
admin@OpenWrt:/www#
VLAN name configuration work fine, even with multiple line and even with special character including $.
Last edited by mike99 on Fri Apr 17, 2015 2:45 pm, edited 1 time in total.
-
sirhc - Employee
- Posts: 7347
- Joined: Tue Apr 08, 2014 3:48 pm
- Location: Lancaster, PA
- Has thanked: 1597 times
- Been thanked: 1318 times
Re: Firmware v1.2.0rc8 bug reports and comments
Thanks Mike, I made Eric aware of this and hope to post a fix for this and DHCP address not getting default gateway and DNS shortly.
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
-
mike99 - Associate
- Posts: 837
- Joined: Tue Nov 25, 2014 10:53 am
- Location: Quebec, Canada
- Has thanked: 95 times
- Been thanked: 245 times
Re: Firmware v1.2.0rc8 bug reports and comments
DHCP Snooping seem not fonctionnal.
Port 9 = Path to the DHCP server
Port 11 = port 1 of a edgerouter with static IP to access WebUI
Port 10 = edgerouter port 2
port 12 = edgerouter port 3
Activate DHCP Snooping on port 9, 10, 11 and 12. After, set port 2 and 3 of the router as dhcp client and both received a lease.
From what I read, devices connected to ports with DS activated should be able to receive DHCP lease but not be able to give DHCP lease.
Port 9 = Path to the DHCP server
Port 11 = port 1 of a edgerouter with static IP to access WebUI
Port 10 = edgerouter port 2
port 12 = edgerouter port 3
Activate DHCP Snooping on port 9, 10, 11 and 12. After, set port 2 and 3 of the router as dhcp client and both received a lease.
From what I read, devices connected to ports with DS activated should be able to receive DHCP lease but not be able to give DHCP lease.
-
sirhc - Employee
- Posts: 7347
- Joined: Tue Apr 08, 2014 3:48 pm
- Location: Lancaster, PA
- Has thanked: 1597 times
- Been thanked: 1318 times
Re: Firmware v1.2.0rc8 bug reports and comments
You're a busy buva Mike
Already passed along to Eric, hopefully we will release v1.2.0rc9 tonight with fixes for:
CLI VLAN stuff
DHCP Snooping
DHCP address not getting Gateway and DNS
Can you find anymore before we release v1.2.0rc9?
![Thumbs Up :thumbsup:](./images/smilies/thumbsup.gif)
Already passed along to Eric, hopefully we will release v1.2.0rc9 tonight with fixes for:
CLI VLAN stuff
DHCP Snooping
DHCP address not getting Gateway and DNS
Can you find anymore before we release v1.2.0rc9?
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
-
mike99 - Associate
- Posts: 837
- Joined: Tue Nov 25, 2014 10:53 am
- Location: Quebec, Canada
- Has thanked: 95 times
- Been thanked: 245 times
Re: Firmware v1.2.0rc8 bug reports and comments
Credentials password is not working, hash password is the same in both following "code". Password are also not apply live. If I change it to 1234 or whatever and try to login to the WebUI, the password is still "admin". User credentials change is working fine.
- Code: Select all
NetonixSwitch# configure
NetonixSwitch(config)# credentials name admin
NetonixSwitch(config)# credentials password 1234
NetonixSwitch(config)# exit
NetonixSwitch# cmdline
BusyBox v1.11.2 (2015-01-12 16:20:46 EST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
admin@OpenWrt:/www# grep admin config.json
"Credentials_Name": "admin",
admin@OpenWrt:/www# grep Credentials config.json
"Credentials_Password": "",
"Credentials_Name": "admin",
"Credentials_HashedPassword": "YWG41BPzVAkN6",
- Code: Select all
NetonixSwitch# configure
NetonixSwitch(config)# credentials name test
NetonixSwitch(config)# credentials password 789123
NetonixSwitch(config)# exit
NetonixSwitch# cmdline
BusyBox v1.11.2 (2015-01-12 16:20:46 EST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
admin@OpenWrt:/www# grep Credentials config.json
"Credentials_Password": "",
"Credentials_Name": "test",
"Credentials_HashedPassword": "YWG41BPzVAkN6",
-
mike99 - Associate
- Posts: 837
- Joined: Tue Nov 25, 2014 10:53 am
- Location: Quebec, Canada
- Has thanked: 95 times
- Been thanked: 245 times
Re: Firmware v1.2.0rc8 bug reports and comments
In VLAN mode, typing exit or end on a new vlan without change to the vlan will untag this VLAN on all port. Same with exit.
No bug on VLANs that already have a config.
- Code: Select all
NetonixSwitch# show vlans
ID Enable Description 1 2 3 4 5 6 7 8 9 10 11 12 13 14
---- ------ ----------- -- -- -- -- -- -- -- -- -- -- -- -- -- --
1 true Management U U U U U U U U U U U U U U
NetonixSwitch# configure
NetonixSwitch(config)# vlan 100
NetonixSwitch(vlan 100)# end
NetonixSwitch# show vlans
ID Enable Description 1 2 3 4 5 6 7 8 9 10 11 12 13 14
---- ------ ----------- -- -- -- -- -- -- -- -- -- -- -- -- -- --
1 true Management U U U U U U U U U U U U U U
100 true VLAN 100 U U U U U U U U U U U U U U
- Code: Select all
NetonixSwitch# show vlans
ID Enable Description 1 2 3 4 5 6 7 8 9 10 11 12 13 14
---- ------ ----------- -- -- -- -- -- -- -- -- -- -- -- -- -- --
1 true Management U U U U U U U U U U U U U U
NetonixSwitch# configure
NetonixSwitch(config)# vlan 100
NetonixSwitch(vlan 100)# exit
NetonixSwitch(config)# exit
NetonixSwitch# show vlans
ID Enable Description 1 2 3 4 5 6 7 8 9 10 11 12 13 14
---- ------ ----------- -- -- -- -- -- -- -- -- -- -- -- -- -- --
1 true Management U U U U U U U U U U U U U U
100 true VLAN 100 U U U U U U U U U U U U U U
NetonixSwitch#
No bug on VLANs that already have a config.
- Code: Select all
NetonixSwitch# show vlans
ID Enable Description 1 2 3 4 5 6 7 8 9 10 11 12 13 14
---- ------ ----------- -- -- -- -- -- -- -- -- -- -- -- -- -- --
1 true Management U U U U U U U U U U U U U U
100 true VLAN 100 T T T T T T T T T T T T U U
NetonixSwitch# configure
NetonixSwitch(config)# vlan 100
NetonixSwitch(vlan 100)# exit
NetonixSwitch(config)# exit
NetonixSwitch# show vlans
ID Enable Description 1 2 3 4 5 6 7 8 9 10 11 12 13 14
---- ------ ----------- -- -- -- -- -- -- -- -- -- -- -- -- -- --
1 true Management U U U U U U U U U U U U U U
100 true VLAN 100 T T T T T T T T T T T T U U
Who is online
Users browsing this forum: No registered users and 16 guests