Page 1 of 5
FIRMWARE BUG ALERT
Posted: Tue Jan 27, 2015 6:07 pm
by sirhc
Any firmware after v1.1.0rc5 has a VLAN bug that was reported today.
We hope to have a FIXED release today yet.
I posted final release v1.0.10 for download and or v1.1.0rc5 for now
We are sorry for the issue.
You can downgrade with no issues.
If you are using VLANs we recommend you downgrade immediately and we will release v1.1.0rc15 ASAP.
Do not issue any config changes if you are working or reboot your switch until you downgrade.
Re: FIRMWARE BUG ALERT
Posted: Tue Jan 27, 2015 7:02 pm
by sirhc
v1.1.0.rc14 Released as fix BUT IF FAILED READ ON
Re: FIRMWARE BUG ALERT
Posted: Thu Jan 29, 2015 12:19 am
by Simple
thanks for the heads up. Luckily I had not updated the firmware before i recieved your PM. Everything's good here. I will post a formul review of the WS24 once I've completed testing. It is in the rack and running good so far with what we are testing with.
Re: FIRMWARE BUG ALERT
Posted: Thu Jan 29, 2015 12:28 am
by lligetfa
sirhc wrote:...we will release v1.1.0rc15 ASAP...
I went to rc15 from rc13 today. I am not using VLANs so cannot report on that aspect.
Re: FIRMWARE BUG ALERT
Posted: Thu Jan 29, 2015 1:28 am
by sirhc
I just upgraded my WISP towers with v1.1.0rc15 and all went well
CLICK IMAGE BELOW TO SEE FULL SIZE
- v1.1.0rc15.png (159.14 KiB) Viewed 8008 times
Re: FIRMWARE BUG ALERT
Posted: Sat Jan 31, 2015 11:19 pm
by adairw
I don't think this issue is fixed... I put 1.1.0rc15 on a ws-24a today to deploy at a tower and I had some very weird vlan issues that only went away after making a change and applying the vlan page 2 or 3 times.
I haven't down graded as I had to much down time as it is for today.
What info would you want to troubleshoot this?
Adair
Re: FIRMWARE BUG ALERT
Posted: Sat Jan 31, 2015 11:29 pm
by sirhc
adairw wrote:I don't think this issue is fixed... I put 1.1.0rc15 on a ws-24a today to deploy at a tower and I had some very weird vlan issues that only went away after making a change and applying the vlan page 2 or 3 times.
I haven't down graded as I had to much down time as it is for today.
What info would you want to troubleshoot this?
Adair
Well Monday I will have Rory get in touch with you but I am running pretty tricked out VLANs on many towers with this version with no issues?
Or tomorrow
MAYBE as we are scheduled to try a different tower config early tomorrow morning and I may meet up with him at my WISP office afterwards?
CLICK IMAGES BELOW TO SEE FULL SIZE
- vlan1.png (240.74 KiB) Viewed 7967 times
- vlan2.png (211.78 KiB) Viewed 7967 times
POSSIBLE v1.1.0rc15 DHCP BUG - 2/1/2015
Posted: Sun Feb 01, 2015 1:30 am
by sirhc
Joe reported a possible problem with this version if you are using a DHCP address which caused his switch to go into a reboot loop which we are investigating.
Firmware version: v1.1.0rc15
Condition: Switch set to get DHCP address (Microtic router)
Symptom: Boot Loop
Recovery: press and hold factory default for 10 seconds until lights loop red or 10 seconds when powering up
If you are using a static IP address this is not an issue.
There are a few strange configuration variables here which is that Joe does all his VLANs in the MT and sets all his switch ports to T,not sure how this effects things but we will test on Monday.
See possible bug description / solution here:http://forum.netonix.com/viewtopic.php?f=17&t=438#p2784
Re: FIRMWARE BUG ALERT
Posted: Sun Feb 01, 2015 1:45 am
by adairw
Not use DHCP here, would never use DHCP for management purposes.
Very odd behavior. I was tagging 4 vlans in port 23 and untagging them on ports 9, 10, 11 & 12. Until I updated the vlans page a couple times by making a change and save/applying only port 9 would work. after the couple of applies the rest of them started working.
I logged in later to add another tagged vlan on some other ports and when i saved, it caused the same behavior as before. the only port that that would pass traffic on the above mentioned was port 9 until several saves.
Re: FIRMWARE BUG ALERT
Posted: Sun Feb 01, 2015 1:48 am
by sirhc
adairw wrote:Not use DHCP here, would never use DHCP for management purposes.
Very odd behavior. I was tagging 4 vlans in port 23 and untagging them on ports 9, 10, 11 & 12. Until I updated the vlans page a couple times by making a change and save/applying only port 9 would work. after the couple of applies the rest of them started working.
I logged in later to add another tagged vlan on some other ports and when i saved, it caused the same behavior as before. the only port that that would pass traffic on the above mentioned was port 9 until several saves.
Please post a screen shot of your full VLAN page here so we can see what your doing and Rory and I will discuss this tomorrow.