Ok so sounds like that was just a fluke but why do the 5ghz 450 SM have a bunch of frequencys unchecked after upgrading to 13.2 final? I did not notice that in beta
— Sent from Mailbox On Fri, Nov 14, 2014 at 6:18 AM, Kurt Fankhauser via Af <[email protected]> wrote: > I updated some 2.4Ghz 450 stuff overnight (previously on build 22) and did > not loose any of the 2.5mhz channelson SM's > Kurt Fankhauser > Wavelinc Communications > P.O. Box 126 > Bucyrus, OH 44820 > http://www.wavelinc.com > tel. 419-562-6405 > fax. 419-617-0110 > On Fri, Nov 14, 2014 at 2:54 AM, Rajesh Vijayakumar via Af <[email protected]> > wrote: >> George, >> Glad to see it upgraded successfully. And thanks for bravely trying it. >> >> Ryan, >> We are continuing our investigation. I will post an update to the list >> tomorrow morning. Please contact me ( >> [email protected]) or Cambium support off list. We >> will get to the root of this as soon as possible. >> >> Rajesh Vijayakumar >> Cambium Networks >> >> >> On Fri, Nov 14, 2014 at 1:14 AM, George Skorup (Cyber Broadcasting) via Af >> <[email protected]> wrote: >> >>> I just got done with that sector and everything went fine. Checked all >>> of the SM scan lists before (all running 13.1.3) and after they updated to >>> 13.2. They all look like this still: >>> >>> >>> >>> On 11/14/2014 12:30 AM, George Skorup (Cyber Broadcasting) via Af wrote: >>> >>> I know I said I was done for the night, but I'm going to update a 2.4 450 >>> sector here shortly. It's on 2460/20MHz, so hopefully nothing bad happens. >>> >>> On 11/14/2014 12:25 AM, Rajesh Vijayakumar via Af wrote: >>> >>> We looked at all the recent changes than went in to 13.2 but did not find >>> anything that would explain this behavior. Also tried to recreate it in the >>> lab on a 2.4 GHz setup, but the SM kept all the checked frequencies after >>> upgrade from 13.1.3 to 13.2. >>> >>> Has anyone else upgraded a 2.4 GHz sector and run into this issue (or >>> did not run into this issue)? >>> >>> Rajesh Vijayakumar >>> Cambium Networks >>> >>> >>> On Thu, Nov 13, 2014 at 10:45 PM, Aaron Schneider via Af <[email protected]> >>> wrote: >>> >>>> We are investigating the other issues, but with respect to 5767.5 and >>>> 5807.5, those two were affected by a bug fix, in that pre-13.2, 5767.5 was >>>> actually enabling 5767.20, due to an obvious typo in the scan list code, >>>> and 5807.5 was actually enabling 5807.00, due to another typo bug in the >>>> code. So correcting these two items may have left them unchecked on an >>>> upgrade to 13.2, but they weren’t valid scan frequencies anyways. >>>> >>>> >>>> >>>> These two updates didn’t make the release notes due to an oversight. >>>> These two frequency updates are in no way related to what is being reported >>>> for the 2.5MHz center channels coming back unchecked for 2.4. we are >>>> investigating. >>>> >>>> >>>> >>>> -Aaron >>>> >>>> >>>> >>>> *From:* Af [mailto:[email protected]] *On Behalf Of *George Skorup >>>> (Cyber Broadcasting) via Af >>>> *Sent:* Thursday, November 13, 2014 9:25 PM >>>> *To:* [email protected] >>>> *Subject:* Re: [AFMUG] 13.2 Issue (Removing frequency checkboxes) >>>> >>>> >>>> >>>> 13.2 on the SM definitely does not jive with build 32 on the AP. So.. >>>> don't do that. I forgot I still had that AP on build 32 until it was too >>>> late. SMs would pop in session for about 2 seconds and go down again. >>>> Luckily updating the AP to 13.2 official fixed it. >>>> >>>> I'm also seeing 5GHz SMs losing freqs. But it's funny, like 99% of them >>>> only lose 5767.5 and 5807.5. I try to avoid the 2.5 centers whenever I can >>>> since I've noticed exactly what you guys are seeing here in the past, ALL >>>> of the 2.5 centers disappear. I don't use 5MHz bandwidth, and I usually >>>> lock the scan list on the SM down to the band the AP is operating in. So >>>> maybe that's why I was losing only a couple freqs. >>>> >>>> On 11/13/2014 9:12 PM, Ryan Ray via Af wrote: >>>> >>>> It's crazy. No warning, no release notes about it. How does this come >>>> out of all the betas and you lose your SM's because a frequency isn't >>>> checked... >>>> >>>> >>>> >>>> On Thu, Nov 13, 2014 at 7:09 PM, timothy steele via Af <[email protected]> >>>> wrote: >>>> >>>> Yeah I noticed that same with 5Ghz looks like they unchecked the rarely >>>> used channels in SM with 13.2 programmer was probably thinking he was >>>> helping but lots are going to complain >>>> >>>> >>>> — >>>> Sent from Mailbox <https://www.dropbox.com/mailbox> >>>> >>>> >>>> >>>> On Thu, Nov 13, 2014 at 10:06 PM, Ryan Ray via Af <[email protected]> wrote: >>>> >>>> Just did a >200 group of SM's and the upgrade has removed frequencies >>>> that were previously checked. I followed the guide and did the SM's first >>>> and AP's last. Luckily the majority of these can see another AP but what >>>> the fuck... >>>> >>>> >>>> >>>> About half of these SM's were on 13.2(34) and the other half were on >>>> 13.1.3... >>>> >>>> >>>> >>>> This is what it looks like after an update >>>> >>>> >>>> >>>> <image.png> >>>> >>>> >>>> >>>> >>>> >>>> Pre update they were all >>>> >>>> >>>> >>>> <image.png> >>>> >>>> >>>> >>>> >>>> >>>> URG >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> >>> >>> >>> >>
