Still don't know what breaks with 6.06.
Jan V
On 07/10/2017 09:34 PM, Jan-OOLLC wrote:
Do we know for sure it's a legal brick? Why would a vendor break
their own hardware by killing it and prevent another vendor firmware
from installing on it? This sounds more like a malware issue to me.
Sure am glad i don't automatically update. Can I get a confirmation
on this question?
Jan V
On 07/10/2017 07:34 PM, Shawn C. Peppers wrote:
Mikrotik 2011LS v6.39.2 and a mikrotik ccr1009-8g-1s-1s+ v6.39.2
Shawn C. Peppers
Video Direct
866-680-8433 Toll Free
http://www.video-direct.tv
On Jul 10, 2017, at 8:56 PM, James Craig <[email protected]
<mailto:[email protected]>> wrote:
Shawn: Just checked and I haven't seen any similar bug reports.
Can you forward me the AP and STA .sup ([email protected]
<mailto:[email protected]>) and I'll take a look?
What are you using for routers?
On Mon, Jul 10, 2017 at 9:46 PM, Shawn C. Peppers
<[email protected]
<mailto:[email protected]>> wrote:
It seems as though it may be breaking ospf....is anyone else
experiencing this? I sent this the other day....
Im not sure of its bug but i did just have a odd issue where i
have a AP running mixed mode 8.3 and when i updated a XM station
to 6.06 the ospf was stuck in exchange state. I had to change
the ospf from point to point to broadcast which fixed the issue.
I can not actually say for certain this is an issue with the
ubnt station or AP.
Shawn C. Peppers
Video Direct
866-680-8433 <tel:%28866%29%20680-8433> Toll Free
http://www.video-direct.tv
On Jul 10, 2017, at 8:34 PM, James Craig via Ubnt_users
<[email protected] <mailto:[email protected]>> wrote:
Hi Guys,
We implemented FW signing to improve device security as a
result of THIS
<https://community.ubnt.com/t5/airMAX-General-Discussion/6-0-3-High-CPU-usage/td-p/1895878>
report (and a few others). This malware would masquerade as
6.0.3, but in reality, it was based on the 5.5.2 SDK.
Regulatory requirements are another factor, but device security
is the major driving factor here.
Forbes: I haven't seen any other reports of radios bricking,
sending you a note for more info
On Mon, Jul 10, 2017 at 3:51 PM, Robert
<[email protected] <mailto:[email protected]>> wrote:
When you can't compete technically, you compete legally...
Shortly
thereafter you wonder why your foot has a hole in it...
On 07/10/2017 12:45 PM, Forbes Mercy wrote:
> It seems that this upgrade isn't an upgrade at all. It's
driven by
> lawyers requiring that you do an electronic signature
that you agree to
> not use Cambium Elevate software on this device. Pretty
odd since it's
> my radio, well past warranty so I can do what I want to
it. Is this the
> direction UBNT is going, turn your radio into a brick if
you don't
> modify your use agreement with them? Well Robert DID
come from Apple so
> I guess I shouldn't be surprised about sabotaging product
to force you
> into newer gear, guess 6.04 is the last update I'll do
for my radios,
> sad. #patheticdirection
>
> Forbes Mercy
>
>
>
> _______________________________________________
> Ubnt_users mailing list
> [email protected] <mailto:[email protected]>
> http://lists.wispa.org/mailman/listinfo/ubnt_users
<http://lists.wispa.org/mailman/listinfo/ubnt_users>
>
_______________________________________________
Ubnt_users mailing list
[email protected] <mailto:[email protected]>
http://lists.wispa.org/mailman/listinfo/ubnt_users
<http://lists.wispa.org/mailman/listinfo/ubnt_users>
_______________________________________________
Ubnt_users mailing list
[email protected] <mailto:[email protected]>
http://lists.wispa.org/mailman/listinfo/ubnt_users
<http://lists.wispa.org/mailman/listinfo/ubnt_users>
_______________________________________________
Ubnt_users mailing list
[email protected]
http://lists.wispa.org/mailman/listinfo/ubnt_users
_______________________________________________
Ubnt_users mailing list
[email protected]
http://lists.wispa.org/mailman/listinfo/ubnt_users
_______________________________________________
Ubnt_users mailing list
[email protected]
http://lists.wispa.org/mailman/listinfo/ubnt_users
