I haven't noticed any major difference with the interface between 3.2.x and 3.3... but perhaps that's just because I'm getting used to dealing with the interface on Elevated XM radios, which makes anything else seem extremely fast...
On Thu, Apr 20, 2017 at 11:07 AM, Steve Jones <[email protected]> wrote: > I dont like that in 3.x the interface has become a slug again > > On Wed, Apr 19, 2017 at 5:24 AM, [email protected] < > [email protected]> wrote: > >> The DFS bug was in relation to 40 MHz channels where it would see false >> positives. It does appear >> to be fixed in 3.3. >> >> On Tue, Apr 18, 2017 at 5:35 PM, Mathew Howard <[email protected]> >> wrote: >> >>> Yes, it's very much more better in 3.3. All of the XM radios we have >>> left have been pretty stable since upgrading to 3.3... but it's possible >>> that's partially because a lot of the problem radios got replaced before >>> 3.3 was released and only the good ones are left. I guess I'll find out >>> when I Elevate the next tower. >>> >>> Unfortunately most of our ubnt 5ghz stuff is XM because of the whole >>> thing with the XW radios being limited to the 5.8ghz band until after we >>> had already switched most of our 5ghz to ePMP... >>> >>> On Tue, Apr 18, 2017 at 4:21 PM, Mike Hammett <[email protected]> wrote: >>> >>>> I heard a lot of bad stuff about Elevate and XM radios. Is that more >>>> better now? >>>> >>>> >>>> >>>> ----- >>>> Mike Hammett >>>> Intelligent Computing Solutions <http://www.ics-il.com/> >>>> <https://www.facebook.com/ICSIL> >>>> <https://plus.google.com/+IntelligentComputingSolutionsDeKalb> >>>> <https://www.linkedin.com/company/intelligent-computing-solutions> >>>> <https://twitter.com/ICSIL> >>>> Midwest Internet Exchange <http://www.midwest-ix.com/> >>>> <https://www.facebook.com/mdwestix> >>>> <https://www.linkedin.com/company/midwest-internet-exchange> >>>> <https://twitter.com/mdwestix> >>>> The Brothers WISP <http://www.thebrotherswisp.com/> >>>> <https://www.facebook.com/thebrotherswisp> >>>> >>>> >>>> <https://www.youtube.com/channel/UCXSdfxQv7SpoRQYNyLwntZg> >>>> ------------------------------ >>>> *From: *"Mathew Howard" <[email protected]> >>>> *To: *"af" <[email protected]> >>>> *Sent: *Tuesday, April 18, 2017 4:20:23 PM >>>> *Subject: *Re: [AFMUG] ePMP v3.3 >>>> >>>> I've been slowly upgrading everything to 3.3, mostly because of the >>>> SNMP lockup thing in 3.2.2... and everything using Elevate is on 3.3, >>>> because they had some major fixes for UBNT XM radios, but I don't know that >>>> we have an ePMP stuff using DFS... if we do, it's off somewhere in a >>>> distant corner of the network that I haven't touched in months. >>>> >>>> If I remember right, there were some major DFS issues starting with >>>> 3.0, and I think it was mostly fixed by 3.2.... but since it didn't affect >>>> me much, I haven't paid too close of attention. >>>> >>>> On Tue, Apr 18, 2017 at 2:30 PM, Josh Luthman < >>>> [email protected]> wrote: >>>> >>>>> Anyone else miss the Mikrotik days where every single change was >>>>> instant? =( >>>>> >>>>> >>>>> Josh Luthman >>>>> Office: 937-552-2340 <(937)%20552-2340> >>>>> Direct: 937-552-2343 <(937)%20552-2343> >>>>> 1100 Wayne St >>>>> Suite 1337 >>>>> Troy, OH 45373 >>>>> >>>>> On Tue, Apr 18, 2017 at 2:52 PM, George Skorup < >>>>> [email protected]> wrote: >>>>> >>>>>> Yeah, I don't have much on 3.3 yet. One of the annoyances I've >>>>>> experienced so far is that ANY config change, something even as simple as >>>>>> enabling syslog web view, will cause a system-wide config reload which >>>>>> results in DFS having to go through CAC all over again, obviously on an >>>>>> AP >>>>>> running in DFS land anyway. This didn't happen with 3.2.2. I'm sure this >>>>>> had to be done probably for a number of reasons, but I'm positive that >>>>>> one >>>>>> of them was that I informed Cambium a few months ago that an old bug came >>>>>> back. It was possible (on 3.2.2) to make the GUI available on the NAT WAN >>>>>> interface even with the separate wireless management interface enabled >>>>>> after saving network config changes. The only fix was to reboot the SM. >>>>>> Now >>>>>> I take it that they're completely resetting drivers, interfaces and >>>>>> daemons >>>>>> upon save w/ 3.3. >>>>>> >>>>>> Anyway.. I haven't loaded 3.3 on any deployed gear running in DFS >>>>>> bands yet, mostly just bench stuff, so I can't say if more DFS issues >>>>>> have >>>>>> been positively resolved. I believe there were some notes about radar >>>>>> stuffs in 3.3 betas/RCs though. >>>>>> >>>>>> On 4/18/2017 11:44 AM, Mathew Howard wrote: >>>>>> >>>>>> I thought that had been fixed awhile back... but I can't even >>>>>> remember what the problem was, so I could be wrong. >>>>>> >>>>>> On Tue, Apr 18, 2017 at 10:50 AM, Josh Luthman < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Hasn't been any mention of it. I don't use it myself. >>>>>>> >>>>>>> >>>>>>> Josh Luthman >>>>>>> Office: 937-552-2340 <%28937%29%20552-2340> >>>>>>> Direct: 937-552-2343 <%28937%29%20552-2343> >>>>>>> 1100 Wayne St >>>>>>> Suite 1337 >>>>>>> Troy, OH 45373 >>>>>>> >>>>>>> On Tue, Apr 18, 2017 at 11:46 AM, Dan Petermann <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Did they get the DFS figured out yet? >>>>>>>> >>>>>>>> It seems to me there was a problem using the DFS bands, but I can’t >>>>>>>> seem to find what it was. >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>> >> >
