I heard a lot of bad stuff about Elevate and XM radios. Is that more better now?
----- Mike Hammett Intelligent Computing Solutions Midwest Internet Exchange The Brothers WISP ----- Original Message ----- 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 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Tue, Apr 18, 2017 at 2:52 PM, George Skorup < [email protected] > wrote: <blockquote> 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: <blockquote> 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: <blockquote> Hasn't been any mention of it. I don't use it myself. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Tue, Apr 18, 2017 at 11:46 AM, Dan Petermann < [email protected] > wrote: <blockquote> 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. </blockquote> </blockquote> </blockquote> </blockquote>
