Re: [AFMUG] Client can't connect since UBNT 5.6.2 Firmware upgrade

[Justin Marshall]

Yeah, I would agree -89 is not good

One of the installers that used to work for us went ahead and installed this 
customer anyways, and they actually worked great for the last 2 ½ years...

From: Af [mailto:af-boun...@afmug.com] On Behalf Of Bill Prince
Sent: Wednesday, October 07, 2015 5:42 PM
To: af@afmug.com
Subject: Re: [AFMUG] Client can't connect since UBNT 5.6.2 Firmware upgrade

-89 is not a "usable" power level IMO.



bp

<part15sbs{at}gmail{dot}com>


On 10/7/2015 12:57 PM, Justin Marshall wrote:
Hi,
�
�
I recently updated a UBNT Rocket M5 to 5.6.2 from 5.5.4. Since this update, one 
of the clients will not connect.
�
This AP originally had 6 SM�s connected at 5490.� After the upgrade from 
5.5.4 to 5.6.2, 2 of the SM�s didn�t come back. �These 2 were not at the 
best signal (-86 and -89).� If I swapped frequencies to 5740 the 1 connected 
at -86 popped back up at an -88 and the other SM�s are ~-2 db.� But still 
no sign of the one that was at -89.
�
This led me to believe UBNT probably lowered the output power for DFS 
frequencies somewhere between 5.5.4 and 5.6.2�
�
One would think that downgrading the SM�s and AP back down to 5.5.4 would put 
things back the way they were but that doesn�t seem to be the case.
�
I even sent a tech onsite to swap out the unreachable SM with one that had 
5.5.4 on it.� He said the one with 5.5.4 and the one with 5.6.2 both see the 
AP at -89 under �Site survey� but won�t register to the AP.
�
I�m at a loss here� Does anyone have any suggestions of things to try, or a 
magic firmware version (folks on the UBNT forums say 5.5.4 is best for DFS 
frequencies) that might make this AP act the way it did prior to upgrading to 
5.6.2?
I�ve already tried every other 5 Ghz Frequency available (with a mix of 
different country codes), most with worse results.
�
Thanks,
Justin
just...@pdmnet.net<mailto:just...@pdmnet.net>
�

Re: [AFMUG] Client can't connect since UBNT 5.6.2 Firmware upgrade

[Eric Kuhnke]

  
  
Same here, -89 is effectively useless...  It'll also be dragging
down all of the other clients on the same sector by using up air
time (TDD) causing the radio to do QPSK 1/2 modulation.


On 10/7/15 1:11 PM, Jeremy wrote:

  I would not expect -86 and -89 to stay connected,
on any firmware.
  
On Wed, Oct 7, 2015 at 2:01 PM, Justin
  Marshall 
  wrote:
  

  
Sorry,
  
 
That
should have read:
This AP originally had 6 SM’s
  connected at 5690
 

  
From:
Af [mailto:af-boun...@afmug.com]
On Behalf Of Justin Marshall
Sent: Wednesday, October 07, 2015 3:57 PM
To: af@afmug.com
Subject: [AFMUG] Client can't connect
since UBNT 5.6.2 Firmware upgrade
  


   
  Hi,
   
   
  I recently updated a UBNT Rocket
M5 to 5.6.2 from 5.5.4. Since this update, one of
the clients will not connect.
   
  This AP originally had 6 SM’s
connected at 5490.  After the upgrade from 5.5.4 to
5.6.2, 2 of the SM’s didn’t come back.  These 2 were
not at the best signal (-86 and -89).  If I swapped
frequencies to 5740 the 1 connected at -86 popped
back up at an -88 and the other SM’s are ~-2 db. 
But still no sign of the one that was at -89.
   
  This led me to believe UBNT
probably lowered the output power for DFS
frequencies somewhere between 5.5.4 and 5.6.2…
   
  One would think that downgrading
the SM’s and AP back down to 5.5.4 would put things
back the way they were but that doesn’t seem to be
the case.
  
   
  I even sent a tech onsite to swap
out the unreachable SM with one that had 5.5.4 on
it.  He said the one with 5.5.4 and the one with
5.6.2 both see the AP at -89 under “Site survey” but
won’t register to the AP.
   
  I’m at a loss here… Does anyone
have any suggestions of things to try, or a magic
firmware version (folks on the UBNT forums say 5.5.4
is best for DFS frequencies) that might make this AP
act the way it did prior to upgrading to 5.6.2?
  I’ve already tried every other 5
Ghz Frequency available (with a mix of different
country codes), most with worse results.
   
  Thanks,
  Justin
  just...@pdmnet.net
   


  


  


  

Re: [AFMUG] Client can't connect since UBNT 5.6.2 Firmware upgrade

[Jaime Solorza]

They connect and pass data @ -90!!!  Just finished reconfiguring a SCADA
network and needed to make a change on another radio. On a hunch i changed
SSID and connected.   Saved me a trip to that well site.   These are all
Bullet M5s

Jaime Solorza
On Oct 7, 2015 2:11 PM, "Jeremy"  wrote:

> I would not expect -86 and -89 to stay connected, on any firmware.
>
> On Wed, Oct 7, 2015 at 2:01 PM, Justin Marshall 
> wrote:
>
>> Sorry,
>>
>>
>>
>> That should have read:
>>
>> This AP originally had 6 SM’s connected at *5690*
>>
>>
>>
>> *From:* Af [mailto:af-boun...@afmug.com] *On Behalf Of *Justin Marshall
>> *Sent:* Wednesday, October 07, 2015 3:57 PM
>> *To:* af@afmug.com
>> *Subject:* [AFMUG] Client can't connect since UBNT 5.6.2 Firmware upgrade
>>
>>
>>
>> Hi,
>>
>>
>>
>>
>>
>> I recently updated a UBNT Rocket M5 to 5.6.2 from 5.5.4. Since this
>> update, one of the clients will not connect.
>>
>>
>>
>> This AP originally had 6 SM’s connected at 5490.  After the upgrade from
>> 5.5.4 to 5.6.2, 2 of the SM’s didn’t come back.  These 2 were not at the
>> best signal (-86 and -89).  If I swapped frequencies to 5740 the 1
>> connected at -86 popped back up at an -88 and the other SM’s are ~-2 db.
>> But still no sign of the one that was at -89.
>>
>>
>>
>> This led me to believe UBNT probably lowered the output power for DFS
>> frequencies somewhere between 5.5.4 and 5.6.2…
>>
>>
>>
>> One would think that downgrading the SM’s and AP back down to 5.5.4 would
>> put things back the way they were but that doesn’t seem to be the case.
>>
>>
>>
>> I even sent a tech onsite to swap out the unreachable SM with one that
>> had 5.5.4 on it.  He said the one with 5.5.4 and the one with 5.6.2 both
>> see the AP at -89 under “Site survey” but won’t register to the AP.
>>
>>
>>
>> I’m at a loss here… Does anyone have any suggestions of things to try, or
>> a magic firmware version (folks on the UBNT forums say 5.5.4 is best for
>> DFS frequencies) that might make this AP act the way it did prior to
>> upgrading to 5.6.2?
>>
>> I’ve already tried every other 5 Ghz Frequency available (with a mix of
>> different country codes), most with worse results.
>>
>>
>>
>> Thanks,
>>
>> Justin
>>
>> just...@pdmnet.net
>>
>>
>>
>
>

Re: [AFMUG] Client can't connect since UBNT 5.6.2 Firmware upgrade

[Josh Luthman]

5.6.2 has no power changes.

Power changes came into play 5.6.3beta-something


Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373

On Wed, Oct 7, 2015 at 5:50 PM, Mathew Howard  wrote:

> If they were that weak, I'm guessing the clients weren't running at 30dbm
> EIRP. before v5.6.x, clients could run at full power regardless of whether
> it was legal in that particular band. So if, for example, we're talking
> about a NanoBridge M5-25, it could've been (and probably was) running at
> 23dbm Tx Power, but legally it can only run at 5dBm in the DFS band, so
> when you upgraded to 5.6.2 it forced it to the legal limit so you lost some
> 18db... if it was at -86, that's obviously not going to work.
>
> On Wed, Oct 7, 2015 at 4:41 PM, Bill Prince  wrote:
>
>> -89 is not a "usable" power level IMO.
>>
>> bp
>> 
>>
>>
>> On 10/7/2015 12:57 PM, Justin Marshall wrote:
>>
>> Hi,
>>
>> �
>>
>> �
>>
>> I recently updated a UBNT Rocket M5 to 5.6.2 from 5.5.4. Since this
>> update, one of the clients will not connect.
>>
>> �
>>
>> This AP originally had 6 SM�s connected at 5490.� After the upgrade
>> from 5.5.4 to 5.6.2, 2 of the SM�s didn�t come back. �These 2 were
>> not at the best signal (-86 and -89).� If I swapped frequencies to 5740
>> the 1 connected at -86 popped back up at an -88 and the other SM�s are
>> ~-2 db.� But still no sign of the one that was at -89.
>>
>> �
>>
>> This led me to believe UBNT probably lowered the output power for DFS
>> frequencies somewhere between 5.5.4 and 5.6.2�
>>
>> �
>>
>> One would think that downgrading the SM�s and AP back down to 5.5.4
>> would put things back the way they were but that doesn�t seem to be the
>> case.
>>
>> �
>>
>> I even sent a tech onsite to swap out the unreachable SM with one that
>> had 5.5.4 on it.� He said the one with 5.5.4 and the one with 5.6.2 both
>> see the AP at -89 under �Site survey� but won�t register to the AP.
>>
>> �
>>
>> I�m at a loss here� Does anyone have any suggestions of things to
>> try, or a magic firmware version (folks on the UBNT forums say 5.5.4 is
>> best for DFS frequencies) that might make this AP act the way it did prior
>> to upgrading to 5.6.2?
>>
>> I�ve already tried every other 5 Ghz Frequency available (with a mix of
>> different country codes), most with worse results.
>>
>> �
>>
>> Thanks,
>>
>> Justin
>>
>> just...@pdmnet.net
>>
>> �
>>
>>
>>
>

Re: [AFMUG] Client can't connect since UBNT 5.6.2 Firmware upgrade

[Justin Marshall]

Sorry,

That should have read:
This AP originally had 6 SM's connected at 5690

From: Af [mailto:af-boun...@afmug.com] On Behalf Of Justin Marshall
Sent: Wednesday, October 07, 2015 3:57 PM
To: af@afmug.com
Subject: [AFMUG] Client can't connect since UBNT 5.6.2 Firmware upgrade

Hi,


I recently updated a UBNT Rocket M5 to 5.6.2 from 5.5.4. Since this update, one 
of the clients will not connect.

This AP originally had 6 SM's connected at 5490.  After the upgrade from 5.5.4 
to 5.6.2, 2 of the SM's didn't come back.  These 2 were not at the best signal 
(-86 and -89).  If I swapped frequencies to 5740 the 1 connected at -86 popped 
back up at an -88 and the other SM's are ~-2 db.  But still no sign of the one 
that was at -89.

This led me to believe UBNT probably lowered the output power for DFS 
frequencies somewhere between 5.5.4 and 5.6.2...

One would think that downgrading the SM's and AP back down to 5.5.4 would put 
things back the way they were but that doesn't seem to be the case.

I even sent a tech onsite to swap out the unreachable SM with one that had 
5.5.4 on it.  He said the one with 5.5.4 and the one with 5.6.2 both see the AP 
at -89 under "Site survey" but won't register to the AP.

I'm at a loss here... Does anyone have any suggestions of things to try, or a 
magic firmware version (folks on the UBNT forums say 5.5.4 is best for DFS 
frequencies) that might make this AP act the way it did prior to upgrading to 
5.6.2?
I've already tried every other 5 Ghz Frequency available (with a mix of 
different country codes), most with worse results.

Thanks,
Justin
just...@pdmnet.net

Re: [AFMUG] Client can't connect since UBNT 5.6.2 Firmware upgrade

[Jeremy]

I would not expect -86 and -89 to stay connected, on any firmware.

On Wed, Oct 7, 2015 at 2:01 PM, Justin Marshall  wrote:

> Sorry,
>
>
>
> That should have read:
>
> This AP originally had 6 SM’s connected at *5690*
>
>
>
> *From:* Af [mailto:af-boun...@afmug.com] *On Behalf Of *Justin Marshall
> *Sent:* Wednesday, October 07, 2015 3:57 PM
> *To:* af@afmug.com
> *Subject:* [AFMUG] Client can't connect since UBNT 5.6.2 Firmware upgrade
>
>
>
> Hi,
>
>
>
>
>
> I recently updated a UBNT Rocket M5 to 5.6.2 from 5.5.4. Since this
> update, one of the clients will not connect.
>
>
>
> This AP originally had 6 SM’s connected at 5490.  After the upgrade from
> 5.5.4 to 5.6.2, 2 of the SM’s didn’t come back.  These 2 were not at the
> best signal (-86 and -89).  If I swapped frequencies to 5740 the 1
> connected at -86 popped back up at an -88 and the other SM’s are ~-2 db.
> But still no sign of the one that was at -89.
>
>
>
> This led me to believe UBNT probably lowered the output power for DFS
> frequencies somewhere between 5.5.4 and 5.6.2…
>
>
>
> One would think that downgrading the SM’s and AP back down to 5.5.4 would
> put things back the way they were but that doesn’t seem to be the case.
>
>
>
> I even sent a tech onsite to swap out the unreachable SM with one that had
> 5.5.4 on it.  He said the one with 5.5.4 and the one with 5.6.2 both see
> the AP at -89 under “Site survey” but won’t register to the AP.
>
>
>
> I’m at a loss here… Does anyone have any suggestions of things to try, or
> a magic firmware version (folks on the UBNT forums say 5.5.4 is best for
> DFS frequencies) that might make this AP act the way it did prior to
> upgrading to 5.6.2?
>
> I’ve already tried every other 5 Ghz Frequency available (with a mix of
> different country codes), most with worse results.
>
>
>
> Thanks,
>
> Justin
>
> just...@pdmnet.net
>
>
>

Re: [AFMUG] Client can't connect since UBNT 5.6.2 Firmware upgrade

[Bill Prince]

-89 is not a "usable" power level IMO.

bp


On 10/7/2015 12:57 PM, Justin Marshall wrote:


Hi,

I recently updated a UBNT Rocket M5 to 5.6.2 from 5.5.4. Since this 
update, one of the clients will not connect.


This AP originally had 6 SM�s connected at 5490.  After the upgrade 
from 5.5.4 to 5.6.2, 2 of the SM�s didn�t come back.  These 2 were not 
at the best signal (-86 and -89).  If I swapped frequencies to 5740 
the 1 connected at -86 popped back up at an -88 and the other SM�s are 
~-2 db. But still no sign of the one that was at -89.


This led me to believe UBNT probably lowered the output power for DFS 
frequencies somewhere between 5.5.4 and 5.6.2�


One would think that downgrading the SM�s and AP back down to 5.5.4 
would put things back the way they were but that doesn�t seem to be 
the case.


I even sent a tech onsite to swap out the unreachable SM with one that 
had 5.5.4 on it.  He said the one with 5.5.4 and the one with 5.6.2 
both see the AP at -89 under �Site survey� but won�t register to the AP.


I�m at a loss here� Does anyone have any suggestions of things to try, 
or a magic firmware version (folks on the UBNT forums say 5.5.4 is 
best for DFS frequencies) that might make this AP act the way it did 
prior to upgrading to 5.6.2?


I�ve already tried every other 5 Ghz Frequency available (with a mix 
of different country codes), most with worse results.


Thanks,

Justin

just...@pdmnet.net 

Re: [AFMUG] Client can't connect since UBNT 5.6.2 Firmware upgrade

[Ryan Ray]

Cut down some trees


On Wed, Oct 7, 2015 at 2:41 PM, Bill Prince  wrote:

> -89 is not a "usable" power level IMO.
>
> bp
> 
>
>
> On 10/7/2015 12:57 PM, Justin Marshall wrote:
>
> Hi,
>
> �
>
> �
>
> I recently updated a UBNT Rocket M5 to 5.6.2 from 5.5.4. Since this
> update, one of the clients will not connect.
>
> �
>
> This AP originally had 6 SM�s connected at 5490.� After the upgrade
> from 5.5.4 to 5.6.2, 2 of the SM�s didn�t come back. �These 2 were
> not at the best signal (-86 and -89).� If I swapped frequencies to 5740
> the 1 connected at -86 popped back up at an -88 and the other SM�s are
> ~-2 db.� But still no sign of the one that was at -89.
>
> �
>
> This led me to believe UBNT probably lowered the output power for DFS
> frequencies somewhere between 5.5.4 and 5.6.2�
>
> �
>
> One would think that downgrading the SM�s and AP back down to 5.5.4
> would put things back the way they were but that doesn�t seem to be the
> case.
>
> �
>
> I even sent a tech onsite to swap out the unreachable SM with one that had
> 5.5.4 on it.� He said the one with 5.5.4 and the one with 5.6.2 both see
> the AP at -89 under �Site survey� but won�t register to the AP.
>
> �
>
> I�m at a loss here� Does anyone have any suggestions of things to try,
> or a magic firmware version (folks on the UBNT forums say 5.5.4 is best for
> DFS frequencies) that might make this AP act the way it did prior to
> upgrading to 5.6.2?
>
> I�ve already tried every other 5 Ghz Frequency available (with a mix of
> different country codes), most with worse results.
>
> �
>
> Thanks,
>
> Justin
>
> just...@pdmnet.net
>
> �
>
>
>

Re: [AFMUG] Client can't connect since UBNT 5.6.2 Firmware upgrade

[Glen Waldrop]

Yep.

That is marginal at best.

I've found MT *much* more stable beyond -83 than UBNT hardware by far. UBNT 
forums seems to support that as well. The majority flog you for a signal worse 
than -70. I have a lot of full speed MT links at -79.

UBNT seems to need -70s to be stable. You were living on the edge.


  - Original Message - 
  From: Jeremy 
  To: af@afmug.com 
  Sent: Wednesday, October 07, 2015 3:11 PM
  Subject: Re: [AFMUG] Client can't connect since UBNT 5.6.2 Firmware upgrade


  I would not expect -86 and -89 to stay connected, on any firmware.


  On Wed, Oct 7, 2015 at 2:01 PM, Justin Marshall <just...@pdmnet.net> wrote:

Sorry, 



That should have read:

This AP originally had 6 SM’s connected at 5690



From: Af [mailto:af-boun...@afmug.com] On Behalf Of Justin Marshall
Sent: Wednesday, October 07, 2015 3:57 PM
To: af@afmug.com
Subject: [AFMUG] Client can't connect since UBNT 5.6.2 Firmware upgrade



Hi,





I recently updated a UBNT Rocket M5 to 5.6.2 from 5.5.4. Since this update, 
one of the clients will not connect.



This AP originally had 6 SM’s connected at 5490.  After the upgrade from 
5.5.4 to 5.6.2, 2 of the SM’s didn’t come back.  These 2 were not at the best 
signal (-86 and -89).  If I swapped frequencies to 5740 the 1 connected at -86 
popped back up at an -88 and the other SM’s are ~-2 db.  But still no sign of 
the one that was at -89.



This led me to believe UBNT probably lowered the output power for DFS 
frequencies somewhere between 5.5.4 and 5.6.2…



One would think that downgrading the SM’s and AP back down to 5.5.4 would 
put things back the way they were but that doesn’t seem to be the case. 



I even sent a tech onsite to swap out the unreachable SM with one that had 
5.5.4 on it.  He said the one with 5.5.4 and the one with 5.6.2 both see the AP 
at -89 under “Site survey” but won’t register to the AP.



I’m at a loss here… Does anyone have any suggestions of things to try, or a 
magic firmware version (folks on the UBNT forums say 5.5.4 is best for DFS 
frequencies) that might make this AP act the way it did prior to upgrading to 
5.6.2?

I’ve already tried every other 5 Ghz Frequency available (with a mix of 
different country codes), most with worse results.



Thanks,

Justin

just...@pdmnet.net

Re: [AFMUG] Client can't connect since UBNT 5.6.2 Firmware upgrade

[Mike Hammett]

Even at several dB more than that. 




- 
Mike Hammett 
Intelligent Computing Solutions 
http://www.ics-il.com 

- Original Message -

From: "Jeremy" <jeremysmi...@gmail.com> 
To: af@afmug.com 
Sent: Wednesday, October 7, 2015 3:11:02 PM 
Subject: Re: [AFMUG] Client can't connect since UBNT 5.6.2 Firmware upgrade 


I would not expect -86 and -89 to stay connected, on any firmware. 


On Wed, Oct 7, 2015 at 2:01 PM, Justin Marshall < just...@pdmnet.net > wrote: 





Sorry, 

That should have read: 
This AP originally had 6 SM’s connected at 5690 



From: Af [mailto: af-boun...@afmug.com ] On Behalf Of Justin Marshall 
Sent: Wednesday, October 07, 2015 3:57 PM 
To: af@afmug.com 
Subject: [AFMUG] Client can't connect since UBNT 5.6.2 Firmware upgrade 

Hi, 


I recently updated a UBNT Rocket M5 to 5.6.2 from 5.5.4. Since this update, one 
of the clients will not connect. 

This AP originally had 6 SM’s connected at 5490. After the upgrade from 5.5.4 
to 5.6.2, 2 of the SM’s didn’t come back. These 2 were not at the best signal 
(-86 and -89). If I swapped frequencies to 5740 the 1 connected at -86 popped 
back up at an -88 and the other SM’s are ~-2 db. But still no sign of the one 
that was at -89. 

This led me to believe UBNT probably lowered the output power for DFS 
frequencies somewhere between 5.5.4 and 5.6.2… 

One would think that downgrading the SM’s and AP back down to 5.5.4 would put 
things back the way they were but that doesn’t seem to be the case. 

I even sent a tech onsite to swap out the unreachable SM with one that had 
5.5.4 on it. He said the one with 5.5.4 and the one with 5.6.2 both see the AP 
at -89 under “Site survey” but won’t register to the AP. 

I’m at a loss here… Does anyone have any suggestions of things to try, or a 
magic firmware version (folks on the UBNT forums say 5.5.4 is best for DFS 
frequencies) that might make this AP act the way it did prior to upgrading to 
5.6.2? 
I’ve already tried every other 5 Ghz Frequency available (with a mix of 
different country codes), most with worse results. 

Thanks, 
Justin 
just...@pdmnet.net 

Re: [AFMUG] Client can't connect since UBNT 5.6.2 Firmware upgrade

[Mathew Howard]

If they were that weak, I'm guessing the clients weren't running at 30dbm
EIRP. before v5.6.x, clients could run at full power regardless of whether
it was legal in that particular band. So if, for example, we're talking
about a NanoBridge M5-25, it could've been (and probably was) running at
23dbm Tx Power, but legally it can only run at 5dBm in the DFS band, so
when you upgraded to 5.6.2 it forced it to the legal limit so you lost some
18db... if it was at -86, that's obviously not going to work.

On Wed, Oct 7, 2015 at 4:41 PM, Bill Prince  wrote:

> -89 is not a "usable" power level IMO.
>
> bp
> 
>
>
> On 10/7/2015 12:57 PM, Justin Marshall wrote:
>
> Hi,
>
> �
>
> �
>
> I recently updated a UBNT Rocket M5 to 5.6.2 from 5.5.4. Since this
> update, one of the clients will not connect.
>
> �
>
> This AP originally had 6 SM�s connected at 5490.� After the upgrade
> from 5.5.4 to 5.6.2, 2 of the SM�s didn�t come back. �These 2 were
> not at the best signal (-86 and -89).� If I swapped frequencies to 5740
> the 1 connected at -86 popped back up at an -88 and the other SM�s are
> ~-2 db.� But still no sign of the one that was at -89.
>
> �
>
> This led me to believe UBNT probably lowered the output power for DFS
> frequencies somewhere between 5.5.4 and 5.6.2�
>
> �
>
> One would think that downgrading the SM�s and AP back down to 5.5.4
> would put things back the way they were but that doesn�t seem to be the
> case.
>
> �
>
> I even sent a tech onsite to swap out the unreachable SM with one that had
> 5.5.4 on it.� He said the one with 5.5.4 and the one with 5.6.2 both see
> the AP at -89 under �Site survey� but won�t register to the AP.
>
> �
>
> I�m at a loss here� Does anyone have any suggestions of things to try,
> or a magic firmware version (folks on the UBNT forums say 5.5.4 is best for
> DFS frequencies) that might make this AP act the way it did prior to
> upgrading to 5.6.2?
>
> I�ve already tried every other 5 Ghz Frequency available (with a mix of
> different country codes), most with worse results.
>
> �
>
> Thanks,
>
> Justin
>
> just...@pdmnet.net
>
> �
>
>
>

Re: [AFMUG] Client can't connect since UBNT 5.6.2 Firmware upgrade

[That One Guy /sarcasm]

they removed some of the encryption modes

On Wed, Oct 7, 2015 at 2:57 PM, Justin Marshall  wrote:

> Hi,
>
>
>
>
>
> I recently updated a UBNT Rocket M5 to 5.6.2 from 5.5.4. Since this
> update, one of the clients will not connect.
>
>
>
> This AP originally had 6 SM’s connected at 5490.  After the upgrade from
> 5.5.4 to 5.6.2, 2 of the SM’s didn’t come back.  These 2 were not at the
> best signal (-86 and -89).  If I swapped frequencies to 5740 the 1
> connected at -86 popped back up at an -88 and the other SM’s are ~-2 db.
> But still no sign of the one that was at -89.
>
>
>
> This led me to believe UBNT probably lowered the output power for DFS
> frequencies somewhere between 5.5.4 and 5.6.2…
>
>
>
> One would think that downgrading the SM’s and AP back down to 5.5.4 would
> put things back the way they were but that doesn’t seem to be the case.
>
>
>
> I even sent a tech onsite to swap out the unreachable SM with one that had
> 5.5.4 on it.  He said the one with 5.5.4 and the one with 5.6.2 both see
> the AP at -89 under “Site survey” but won’t register to the AP.
>
>
>
> I’m at a loss here… Does anyone have any suggestions of things to try, or
> a magic firmware version (folks on the UBNT forums say 5.5.4 is best for
> DFS frequencies) that might make this AP act the way it did prior to
> upgrading to 5.6.2?
>
> I’ve already tried every other 5 Ghz Frequency available (with a mix of
> different country codes), most with worse results.
>
>
>
> Thanks,
>
> Justin
>
> just...@pdmnet.net
>
>
>



-- 
If you only see yourself as part of the team but you don't see your team as
part of yourself you have already failed as part of the team.

Re: [AFMUG] Client can't connect since UBNT 5.6.2 Firmware upgrade

[Mathew Howard]

Not power changes, but it does automatically limit the clients to 30dbm
EIRP on DFS channels now... in 5.5.x, clients just ran full blast if you
didn't manually set it.

On Wed, Oct 7, 2015 at 4:53 PM, Josh Luthman 
wrote:

> 5.6.2 has no power changes.
>
> Power changes came into play 5.6.3beta-something
>
>
> Josh Luthman
> Office: 937-552-2340
> Direct: 937-552-2343
> 1100 Wayne St
> Suite 1337
> Troy, OH 45373
>
> On Wed, Oct 7, 2015 at 5:50 PM, Mathew Howard 
> wrote:
>
>> If they were that weak, I'm guessing the clients weren't running at 30dbm
>> EIRP. before v5.6.x, clients could run at full power regardless of whether
>> it was legal in that particular band. So if, for example, we're talking
>> about a NanoBridge M5-25, it could've been (and probably was) running at
>> 23dbm Tx Power, but legally it can only run at 5dBm in the DFS band, so
>> when you upgraded to 5.6.2 it forced it to the legal limit so you lost some
>> 18db... if it was at -86, that's obviously not going to work.
>>
>> On Wed, Oct 7, 2015 at 4:41 PM, Bill Prince  wrote:
>>
>>> -89 is not a "usable" power level IMO.
>>>
>>> bp
>>> 
>>>
>>>
>>> On 10/7/2015 12:57 PM, Justin Marshall wrote:
>>>
>>> Hi,
>>>
>>> �
>>>
>>> �
>>>
>>> I recently updated a UBNT Rocket M5 to 5.6.2 from 5.5.4. Since this
>>> update, one of the clients will not connect.
>>>
>>> �
>>>
>>> This AP originally had 6 SM�s connected at 5490.� After the upgrade
>>> from 5.5.4 to 5.6.2, 2 of the SM�s didn�t come back. �These 2 were
>>> not at the best signal (-86 and -89).� If I swapped frequencies to 5740
>>> the 1 connected at -86 popped back up at an -88 and the other SM�s are
>>> ~-2 db.� But still no sign of the one that was at -89.
>>>
>>> �
>>>
>>> This led me to believe UBNT probably lowered the output power for DFS
>>> frequencies somewhere between 5.5.4 and 5.6.2�
>>>
>>> �
>>>
>>> One would think that downgrading the SM�s and AP back down to 5.5.4
>>> would put things back the way they were but that doesn�t seem to be the
>>> case.
>>>
>>> �
>>>
>>> I even sent a tech onsite to swap out the unreachable SM with one that
>>> had 5.5.4 on it.� He said the one with 5.5.4 and the one with 5.6.2 both
>>> see the AP at -89 under �Site survey� but won�t register to the AP.
>>>
>>> �
>>>
>>> I�m at a loss here� Does anyone have any suggestions of things to
>>> try, or a magic firmware version (folks on the UBNT forums say 5.5.4 is
>>> best for DFS frequencies) that might make this AP act the way it did prior
>>> to upgrading to 5.6.2?
>>>
>>> I�ve already tried every other 5 Ghz Frequency available (with a mix
>>> of different country codes), most with worse results.
>>>
>>> �
>>>
>>> Thanks,
>>>
>>> Justin
>>>
>>> just...@pdmnet.net
>>>
>>> �
>>>
>>>
>>>
>>
>