Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[RickG]

Thanks Gents!

On Sat, Nov 18, 2017 at 9:51 PM, Tommy Adams <tomm...@digitex.net> wrote:

> We have moved several Mikrotik 2.4 towers to the ePMP 2.4 and see huge
> increases in performance. The stuff just works. We will be elevating our
> remaining 2.4 UBNT gear very soon.
>
>
> 
> Tommy A.
> Digitex.com
>
> 817.558.6230 V
> 817.558.1204 F
>
> On Nov 18, 2017, at 7:11 PM, David Jones <d...@nglconnection.com> wrote:
>
> It's an ePMP 1000 2ghz with sync connected to a ubnt 2ghz sector. We
> elevated the people connect to the old rocket and swapped the Rocket with
> the ePMP. Signals were about the same maybe a bit less but performance was
> greatly increased.
>
> On Nov 18, 2017 12:55 PM, "RickG" <rgunder...@gmail.com> wrote:
>
> David, What AP did you use for the NS2's?
>
> On Sat, Nov 18, 2017 at 12:46 PM, David Jones <d...@nglconnection.com>
> wrote:
>
>> That was a 5ghz. I have elevated some NS2's. Here is a NS2 with a
>> reflector dish at 14.8 miles getting about 62mbps down. I am really
>> impressed with what I can now get from the 2ghz.
>>
>> On Fri, Nov 17, 2017 at 7:18 PM, RickG <rgunder...@gmail.com> wrote:
>>
>>> Ha-vent had any issues with the Rocket Prism 5GHz but the "XM" firmware
>>> 2.4GHz CPE not so much ;(
>>>
>>> On Fri, Nov 17, 2017 at 6:33 PM, David Jones <d...@nglconnection.com>
>>> wrote:
>>>
>>>> We tried an AC with MM sync And the performance is worse than just
>>>> mixed mode. It may have to do with the clients that have poor signal. With
>>>> an elevated XM I can pull 70mbps at a -73 signal with 60 other people
>>>> connected to the AP on a 40mhz channel. with a - 64 signal I can pull
>>>> 94mbps maxing out the 100mbps port. an XW on the same sector can pull about
>>>> 127mbps tcp throughput.
>>>> No matter what I tried with UBNT I could not get my legacy devices to
>>>> pull more than 40mbps TCP on a sector with more than 35 devices connected.
>>>> sure its udp test showed 85mbps+ but the TCP was barely half that. With the
>>>> cambium tests the TCP is usually within 5% of it.
>>>>
>>>> We have also had problems with random UDP packets going missing and it
>>>> causes problems with VOIP and gamers. its not the connection quality
>>>> because we can use a VPN and magically the udp didn't disappear. adding the
>>>> latency and overhead improved the VOIP and UDP based games.
>>>>
>>>> Going Forward we may have places that pure AC may work well but for any
>>>> of the old M equipment nothing beats an ePMP2000 with elevated firmware.
>>>>
>>>> On Fri, Nov 17, 2017 at 1:38 PM, J Portman <ba...@baron.com> wrote:
>>>>
>>>>> Just as a data point, we upgraded one of our towers to run sync in
>>>>> mixed mode a few weeks ago and it has performed flawlessly.
>>>>>
>>>>> We are getting ready to roll sync out to the entire network (60+ APS).
>>>>> I will report on our progress.
>>>>>
>>>>> YMMV,
>>>>> JP
>>>>>
>>>>>
>>>>> *On Fri, 17 Nov 2017 19:56:17 +, Rory Conaway wrote*
>>>>> > Understood.  With the [UTF-8?]Prism’s handling multi-mode, have
>>>>> you considered that option?
>>>>> >
>>>>> > Rory
>>>>> >
>>>>> > *From:* ubnt_users-boun...@wispa.org [mailto:ubnt_users-bounces@wis
>>>>> pa.org] *On Behalf Of *David Jones
>>>>> > *Sent:* Friday, November 17, 2017 12:21 PM
>>>>> > *To:* Ubiquiti Users Group <ubnt_users@wispa.org>
>>>>> > *Subject:* Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
>>>>> >
>>>>> >
>>>>> > Well for us it is because we are elevating our units. I also hate
>>>>> the locked firmware at and after 6.0.6
>>>>> >
>>>>> >
>>>>> >
>>>>> > On Fri, Nov 17, 2017 at 10:21 AM, Rory Conaway <
>>>>> r...@triadwireless.net> wrote:
>>>>>
>>>>>
>>>>> >
>>>>> > Why are you still running 6.0.4?
>>>>> >
>>>>> > Rory
>>>>> >
>>>>> >
>>>>> > *From:* ubnt_users-boun...@wispa.org [mailto:ubnt_users-bounces@wis
>&

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[Tommy Adams]

We have moved several Mikrotik 2.4 towers to the ePMP 2.4 and see huge 
increases in performance. The stuff just works. We will be elevating our 
remaining 2.4 UBNT gear very soon. 



Tommy A.
Digitex.com

817.558.6230 V
817.558.1204 F

> On Nov 18, 2017, at 7:11 PM, David Jones <d...@nglconnection.com> wrote:
> 
> It's an ePMP 1000 2ghz with sync connected to a ubnt 2ghz sector. We elevated 
> the people connect to the old rocket and swapped the Rocket with the ePMP. 
> Signals were about the same maybe a bit less but performance was greatly 
> increased.
> 
> On Nov 18, 2017 12:55 PM, "RickG" <rgunder...@gmail.com> wrote:
> David, What AP did you use for the NS2's?
> 
> On Sat, Nov 18, 2017 at 12:46 PM, David Jones <d...@nglconnection.com> wrote:
>> That was a 5ghz. I have elevated some NS2's. Here is a NS2 with a reflector 
>> dish at 14.8 miles getting about 62mbps down. I am really impressed with 
>> what I can now get from the 2ghz.
>> 
>>> On Fri, Nov 17, 2017 at 7:18 PM, RickG <rgunder...@gmail.com> wrote:
>>> Ha-vent had any issues with the Rocket Prism 5GHz but the "XM" firmware 
>>> 2.4GHz CPE not so much ;(
>>> 
>>>> On Fri, Nov 17, 2017 at 6:33 PM, David Jones <d...@nglconnection.com> 
>>>> wrote:
>>> 
>>>> We tried an AC with MM sync And the performance is worse than just mixed 
>>>> mode. It may have to do with the clients that have poor signal. With an 
>>>> elevated XM I can pull 70mbps at a -73 signal with 60 other people 
>>>> connected to the AP on a 40mhz channel. with a - 64 signal I can pull 
>>>> 94mbps maxing out the 100mbps port. an XW on the same sector can pull 
>>>> about 127mbps tcp throughput.
>>>> No matter what I tried with UBNT I could not get my legacy devices to pull 
>>>> more than 40mbps TCP on a sector with more than 35 devices connected. sure 
>>>> its udp test showed 85mbps+ but the TCP was barely half that. With the 
>>>> cambium tests the TCP is usually within 5% of it.
>>>> 
>>>> We have also had problems with random UDP packets going missing and it 
>>>> causes problems with VOIP and gamers. its not the connection quality 
>>>> because we can use a VPN and magically the udp didn't disappear. adding 
>>>> the latency and overhead improved the VOIP and UDP based games.
>>>> 
>>>> Going Forward we may have places that pure AC may work well but for any of 
>>>> the old M equipment nothing beats an ePMP2000 with elevated firmware.
>>>> 
>>>>> On Fri, Nov 17, 2017 at 1:38 PM, J Portman <ba...@baron.com> wrote:
>>>>> Just as a data point, we upgraded one of our towers to run sync in mixed 
>>>>> mode a few weeks ago and it has performed flawlessly. 
>>>>> 
>>>>> We are getting ready to roll sync out to the entire network (60+ APS). I 
>>>>> will report on our progress. 
>>>>> 
>>>>> YMMV, 
>>>>> JP 
>>>>> 
>>>>> 
>>>>> On Fri, 17 Nov 2017 19:56:17 +, Rory Conaway wrote 
>>>>> > Understood.  With the [UTF-8?]Prism’s handling multi-mode, have you 
>>>>> > considered that option? 
>>>>> >   
>>>>> > Rory 
>>>>> >   
>>>>> > From: ubnt_users-boun...@wispa.org 
>>>>> > [mailto:ubnt_users-boun...@wispa.org] On Behalf Of David Jones 
>>>>> > Sent: Friday, November 17, 2017 12:21 PM 
>>>>> > To: Ubiquiti Users Group <ubnt_users@wispa.org> 
>>>>> > Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices 
>>>>> >   
>>>>> > 
>>>>> > Well for us it is because we are elevating our units. I also hate the 
>>>>> > locked firmware at and after 6.0.6 
>>>>> > 
>>>>> >   
>>>>> > 
>>>>> > On Fri, Nov 17, 2017 at 10:21 AM, Rory Conaway <r...@triadwireless.net> 
>>>>> > wrote:
>>>>> 
>>>>> > 
>>>>> > Why are you still running 6.0.4? 
>>>>> >   
>>>>> > Rory 
>>>>> >   
>>>>> > 
>>>>> > From: ubnt_users-boun...@wispa.org 
>>>>> > [mailto:ubnt_users-boun...@wispa.org] On Behalf Of Troy Gibson, 
>>>>> > Byhalia.net,LLC 
>>>>

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[David Jones]

It's an ePMP 1000 2ghz with sync connected to a ubnt 2ghz sector. We
elevated the people connect to the old rocket and swapped the Rocket with
the ePMP. Signals were about the same maybe a bit less but performance was
greatly increased.

On Nov 18, 2017 12:55 PM, "RickG" <rgunder...@gmail.com> wrote:

David, What AP did you use for the NS2's?

On Sat, Nov 18, 2017 at 12:46 PM, David Jones <d...@nglconnection.com>
wrote:

> That was a 5ghz. I have elevated some NS2's. Here is a NS2 with a
> reflector dish at 14.8 miles getting about 62mbps down. I am really
> impressed with what I can now get from the 2ghz.
>
> On Fri, Nov 17, 2017 at 7:18 PM, RickG <rgunder...@gmail.com> wrote:
>
>> Ha-vent had any issues with the Rocket Prism 5GHz but the "XM" firmware
>> 2.4GHz CPE not so much ;(
>>
>> On Fri, Nov 17, 2017 at 6:33 PM, David Jones <d...@nglconnection.com>
>> wrote:
>>
>>> We tried an AC with MM sync And the performance is worse than just mixed
>>> mode. It may have to do with the clients that have poor signal. With an
>>> elevated XM I can pull 70mbps at a -73 signal with 60 other people
>>> connected to the AP on a 40mhz channel. with a - 64 signal I can pull
>>> 94mbps maxing out the 100mbps port. an XW on the same sector can pull about
>>> 127mbps tcp throughput.
>>> No matter what I tried with UBNT I could not get my legacy devices to
>>> pull more than 40mbps TCP on a sector with more than 35 devices connected.
>>> sure its udp test showed 85mbps+ but the TCP was barely half that. With the
>>> cambium tests the TCP is usually within 5% of it.
>>>
>>> We have also had problems with random UDP packets going missing and it
>>> causes problems with VOIP and gamers. its not the connection quality
>>> because we can use a VPN and magically the udp didn't disappear. adding the
>>> latency and overhead improved the VOIP and UDP based games.
>>>
>>> Going Forward we may have places that pure AC may work well but for any
>>> of the old M equipment nothing beats an ePMP2000 with elevated firmware.
>>>
>>> On Fri, Nov 17, 2017 at 1:38 PM, J Portman <ba...@baron.com> wrote:
>>>
>>>> Just as a data point, we upgraded one of our towers to run sync in
>>>> mixed mode a few weeks ago and it has performed flawlessly.
>>>>
>>>> We are getting ready to roll sync out to the entire network (60+ APS).
>>>> I will report on our progress.
>>>>
>>>> YMMV,
>>>> JP
>>>>
>>>>
>>>> *On Fri, 17 Nov 2017 19:56:17 +0000, Rory Conaway wrote*
>>>> > Understood.  With the [UTF-8?]Prism’s handling multi-mode, have you
>>>> considered that option?
>>>> >
>>>> > Rory
>>>> >
>>>> > *From:* ubnt_users-boun...@wispa.org [mailto:ubnt_users-bounces@wis
>>>> pa.org] *On Behalf Of *David Jones
>>>> > *Sent:* Friday, November 17, 2017 12:21 PM
>>>> > *To:* Ubiquiti Users Group <ubnt_users@wispa.org>
>>>> > *Subject:* Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
>>>> >
>>>> >
>>>> > Well for us it is because we are elevating our units. I also hate the
>>>> locked firmware at and after 6.0.6
>>>> >
>>>> >
>>>> >
>>>> > On Fri, Nov 17, 2017 at 10:21 AM, Rory Conaway <
>>>> r...@triadwireless.net> wrote:
>>>>
>>>>
>>>> >
>>>> > Why are you still running 6.0.4?
>>>> >
>>>> > Rory
>>>> >
>>>> >
>>>> > *From:* ubnt_users-boun...@wispa.org [mailto:ubnt_users-bounces@wis
>>>> pa.org] *On Behalf Of *Troy Gibson, Byhalia.net,LLC
>>>> > *Sent:* Friday, November 17, 2017 5:31 AM
>>>> >
>>>> > *To:* Ubiquiti Users Group <ubnt_users@wispa.org>
>>>> > *Subject:* Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
>>>> >
>>>> >
>>>> >
>>>> > Beta 6 or 7 still does not find 6.0.4.  I have had to go through my
>>>> system to find missing CPE's or APs that were on 6.0.4  Downgraded to
>>>> 5.6.15 for them to be found as I was unsure of the higher 6.0 firmware at
>>>> the time.
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > Troy Gibs

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[RickG]

David, What AP did you use for the NS2's?

On Sat, Nov 18, 2017 at 12:46 PM, David Jones <d...@nglconnection.com>
wrote:

> That was a 5ghz. I have elevated some NS2's. Here is a NS2 with a
> reflector dish at 14.8 miles getting about 62mbps down. I am really
> impressed with what I can now get from the 2ghz.
>
> On Fri, Nov 17, 2017 at 7:18 PM, RickG <rgunder...@gmail.com> wrote:
>
>> Ha-vent had any issues with the Rocket Prism 5GHz but the "XM" firmware
>> 2.4GHz CPE not so much ;(
>>
>> On Fri, Nov 17, 2017 at 6:33 PM, David Jones <d...@nglconnection.com>
>> wrote:
>>
>>> We tried an AC with MM sync And the performance is worse than just mixed
>>> mode. It may have to do with the clients that have poor signal. With an
>>> elevated XM I can pull 70mbps at a -73 signal with 60 other people
>>> connected to the AP on a 40mhz channel. with a - 64 signal I can pull
>>> 94mbps maxing out the 100mbps port. an XW on the same sector can pull about
>>> 127mbps tcp throughput.
>>> No matter what I tried with UBNT I could not get my legacy devices to
>>> pull more than 40mbps TCP on a sector with more than 35 devices connected.
>>> sure its udp test showed 85mbps+ but the TCP was barely half that. With the
>>> cambium tests the TCP is usually within 5% of it.
>>>
>>> We have also had problems with random UDP packets going missing and it
>>> causes problems with VOIP and gamers. its not the connection quality
>>> because we can use a VPN and magically the udp didn't disappear. adding the
>>> latency and overhead improved the VOIP and UDP based games.
>>>
>>> Going Forward we may have places that pure AC may work well but for any
>>> of the old M equipment nothing beats an ePMP2000 with elevated firmware.
>>>
>>> On Fri, Nov 17, 2017 at 1:38 PM, J Portman <ba...@baron.com> wrote:
>>>
>>>> Just as a data point, we upgraded one of our towers to run sync in
>>>> mixed mode a few weeks ago and it has performed flawlessly.
>>>>
>>>> We are getting ready to roll sync out to the entire network (60+ APS).
>>>> I will report on our progress.
>>>>
>>>> YMMV,
>>>> JP
>>>>
>>>>
>>>> *On Fri, 17 Nov 2017 19:56:17 +, Rory Conaway wrote*
>>>> > Understood.  With the [UTF-8?]Prism’s handling multi-mode, have you
>>>> considered that option?
>>>> >
>>>> > Rory
>>>> >
>>>> > *From:* ubnt_users-boun...@wispa.org [mailto:ubnt_users-bounces@wis
>>>> pa.org] *On Behalf Of *David Jones
>>>> > *Sent:* Friday, November 17, 2017 12:21 PM
>>>> > *To:* Ubiquiti Users Group <ubnt_users@wispa.org>
>>>> > *Subject:* Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
>>>> >
>>>> >
>>>> > Well for us it is because we are elevating our units. I also hate the
>>>> locked firmware at and after 6.0.6
>>>> >
>>>> >
>>>> >
>>>> > On Fri, Nov 17, 2017 at 10:21 AM, Rory Conaway <
>>>> r...@triadwireless.net> wrote:
>>>>
>>>>
>>>> >
>>>> > Why are you still running 6.0.4?
>>>> >
>>>> > Rory
>>>> >
>>>> >
>>>> > *From:* ubnt_users-boun...@wispa.org [mailto:ubnt_users-bounces@wis
>>>> pa.org] *On Behalf Of *Troy Gibson, Byhalia.net,LLC
>>>> > *Sent:* Friday, November 17, 2017 5:31 AM
>>>> >
>>>> > *To:* Ubiquiti Users Group <ubnt_users@wispa.org>
>>>> > *Subject:* Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
>>>> >
>>>> >
>>>> >
>>>> > Beta 6 or 7 still does not find 6.0.4.  I have had to go through my
>>>> system to find missing CPE's or APs that were on 6.0.4  Downgraded to
>>>> 5.6.15 for them to be found as I was unsure of the higher 6.0 firmware at
>>>> the time.
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > Troy Gibson
>>>> >
>>>> >
>>>> >
>>>> > Sent from my Verizon, Samsung Galaxy smartphone
>>>> >
>>>> >
>>>> >
>>>> >  Original message 
>>>> >
>>>&

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[RickG]

Wow!

On Sat, Nov 18, 2017 at 12:46 PM, David Jones <d...@nglconnection.com>
wrote:

> That was a 5ghz. I have elevated some NS2's. Here is a NS2 with a
> reflector dish at 14.8 miles getting about 62mbps down. I am really
> impressed with what I can now get from the 2ghz.
>
> On Fri, Nov 17, 2017 at 7:18 PM, RickG <rgunder...@gmail.com> wrote:
>
>> Ha-vent had any issues with the Rocket Prism 5GHz but the "XM" firmware
>> 2.4GHz CPE not so much ;(
>>
>> On Fri, Nov 17, 2017 at 6:33 PM, David Jones <d...@nglconnection.com>
>> wrote:
>>
>>> We tried an AC with MM sync And the performance is worse than just mixed
>>> mode. It may have to do with the clients that have poor signal. With an
>>> elevated XM I can pull 70mbps at a -73 signal with 60 other people
>>> connected to the AP on a 40mhz channel. with a - 64 signal I can pull
>>> 94mbps maxing out the 100mbps port. an XW on the same sector can pull about
>>> 127mbps tcp throughput.
>>> No matter what I tried with UBNT I could not get my legacy devices to
>>> pull more than 40mbps TCP on a sector with more than 35 devices connected.
>>> sure its udp test showed 85mbps+ but the TCP was barely half that. With the
>>> cambium tests the TCP is usually within 5% of it.
>>>
>>> We have also had problems with random UDP packets going missing and it
>>> causes problems with VOIP and gamers. its not the connection quality
>>> because we can use a VPN and magically the udp didn't disappear. adding the
>>> latency and overhead improved the VOIP and UDP based games.
>>>
>>> Going Forward we may have places that pure AC may work well but for any
>>> of the old M equipment nothing beats an ePMP2000 with elevated firmware.
>>>
>>> On Fri, Nov 17, 2017 at 1:38 PM, J Portman <ba...@baron.com> wrote:
>>>
>>>> Just as a data point, we upgraded one of our towers to run sync in
>>>> mixed mode a few weeks ago and it has performed flawlessly.
>>>>
>>>> We are getting ready to roll sync out to the entire network (60+ APS).
>>>> I will report on our progress.
>>>>
>>>> YMMV,
>>>> JP
>>>>
>>>>
>>>> *On Fri, 17 Nov 2017 19:56:17 +, Rory Conaway wrote*
>>>> > Understood.  With the [UTF-8?]Prism’s handling multi-mode, have you
>>>> considered that option?
>>>> >
>>>> > Rory
>>>> >
>>>> > *From:* ubnt_users-boun...@wispa.org [mailto:ubnt_users-bounces@wis
>>>> pa.org] *On Behalf Of *David Jones
>>>> > *Sent:* Friday, November 17, 2017 12:21 PM
>>>> > *To:* Ubiquiti Users Group <ubnt_users@wispa.org>
>>>> > *Subject:* Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
>>>> >
>>>> >
>>>> > Well for us it is because we are elevating our units. I also hate the
>>>> locked firmware at and after 6.0.6
>>>> >
>>>> >
>>>> >
>>>> > On Fri, Nov 17, 2017 at 10:21 AM, Rory Conaway <
>>>> r...@triadwireless.net> wrote:
>>>>
>>>>
>>>> >
>>>> > Why are you still running 6.0.4?
>>>> >
>>>> > Rory
>>>> >
>>>> >
>>>> > *From:* ubnt_users-boun...@wispa.org [mailto:ubnt_users-bounces@wis
>>>> pa.org] *On Behalf Of *Troy Gibson, Byhalia.net,LLC
>>>> > *Sent:* Friday, November 17, 2017 5:31 AM
>>>> >
>>>> > *To:* Ubiquiti Users Group <ubnt_users@wispa.org>
>>>> > *Subject:* Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
>>>> >
>>>> >
>>>> >
>>>> > Beta 6 or 7 still does not find 6.0.4.  I have had to go through my
>>>> system to find missing CPE's or APs that were on 6.0.4  Downgraded to
>>>> 5.6.15 for them to be found as I was unsure of the higher 6.0 firmware at
>>>> the time.
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > Troy Gibson
>>>> >
>>>> >
>>>> >
>>>> > Sent from my Verizon, Samsung Galaxy smartphone
>>>> >
>>>> >
>>>> >
>>>> >  Original message 
>>>> >
>>>> > From: RickG <rgunder.

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[David Jones]

That was a 5ghz. I have elevated some NS2's. Here is a NS2 with a reflector
dish at 14.8 miles getting about 62mbps down. I am really impressed with
what I can now get from the 2ghz.

On Fri, Nov 17, 2017 at 7:18 PM, RickG <rgunder...@gmail.com> wrote:

> Ha-vent had any issues with the Rocket Prism 5GHz but the "XM" firmware
> 2.4GHz CPE not so much ;(
>
> On Fri, Nov 17, 2017 at 6:33 PM, David Jones <d...@nglconnection.com>
> wrote:
>
>> We tried an AC with MM sync And the performance is worse than just mixed
>> mode. It may have to do with the clients that have poor signal. With an
>> elevated XM I can pull 70mbps at a -73 signal with 60 other people
>> connected to the AP on a 40mhz channel. with a - 64 signal I can pull
>> 94mbps maxing out the 100mbps port. an XW on the same sector can pull about
>> 127mbps tcp throughput.
>> No matter what I tried with UBNT I could not get my legacy devices to
>> pull more than 40mbps TCP on a sector with more than 35 devices connected.
>> sure its udp test showed 85mbps+ but the TCP was barely half that. With the
>> cambium tests the TCP is usually within 5% of it.
>>
>> We have also had problems with random UDP packets going missing and it
>> causes problems with VOIP and gamers. its not the connection quality
>> because we can use a VPN and magically the udp didn't disappear. adding the
>> latency and overhead improved the VOIP and UDP based games.
>>
>> Going Forward we may have places that pure AC may work well but for any
>> of the old M equipment nothing beats an ePMP2000 with elevated firmware.
>>
>> On Fri, Nov 17, 2017 at 1:38 PM, J Portman <ba...@baron.com> wrote:
>>
>>> Just as a data point, we upgraded one of our towers to run sync in mixed
>>> mode a few weeks ago and it has performed flawlessly.
>>>
>>> We are getting ready to roll sync out to the entire network (60+ APS). I
>>> will report on our progress.
>>>
>>> YMMV,
>>> JP
>>>
>>>
>>> *On Fri, 17 Nov 2017 19:56:17 +, Rory Conaway wrote*
>>> > Understood.  With the [UTF-8?]Prism’s handling multi-mode, have you
>>> considered that option?
>>> >
>>> > Rory
>>> >
>>> > *From:* ubnt_users-boun...@wispa.org [mailto:ubnt_users-bounces@wis
>>> pa.org] *On Behalf Of *David Jones
>>> > *Sent:* Friday, November 17, 2017 12:21 PM
>>> > *To:* Ubiquiti Users Group <ubnt_users@wispa.org>
>>> > *Subject:* Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
>>> >
>>> >
>>> > Well for us it is because we are elevating our units. I also hate the
>>> locked firmware at and after 6.0.6
>>> >
>>> >
>>> >
>>> > On Fri, Nov 17, 2017 at 10:21 AM, Rory Conaway <r...@triadwireless.net>
>>> wrote:
>>>
>>>
>>> >
>>> > Why are you still running 6.0.4?
>>> >
>>> > Rory
>>> >
>>> >
>>> > *From:* ubnt_users-boun...@wispa.org [mailto:ubnt_users-bounces@wis
>>> pa.org] *On Behalf Of *Troy Gibson, Byhalia.net,LLC
>>> > *Sent:* Friday, November 17, 2017 5:31 AM
>>> >
>>> > *To:* Ubiquiti Users Group <ubnt_users@wispa.org>
>>> > *Subject:* Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
>>> >
>>> >
>>> >
>>> > Beta 6 or 7 still does not find 6.0.4.  I have had to go through my
>>> system to find missing CPE's or APs that were on 6.0.4  Downgraded to
>>> 5.6.15 for them to be found as I was unsure of the higher 6.0 firmware at
>>> the time.
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > Troy Gibson
>>> >
>>> >
>>> >
>>> > Sent from my Verizon, Samsung Galaxy smartphone
>>> >
>>> >
>>> >
>>> >  Original message 
>>> >
>>> > From: RickG <rgunder...@gmail.com>
>>> >
>>> > Date: 11/17/17 4:51 AM (GMT-05:00)
>>> >
>>> > To: Ubiquiti Users Group <ubnt_users@wispa.org>
>>> >
>>> > Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
>>> >
>>> >
>>> >
>>> > The beta works better.
>>> >
>>> >
>>> >
>>> > On Thu, Nov 16, 2017 at 1:48 PM, Phil Curnutt <pcurn...@gmail.com>
>>&

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[RickG]

2.4GHz and/or 5GHz?

On Fri, Nov 17, 2017 at 3:38 PM, J Portman <ba...@baron.com> wrote:

> Just as a data point, we upgraded one of our towers to run sync in mixed
> mode a few weeks ago and it has performed flawlessly.
>
> We are getting ready to roll sync out to the entire network (60+ APS). I
> will report on our progress.
>
> YMMV,
> JP
>
>
> *On Fri, 17 Nov 2017 19:56:17 +, Rory Conaway wrote*
> > Understood.  With the [UTF-8?]Prism’s handling multi-mode, have you
> considered that option?
> >
> > Rory
> >
> > *From:* ubnt_users-boun...@wispa.org [mailto:ubnt_users-bounces@
> wispa.org] *On Behalf Of *David Jones
> > *Sent:* Friday, November 17, 2017 12:21 PM
> > *To:* Ubiquiti Users Group <ubnt_users@wispa.org>
> > *Subject:* Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
> >
> >
> > Well for us it is because we are elevating our units. I also hate the
> locked firmware at and after 6.0.6
> >
> >
> >
> > On Fri, Nov 17, 2017 at 10:21 AM, Rory Conaway <r...@triadwireless.net>
> wrote:
>
>
> >
> > Why are you still running 6.0.4?
> >
> > Rory
> >
> >
> > *From:* ubnt_users-boun...@wispa.org [mailto:ubnt_users-bounces@
> wispa.org] *On Behalf Of *Troy Gibson, Byhalia.net,LLC
> > *Sent:* Friday, November 17, 2017 5:31 AM
> >
> > *To:* Ubiquiti Users Group <ubnt_users@wispa.org>
> > *Subject:* Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
> >
> >
> >
> > Beta 6 or 7 still does not find 6.0.4.  I have had to go through my
> system to find missing CPE's or APs that were on 6.0.4  Downgraded to
> 5.6.15 for them to be found as I was unsure of the higher 6.0 firmware at
> the time.
> >
> >
> >
> >
> >
> >
> >
> > Troy Gibson
> >
> >
> >
> > Sent from my Verizon, Samsung Galaxy smartphone
> >
> >
> >
> >  Original message 
> >
> > From: RickG <rgunder...@gmail.com>
> >
> > Date: 11/17/17 4:51 AM (GMT-05:00)
> >
> > To: Ubiquiti Users Group <ubnt_users@wispa.org>
> >
> > Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
> >
> >
> >
> > The beta works better.
> >
> >
> >
> > On Thu, Nov 16, 2017 at 1:48 PM, Phil Curnutt <pcurn...@gmail.com>
> wrote:
>
>
> >
> > AirControl2 2.0.3 is found on Ubnt.com, Support>Downloads>AirMax>Utilities.
> Your have choices of Linux or Windows10 Servers and Clients and Mac
> Clients.  I found our 900 radios on 5.6.9, but not the one on 6.0.4, but I
> was able to add the device manually using v 2.0.2.
> >
> >
> >
> > Phil
> >
> >
> >
> > On Thu, Nov 16, 2017 at 11:18 AM, Jan Van Kort <
> j.vank...@oregononline.net> wrote:
>
>
> >
> > I had an earlier version of air control installed and gave up trying to
> make it work over 2 years ago.  Where do i go to get a current version of
> air control so I can try it again?  I'm wandering around the ubnt.com
> website and can't find it.  Does the current version have the 6.04 issue?
> >
> >
> > On 08/31/2017 11:05 AM, James Craig via Ubnt_users wrote:
>
>
> >
> > Hi Guys,
> >
> >
> >
> > This is most likely due to this change in discovery in 6.0.4.  We're
> adding CGN address space in 6.0.7, so moving forward, you will only be able
> to discover from RFC1918 and RFC6598 address. IP range scanning should
> still work.
> >
> >
> >
>
> - Fix: Limit discovery response to queries from private
> subnets or
> multicast/broadcast
>
>
> >
> >
> >
> > On Thu, Aug 31, 2017 at 1:58 PM, Troy Gibson, Byhalia.net,LLC <
> t...@byhalia.net> wrote:
>
>
> >
> > I'm on AC2.1 beta 7 and it won't find any 6.0.4 radios, XW or XM.  I had
> some being monitored on beta 6, so those are still monitored, but show in
> devices not found column of discovery.  TCP scan only showed prism radios
> too.
> >
> >
> >
> > I downgraded to 5.6.15 and it was discovered.  I had to downgrade AP and
> CPE for it to discover the devices on AC. Now to search for the missing
> radios!!
> >
> >
> >
> >
> >
> > Troy
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Sent from my Verizon, Samsung Galaxy smartphone
> >
> >
> >
> >  Original message 
> >
> > From: CBB - Jay Fuller <par...@cyb

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[James Craig via Ubnt_users]

Hi David,

I would like to have a look if you have any MM sectors that are seeing a
larger discrepancy between UDP and TCP performance.  Sending you an email.


>No matter what I tried with UBNT I could not get my legacy devices to pull
more than 40mbps TCP on a sector with more than 35 devices connected. sure
its udp test showed 85mbps+ but the TCP was barely half that. With the
cambium tests the TCP is usually within 5% of it.

Thanks,
James



On Fri, Nov 17, 2017 at 6:33 PM, David Jones <d...@nglconnection.com> wrote:

> We tried an AC with MM sync And the performance is worse than just mixed
> mode. It may have to do with the clients that have poor signal. With an
> elevated XM I can pull 70mbps at a -73 signal with 60 other people
> connected to the AP on a 40mhz channel. with a - 64 signal I can pull
> 94mbps maxing out the 100mbps port. an XW on the same sector can pull about
> 127mbps tcp throughput.
> No matter what I tried with UBNT I could not get my legacy devices to pull
> more than 40mbps TCP on a sector with more than 35 devices connected. sure
> its udp test showed 85mbps+ but the TCP was barely half that. With the
> cambium tests the TCP is usually within 5% of it.
>
> We have also had problems with random UDP packets going missing and it
> causes problems with VOIP and gamers. its not the connection quality
> because we can use a VPN and magically the udp didn't disappear. adding the
> latency and overhead improved the VOIP and UDP based games.
>
> Going Forward we may have places that pure AC may work well but for any of
> the old M equipment nothing beats an ePMP2000 with elevated firmware.
>
> On Fri, Nov 17, 2017 at 1:38 PM, J Portman <ba...@baron.com> wrote:
>
>> Just as a data point, we upgraded one of our towers to run sync in mixed
>> mode a few weeks ago and it has performed flawlessly.
>>
>> We are getting ready to roll sync out to the entire network (60+ APS). I
>> will report on our progress.
>>
>> YMMV,
>> JP
>>
>>
>> *On Fri, 17 Nov 2017 19:56:17 +, Rory Conaway wrote*
>> > Understood.  With the [UTF-8?]Prism’s handling multi-mode, have you
>> considered that option?
>> >
>> > Rory
>> >
>> > *From:* ubnt_users-boun...@wispa.org [mailto:ubnt_users-bounces@wis
>> pa.org] *On Behalf Of *David Jones
>> > *Sent:* Friday, November 17, 2017 12:21 PM
>> > *To:* Ubiquiti Users Group <ubnt_users@wispa.org>
>> > *Subject:* Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
>> >
>> >
>> > Well for us it is because we are elevating our units. I also hate the
>> locked firmware at and after 6.0.6
>> >
>> >
>> >
>> > On Fri, Nov 17, 2017 at 10:21 AM, Rory Conaway <r...@triadwireless.net>
>> wrote:
>>
>>
>> >
>> > Why are you still running 6.0.4?
>> >
>> > Rory
>> >
>> >
>> > *From:* ubnt_users-boun...@wispa.org [mailto:ubnt_users-bounces@wis
>> pa.org] *On Behalf Of *Troy Gibson, Byhalia.net,LLC
>> > *Sent:* Friday, November 17, 2017 5:31 AM
>> >
>> > *To:* Ubiquiti Users Group <ubnt_users@wispa.org>
>> > *Subject:* Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
>> >
>> >
>> >
>> > Beta 6 or 7 still does not find 6.0.4.  I have had to go through my
>> system to find missing CPE's or APs that were on 6.0.4  Downgraded to
>> 5.6.15 for them to be found as I was unsure of the higher 6.0 firmware at
>> the time.
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > Troy Gibson
>> >
>> >
>> >
>> > Sent from my Verizon, Samsung Galaxy smartphone
>> >
>> >
>> >
>> >  Original message 
>> >
>> > From: RickG <rgunder...@gmail.com>
>> >
>> > Date: 11/17/17 4:51 AM (GMT-05:00)
>> >
>> > To: Ubiquiti Users Group <ubnt_users@wispa.org>
>> >
>> > Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
>> >
>> >
>> >
>> > The beta works better.
>> >
>> >
>> >
>> > On Thu, Nov 16, 2017 at 1:48 PM, Phil Curnutt <pcurn...@gmail.com>
>> wrote:
>>
>>
>> >
>> > AirControl2 2.0.3 is found on Ubnt.com, Support>Downloads>AirMax>Utilities.
>> Your have choices of Linux or Windows10 Servers and Clients and Mac
>> Clients.  I found our 900 radios on 5.6.9, but not the one on 6.0.4, but I
>> was able to add the device manually using v 2.0.2.
>

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[David Jones]

We tried an AC with MM sync And the performance is worse than just mixed
mode. It may have to do with the clients that have poor signal. With an
elevated XM I can pull 70mbps at a -73 signal with 60 other people
connected to the AP on a 40mhz channel. with a - 64 signal I can pull
94mbps maxing out the 100mbps port. an XW on the same sector can pull about
127mbps tcp throughput.
No matter what I tried with UBNT I could not get my legacy devices to pull
more than 40mbps TCP on a sector with more than 35 devices connected. sure
its udp test showed 85mbps+ but the TCP was barely half that. With the
cambium tests the TCP is usually within 5% of it.

We have also had problems with random UDP packets going missing and it
causes problems with VOIP and gamers. its not the connection quality
because we can use a VPN and magically the udp didn't disappear. adding the
latency and overhead improved the VOIP and UDP based games.

Going Forward we may have places that pure AC may work well but for any of
the old M equipment nothing beats an ePMP2000 with elevated firmware.

On Fri, Nov 17, 2017 at 1:38 PM, J Portman <ba...@baron.com> wrote:

> Just as a data point, we upgraded one of our towers to run sync in mixed
> mode a few weeks ago and it has performed flawlessly.
>
> We are getting ready to roll sync out to the entire network (60+ APS). I
> will report on our progress.
>
> YMMV,
> JP
>
>
> *On Fri, 17 Nov 2017 19:56:17 +, Rory Conaway wrote*
> > Understood.  With the [UTF-8?]Prism’s handling multi-mode, have you
> considered that option?
> >
> > Rory
> >
> > *From:* ubnt_users-boun...@wispa.org [mailto:ubnt_users-bounces@
> wispa.org] *On Behalf Of *David Jones
> > *Sent:* Friday, November 17, 2017 12:21 PM
> > *To:* Ubiquiti Users Group <ubnt_users@wispa.org>
> > *Subject:* Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
> >
> >
> > Well for us it is because we are elevating our units. I also hate the
> locked firmware at and after 6.0.6
> >
> >
> >
> > On Fri, Nov 17, 2017 at 10:21 AM, Rory Conaway <r...@triadwireless.net>
> wrote:
>
>
> >
> > Why are you still running 6.0.4?
> >
> > Rory
> >
> >
> > *From:* ubnt_users-boun...@wispa.org [mailto:ubnt_users-bounces@
> wispa.org] *On Behalf Of *Troy Gibson, Byhalia.net,LLC
> > *Sent:* Friday, November 17, 2017 5:31 AM
> >
> > *To:* Ubiquiti Users Group <ubnt_users@wispa.org>
> > *Subject:* Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
> >
> >
> >
> > Beta 6 or 7 still does not find 6.0.4.  I have had to go through my
> system to find missing CPE's or APs that were on 6.0.4  Downgraded to
> 5.6.15 for them to be found as I was unsure of the higher 6.0 firmware at
> the time.
> >
> >
> >
> >
> >
> >
> >
> > Troy Gibson
> >
> >
> >
> > Sent from my Verizon, Samsung Galaxy smartphone
> >
> >
> >
> >  Original message 
> >
> > From: RickG <rgunder...@gmail.com>
> >
> > Date: 11/17/17 4:51 AM (GMT-05:00)
> >
> > To: Ubiquiti Users Group <ubnt_users@wispa.org>
> >
> > Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
> >
> >
> >
> > The beta works better.
> >
> >
> >
> > On Thu, Nov 16, 2017 at 1:48 PM, Phil Curnutt <pcurn...@gmail.com>
> wrote:
>
>
> >
> > AirControl2 2.0.3 is found on Ubnt.com, Support>Downloads>AirMax>Utilities.
> Your have choices of Linux or Windows10 Servers and Clients and Mac
> Clients.  I found our 900 radios on 5.6.9, but not the one on 6.0.4, but I
> was able to add the device manually using v 2.0.2.
> >
> >
> >
> > Phil
> >
> >
> >
> > On Thu, Nov 16, 2017 at 11:18 AM, Jan Van Kort <
> j.vank...@oregononline.net> wrote:
>
>
> >
> > I had an earlier version of air control installed and gave up trying to
> make it work over 2 years ago.  Where do i go to get a current version of
> air control so I can try it again?  I'm wandering around the ubnt.com
> website and can't find it.  Does the current version have the 6.04 issue?
> >
> >
> > On 08/31/2017 11:05 AM, James Craig via Ubnt_users wrote:
>
>
> >
> > Hi Guys,
> >
> >
> >
> > This is most likely due to this change in discovery in 6.0.4.  We're
> adding CGN address space in 6.0.7, so moving forward, you will only be able
> to discover from RFC1918 and RFC6598 address. IP range scanning should
> still work.
> >
> >
> >
>
> - Fix: Limit discovery response to queri

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[J Portman]

Just as a data point, we upgraded one of our towers to run sync in mixed mode a 
few weeks ago and it has performed flawlessly.

We are getting ready to roll sync out to the entire network (60+ APS). I will 
report on our progress.

YMMV,
JP

On Fri, 17 Nov 2017 19:56:17 +, Rory Conaway wrote
> Understood.  With the [UTF-8?]Prism’s handling multi-mode, have you 
> considered that option?
>  
> Rory
>  
> From: ubnt_users-boun...@wispa.org [mailto:ubnt_users-boun...@wispa.org]On 
> Behalf Of David Jones
> Sent: Friday, November 17, 2017 12:21 PM
> To: Ubiquiti Users Group <ubnt_users@wispa.org>
> Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
>  
> 
> Well for us it is because we are elevating our units. I also hate the locked 
> firmware at and after 6.0.6
> 
>  
> 
> On Fri, Nov 17, 2017 at 10:21 AM, Rory Conaway <r...@triadwireless.net> wrote:
> 
> Why are you still running 6.0.4?
>  
> Rory
>  
> 
> From:ubnt_users-boun...@wispa.org [mailto:ubnt_users-boun...@wispa.org]On 
> Behalf Of Troy Gibson, Byhalia.net,LLC
> Sent: Friday, November 17, 2017 5:31 AM
> 
> To: Ubiquiti Users Group <ubnt_users@wispa.org>
> Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
> 
>  
> 
> Beta 6 or 7 still does not find 6.0.4.  I have had to go through my system to 
> find missing CPE's or APs that were on 6.0.4  Downgraded to 5.6.15 for them 
> to be found as I was unsureof the higher 6.0 firmware at the time.
> 
>  
> 
>  
> 
>  
> 
> Troy Gibson
> 
>  
> 
> Sent from my Verizon, Samsung Galaxy smartphone
> 
>  
> 
>  Original message 
> 
> From: RickG <rgunder...@gmail.com>
> 
> Date: 11/17/17 4:51 AM (GMT-05:00)
> 
> To: Ubiquiti Users Group <ubnt_users@wispa.org>
> 
> Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
> 
>  
> 
> The beta works better.
> 
>  
> 
> On Thu, Nov 16, 2017 at 1:48 PM, Phil Curnutt <pcurn...@gmail.com> wrote:
> 
> AirControl2 2.0.3 is found on Ubnt.com, Support>Downloads>AirMax>Utilities.  
> Your have choices of Linux or Windows10 Servers and Clients and Mac Clients.  
> I found our 900 radioson 5.6.9, but not the one on 6.0.4, but I was able to 
> add the device manually using v 2.0.2.
> 
>  
> 
> Phil
> 
>  
> 
> On Thu, Nov 16, 2017 at 11:18 AM, Jan Van Kort <j.vank...@oregononline.net> 
> wrote:
> 
> I had an earlier version of air control installed and gave up trying to make 
> it work over 2 years ago.  Where do i go to get a current version of air 
> control so I can try it again?  I'm wandering around theubnt.com website and 
> can't find it.  Does the current version have the 6.04 issue?
>  
> 
> On 08/31/2017 11:05 AM, James Craig via Ubnt_users wrote:
> 
> Hi Guys,
> 
>  
> 
> This is most likely due to this change in discovery in 6.0.4. We're adding 
> CGN address space in 6.0.7, so moving forward, you will only be able to 
> discover from RFC1918 and RFC6598address. IP range scanning should still work.
> 
>  
>- Fix: Limit discovery response to queries from private 
subnets or 
multicast/broadcast
> 
>  
> 
> On Thu, Aug 31, 2017 at 1:58 PM, Troy Gibson, Byhalia.net,LLC 
> <t...@byhalia.net> wrote:
> 
> I'm on AC2.1 beta 7 and it won't find any 6.0.4 radios, XW or XM.  I had some 
> being monitored on beta 6, so those are still monitored, but show in devices 
> not found column of discovery. TCP scan only showed prism radios too.
> 
>  
> 
> I downgraded to 5.6.15 and it was discovered.  I had to downgrade AP and CPE 
> for it to discover the devices on AC. Now to search for the missing radios!!
> 
>  
> 
>  
> 
> Troy
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
> Sent from my Verizon, Samsung Galaxy smartphone
> 
>  
> 
>  Original message 
> 
> From: CBB - Jay Fuller <par...@cyberbroadband.net>
> 
> Date: 8/31/17 1:25 PM (GMT-05:00)
> 
> To: Ubiquiti Users Group <ubnt_users@wispa.org>
> 
> Subject: [Ubnt_users] aircontrol won't find 6.0.4 devices
> 
>  
> 
>  
> 
> Been reading all about it in the ubnt forums - but anyone have any 
> suggestions around this?
> 
>  
> 
> Thought I'd post it here too -
> 
>  
> 
> Haven't run aircontrol since about 18 months ago.  About nine months ago I 
> attempted to upgrade to the then current beta but it basicallycorrupted my 
> database and would not even start the server service.  Last night late I 
> started over again from scratch.  Ran into the 6.0.4 problem as one of my 
> network segments (from a recent purchas

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[RickG]

Mine does. Using AC 2.1 Beta9

On Fri, Nov 17, 2017 at 7:31 AM, Troy Gibson, Byhalia.net,LLC <
t...@byhalia.net> wrote:

> Beta 6 or 7 still does not find 6.0.4.  I have had to go through my system
> to find missing CPE's or APs that were on 6.0.4  Downgraded to 5.6.15 for
> them to be found as I was unsure of the higher 6.0 firmware at the time.
>
>
>
> Troy Gibson
>
> Sent from my Verizon, Samsung Galaxy smartphone
>
>  Original message 
> From: RickG <rgunder...@gmail.com>
> Date: 11/17/17 4:51 AM (GMT-05:00)
> To: Ubiquiti Users Group <ubnt_users@wispa.org>
> Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
>
> The beta works better.
>
> On Thu, Nov 16, 2017 at 1:48 PM, Phil Curnutt <pcurn...@gmail.com> wrote:
>
>> AirControl2 2.0.3 is found on Ubnt.com, Support>Downloads>AirMax>Utilities.
>> Your have choices of Linux or Windows10 Servers and Clients and Mac
>> Clients.  I found our 900 radios on 5.6.9, but not the one on 6.0.4, but I
>> was able to add the device manually using v 2.0.2.
>>
>> Phil
>>
>> On Thu, Nov 16, 2017 at 11:18 AM, Jan Van Kort <
>> j.vank...@oregononline.net> wrote:
>>
>>> I had an earlier version of air control installed and gave up trying to
>>> make it work over 2 years ago.  Where do i go to get a current version of
>>> air control so I can try it again?  I'm wandering around the ubnt.com
>>> website and can't find it.  Does the current version have the 6.04 issue?
>>>
>>> On 08/31/2017 11:05 AM, James Craig via Ubnt_users wrote:
>>>
>>> Hi Guys,
>>>
>>> This is most likely due to this change in discovery in 6.0.4.  We're
>>> adding CGN address space in 6.0.7, so moving forward, you will only be able
>>> to discover from RFC1918 and RFC6598 address. IP range scanning should
>>> still work.
>>>
>>> - Fix: Limit discovery response to queries from private subnets or 
>>> multicast/broadcast
>>>
>>>
>>> On Thu, Aug 31, 2017 at 1:58 PM, Troy Gibson, Byhalia.net,LLC <
>>> t...@byhalia.net> wrote:
>>>
>>>> I'm on AC2.1 beta 7 and it won't find any 6.0.4 radios, XW or XM.  I
>>>> had some being monitored on beta 6, so those are still monitored, but show
>>>> in devices not found column of discovery.  TCP scan only showed prism
>>>> radios too.
>>>>
>>>> I downgraded to 5.6.15 and it was discovered.  I had to downgrade AP
>>>> and CPE for it to discover the devices on AC. Now to search for the missing
>>>> radios!!
>>>>
>>>>
>>>> Troy
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Sent from my Verizon, Samsung Galaxy smartphone
>>>>
>>>>  Original message 
>>>> From: CBB - Jay Fuller <par...@cyberbroadband.net>
>>>> Date: 8/31/17 1:25 PM (GMT-05:00)
>>>> To: Ubiquiti Users Group <ubnt_users@wispa.org>
>>>> Subject: [Ubnt_users] aircontrol won't find 6.0.4 devices
>>>>
>>>>
>>>> Been reading all about it in the ubnt forums - but anyone have any
>>>> suggestions around this?
>>>>
>>>> Thought I'd post it here too -
>>>>
>>>> Haven't run aircontrol since about 18 months ago.  About nine months
>>>> ago I attempted to upgrade to the then current beta but it basically
>>>> corrupted my database and would not even start the server service.  Last
>>>> night late I started over again from scratch.  Ran into the 6.0.4 problem
>>>> as one of my network segments (from a recent purchase) we have manually
>>>> changed the ip addresses and put them all on 6.0.4
>>>>
>>>>
>>>> A different segment is still running 5.6.3.  I was planning to move
>>>> them all to 6.0.4 and also make a mass change of the username / password.
>>>>
>>>>
>>>>
>>>> Left discovering overnight, found all the devices on 5.6.3 on that
>>>> particular network segment but did not find any 6.0.4
>>>>
>>>>
>>>>
>>>> Today once googling and discovering this issue I downgraded an AP from
>>>> 6.0.4 to 5.6.3 and discovery found it immediately.
>>>>
>>>>
>>>>
>>>> I don't want to do this to 300 devices.
>>>>
>>>>
>>>>
&

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[Rory Conaway]

Understood.  With the Prism’s handling multi-mode, have you considered that 
option?

Rory

From: ubnt_users-boun...@wispa.org [mailto:ubnt_users-boun...@wispa.org] On 
Behalf Of David Jones
Sent: Friday, November 17, 2017 12:21 PM
To: Ubiquiti Users Group <ubnt_users@wispa.org>
Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

Well for us it is because we are elevating our units. I also hate the locked 
firmware at and after 6.0.6

On Fri, Nov 17, 2017 at 10:21 AM, Rory Conaway 
<r...@triadwireless.net<mailto:r...@triadwireless.net>> wrote:
Why are you still running 6.0.4?

Rory

From: ubnt_users-boun...@wispa.org<mailto:ubnt_users-boun...@wispa.org> 
[mailto:ubnt_users-boun...@wispa.org<mailto:ubnt_users-boun...@wispa.org>] On 
Behalf Of Troy Gibson, Byhalia.net,LLC
Sent: Friday, November 17, 2017 5:31 AM

To: Ubiquiti Users Group <ubnt_users@wispa.org<mailto:ubnt_users@wispa.org>>
Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

Beta 6 or 7 still does not find 6.0.4.  I have had to go through my system to 
find missing CPE's or APs that were on 6.0.4  Downgraded to 5.6.15 for them to 
be found as I was unsure of the higher 6.0 firmware at the time.



Troy Gibson

Sent from my Verizon, Samsung Galaxy smartphone

 Original message 
From: RickG <rgunder...@gmail.com<mailto:rgunder...@gmail.com>>
Date: 11/17/17 4:51 AM (GMT-05:00)
To: Ubiquiti Users Group <ubnt_users@wispa.org<mailto:ubnt_users@wispa.org>>
Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

The beta works better.

On Thu, Nov 16, 2017 at 1:48 PM, Phil Curnutt 
<pcurn...@gmail.com<mailto:pcurn...@gmail.com>> wrote:
AirControl2 2.0.3 is found on Ubnt.com, Support>Downloads>AirMax>Utilities.  
Your have choices of Linux or Windows10 Servers and Clients and Mac Clients.  I 
found our 900 radios on 5.6.9, but not the one on 6.0.4, but I was able to add 
the device manually using v 2.0.2.

Phil

On Thu, Nov 16, 2017 at 11:18 AM, Jan Van Kort 
<j.vank...@oregononline.net<mailto:j.vank...@oregononline.net>> wrote:

I had an earlier version of air control installed and gave up trying to make it 
work over 2 years ago.  Where do i go to get a current version of air control 
so I can try it again?  I'm wandering around the ubnt.com<http://ubnt.com> 
website and can't find it.  Does the current version have the 6.04 issue?

On 08/31/2017 11:05 AM, James Craig via Ubnt_users wrote:
Hi Guys,

This is most likely due to this change in discovery in 6.0.4.  We're adding CGN 
address space in 6.0.7, so moving forward, you will only be able to discover 
from RFC1918 and RFC6598 address. IP range scanning should still work.


- Fix: Limit discovery response to queries from private subnets or 
multicast/broadcast

On Thu, Aug 31, 2017 at 1:58 PM, Troy Gibson, Byhalia.net,LLC 
<t...@byhalia.net<mailto:t...@byhalia.net>> wrote:
I'm on AC2.1 beta 7 and it won't find any 6.0.4 radios, XW or XM.  I had some 
being monitored on beta 6, so those are still monitored, but show in devices 
not found column of discovery.  TCP scan only showed prism radios too.

I downgraded to 5.6.15 and it was discovered.  I had to downgrade AP and CPE 
for it to discover the devices on AC. Now to search for the missing radios!!


Troy





Sent from my Verizon, Samsung Galaxy smartphone

 Original message 
From: CBB - Jay Fuller 
<par...@cyberbroadband.net<mailto:par...@cyberbroadband.net>>
Date: 8/31/17 1:25 PM (GMT-05:00)
To: Ubiquiti Users Group <ubnt_users@wispa.org<mailto:ubnt_users@wispa.org>>
Subject: [Ubnt_users] aircontrol won't find 6.0.4 devices


Been reading all about it in the ubnt forums - but anyone have any suggestions 
around this?

Thought I'd post it here too -

Haven't run aircontrol since about 18 months ago.  About nine months ago I 
attempted to upgrade to the then current beta but it basically corrupted my 
database and would not even start the server service.  Last night late I 
started over again from scratch.  Ran into the 6.0.4 problem as one of my 
network segments (from a recent purchase) we have manually changed the ip 
addresses and put them all on 6.0.4


A different segment is still running 5.6.3.  I was planning to move them all to 
6.0.4 and also make a mass change of the username / password.



Left discovering overnight, found all the devices on 5.6.3 on that particular 
network segment but did not find any 6.0.4



Today once googling and discovering this issue I downgraded an AP from 6.0.4 to 
5.6.3 and discovery found it immediately.



I don't want to do this to 300 devices.



Aircontrol v.2.0.2.2874.170719.18353 is running on a public IP within our 
network.



I tried to new feature tcp scan but no luck (probably because the server is in 
public ip space).


I thought about temporarily changing the IP but then radios would be rep

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[David Jones]

Well for us it is because we are elevating our units. I also hate the
locked firmware at and after 6.0.6

On Fri, Nov 17, 2017 at 10:21 AM, Rory Conaway <r...@triadwireless.net>
wrote:

> Why are you still running 6.0.4?
>
>
>
> Rory
>
>
>
> *From:* ubnt_users-boun...@wispa.org [mailto:ubnt_users-boun...@wispa.org]
> *On Behalf Of *Troy Gibson, Byhalia.net,LLC
> *Sent:* Friday, November 17, 2017 5:31 AM
>
> *To:* Ubiquiti Users Group <ubnt_users@wispa.org>
> *Subject:* Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
>
>
>
> Beta 6 or 7 still does not find 6.0.4.  I have had to go through my system
> to find missing CPE's or APs that were on 6.0.4  Downgraded to 5.6.15 for
> them to be found as I was unsure of the higher 6.0 firmware at the time.
>
>
>
>
>
>
>
> Troy Gibson
>
>
>
> Sent from my Verizon, Samsung Galaxy smartphone
>
>
>
>  Original message 
>
> From: RickG <rgunder...@gmail.com>
>
> Date: 11/17/17 4:51 AM (GMT-05:00)
>
> To: Ubiquiti Users Group <ubnt_users@wispa.org>
>
> Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
>
>
>
> The beta works better.
>
>
>
> On Thu, Nov 16, 2017 at 1:48 PM, Phil Curnutt <pcurn...@gmail.com> wrote:
>
> AirControl2 2.0.3 is found on Ubnt.com, Support>Downloads>AirMax>Utilities.
> Your have choices of Linux or Windows10 Servers and Clients and Mac
> Clients.  I found our 900 radios on 5.6.9, but not the one on 6.0.4, but I
> was able to add the device manually using v 2.0.2.
>
>
>
> Phil
>
>
>
> On Thu, Nov 16, 2017 at 11:18 AM, Jan Van Kort <j.vank...@oregononline.net>
> wrote:
>
> I had an earlier version of air control installed and gave up trying to
> make it work over 2 years ago.  Where do i go to get a current version of
> air control so I can try it again?  I'm wandering around the ubnt.com
> website and can't find it.  Does the current version have the 6.04 issue?
>
>
>
> On 08/31/2017 11:05 AM, James Craig via Ubnt_users wrote:
>
> Hi Guys,
>
>
>
> This is most likely due to this change in discovery in 6.0.4.  We're
> adding CGN address space in 6.0.7, so moving forward, you will only be able
> to discover from RFC1918 and RFC6598 address. IP range scanning should
> still work.
>
>
>
> - Fix: Limit discovery response to queries from private subnets or 
> multicast/broadcast
>
>
>
> On Thu, Aug 31, 2017 at 1:58 PM, Troy Gibson, Byhalia.net,LLC <
> t...@byhalia.net> wrote:
>
> I'm on AC2.1 beta 7 and it won't find any 6.0.4 radios, XW or XM.  I had
> some being monitored on beta 6, so those are still monitored, but show in
> devices not found column of discovery.  TCP scan only showed prism radios
> too.
>
>
>
> I downgraded to 5.6.15 and it was discovered.  I had to downgrade AP and
> CPE for it to discover the devices on AC. Now to search for the missing
> radios!!
>
>
>
>
>
> Troy
>
>
>
>
>
>
>
>
>
>
>
> Sent from my Verizon, Samsung Galaxy smartphone
>
>
>
>  Original message 
>
> From: CBB - Jay Fuller <par...@cyberbroadband.net>
>
> Date: 8/31/17 1:25 PM (GMT-05:00)
>
> To: Ubiquiti Users Group <ubnt_users@wispa.org>
>
> Subject: [Ubnt_users] aircontrol won't find 6.0.4 devices
>
>
>
>
>
> Been reading all about it in the ubnt forums - but anyone have any
> suggestions around this?
>
>
>
> Thought I'd post it here too -
>
>
>
> Haven't run aircontrol since about 18 months ago.  About nine months ago I
> attempted to upgrade to the then current beta but it basically corrupted my
> database and would not even start the server service.  Last night late I
> started over again from scratch.  Ran into the 6.0.4 problem as one of my
> network segments (from a recent purchase) we have manually changed the ip
> addresses and put them all on 6.0.4
>
>
>
>
> A different segment is still running 5.6.3.  I was planning to move them
> all to 6.0.4 and also make a mass change of the username / password.
>
>
>
>
>
>
>
> Left discovering overnight, found all the devices on 5.6.3 on that
> particular network segment but did not find any 6.0.4
>
>
>
>
>
>
>
> Today once googling and discovering this issue I downgraded an AP from
> 6.0.4 to 5.6.3 and discovery found it immediately.
>
>
>
>
>
>
>
> I don't want to do this to 300 devices.
>
>
>
>
>
>
>
> Aircontrol v.2.0.2.2874.170719.18353 is running on a public IP within our
> network.
>
>
>
>
>
>
>

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[Rory Conaway]

Why are you still running 6.0.4?

Rory

From: ubnt_users-boun...@wispa.org [mailto:ubnt_users-boun...@wispa.org] On 
Behalf Of Troy Gibson, Byhalia.net,LLC
Sent: Friday, November 17, 2017 5:31 AM
To: Ubiquiti Users Group <ubnt_users@wispa.org>
Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

Beta 6 or 7 still does not find 6.0.4.  I have had to go through my system to 
find missing CPE's or APs that were on 6.0.4  Downgraded to 5.6.15 for them to 
be found as I was unsure of the higher 6.0 firmware at the time.



Troy Gibson

Sent from my Verizon, Samsung Galaxy smartphone

 Original message 
From: RickG <rgunder...@gmail.com<mailto:rgunder...@gmail.com>>
Date: 11/17/17 4:51 AM (GMT-05:00)
To: Ubiquiti Users Group <ubnt_users@wispa.org<mailto:ubnt_users@wispa.org>>
Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

The beta works better.

On Thu, Nov 16, 2017 at 1:48 PM, Phil Curnutt 
<pcurn...@gmail.com<mailto:pcurn...@gmail.com>> wrote:
AirControl2 2.0.3 is found on Ubnt.com, Support>Downloads>AirMax>Utilities.  
Your have choices of Linux or Windows10 Servers and Clients and Mac Clients.  I 
found our 900 radios on 5.6.9, but not the one on 6.0.4, but I was able to add 
the device manually using v 2.0.2.

Phil

On Thu, Nov 16, 2017 at 11:18 AM, Jan Van Kort 
<j.vank...@oregononline.net<mailto:j.vank...@oregononline.net>> wrote:

I had an earlier version of air control installed and gave up trying to make it 
work over 2 years ago.  Where do i go to get a current version of air control 
so I can try it again?  I'm wandering around the ubnt.com<http://ubnt.com> 
website and can't find it.  Does the current version have the 6.04 issue?

On 08/31/2017 11:05 AM, James Craig via Ubnt_users wrote:
Hi Guys,

This is most likely due to this change in discovery in 6.0.4.  We're adding CGN 
address space in 6.0.7, so moving forward, you will only be able to discover 
from RFC1918 and RFC6598 address. IP range scanning should still work.


- Fix: Limit discovery response to queries from private subnets or 
multicast/broadcast

On Thu, Aug 31, 2017 at 1:58 PM, Troy Gibson, Byhalia.net,LLC 
<t...@byhalia.net<mailto:t...@byhalia.net>> wrote:
I'm on AC2.1 beta 7 and it won't find any 6.0.4 radios, XW or XM.  I had some 
being monitored on beta 6, so those are still monitored, but show in devices 
not found column of discovery.  TCP scan only showed prism radios too.

I downgraded to 5.6.15 and it was discovered.  I had to downgrade AP and CPE 
for it to discover the devices on AC. Now to search for the missing radios!!


Troy





Sent from my Verizon, Samsung Galaxy smartphone

 Original message 
From: CBB - Jay Fuller 
<par...@cyberbroadband.net<mailto:par...@cyberbroadband.net>>
Date: 8/31/17 1:25 PM (GMT-05:00)
To: Ubiquiti Users Group <ubnt_users@wispa.org<mailto:ubnt_users@wispa.org>>
Subject: [Ubnt_users] aircontrol won't find 6.0.4 devices


Been reading all about it in the ubnt forums - but anyone have any suggestions 
around this?

Thought I'd post it here too -

Haven't run aircontrol since about 18 months ago.  About nine months ago I 
attempted to upgrade to the then current beta but it basically corrupted my 
database and would not even start the server service.  Last night late I 
started over again from scratch.  Ran into the 6.0.4 problem as one of my 
network segments (from a recent purchase) we have manually changed the ip 
addresses and put them all on 6.0.4


A different segment is still running 5.6.3.  I was planning to move them all to 
6.0.4 and also make a mass change of the username / password.



Left discovering overnight, found all the devices on 5.6.3 on that particular 
network segment but did not find any 6.0.4



Today once googling and discovering this issue I downgraded an AP from 6.0.4 to 
5.6.3 and discovery found it immediately.



I don't want to do this to 300 devices.



Aircontrol v.2.0.2.2874.170719.18353 is running on a public IP within our 
network.



I tried to new feature tcp scan but no luck (probably because the server is in 
public ip space).


I thought about temporarily changing the IP but then radios would be reporting 
to the wrong IP.



I can manually add the device but have not found a way to do that in bulk.



I don't know if it is easier for me to upgrade to something higher than 6.0.4 
on all of my devices and use discovery or to manually add 300+ devices.  I am 
hoping for another option.



Bueller?  Bueller?



Thanks

___
Ubnt_users mailing list
Ubnt_users@wispa.org<mailto:Ubnt_users@wispa.org>
http://lists.wispa.org/mailman/listinfo/ubnt_users




___

Ubnt_users mailing list

Ubnt_users@wispa.org<mailto:Ubnt_users@wispa.org>

http://lists.wispa.org/mailman/listinfo/ubnt_users


_

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[RickG]

The beta works better.

On Thu, Nov 16, 2017 at 1:48 PM, Phil Curnutt <pcurn...@gmail.com> wrote:

> AirControl2 2.0.3 is found on Ubnt.com, Support>Downloads>AirMax>Utilities.
> Your have choices of Linux or Windows10 Servers and Clients and Mac
> Clients.  I found our 900 radios on 5.6.9, but not the one on 6.0.4, but I
> was able to add the device manually using v 2.0.2.
>
> Phil
>
> On Thu, Nov 16, 2017 at 11:18 AM, Jan Van Kort <j.vank...@oregononline.net
> > wrote:
>
>> I had an earlier version of air control installed and gave up trying to
>> make it work over 2 years ago.  Where do i go to get a current version of
>> air control so I can try it again?  I'm wandering around the ubnt.com
>> website and can't find it.  Does the current version have the 6.04 issue?
>>
>> On 08/31/2017 11:05 AM, James Craig via Ubnt_users wrote:
>>
>> Hi Guys,
>>
>> This is most likely due to this change in discovery in 6.0.4.  We're
>> adding CGN address space in 6.0.7, so moving forward, you will only be able
>> to discover from RFC1918 and RFC6598 address. IP range scanning should
>> still work.
>>
>> - Fix: Limit discovery response to queries from private subnets or 
>> multicast/broadcast
>>
>>
>> On Thu, Aug 31, 2017 at 1:58 PM, Troy Gibson, Byhalia.net,LLC <
>> t...@byhalia.net> wrote:
>>
>>> I'm on AC2.1 beta 7 and it won't find any 6.0.4 radios, XW or XM.  I had
>>> some being monitored on beta 6, so those are still monitored, but show in
>>> devices not found column of discovery.  TCP scan only showed prism radios
>>> too.
>>>
>>> I downgraded to 5.6.15 and it was discovered.  I had to downgrade AP and
>>> CPE for it to discover the devices on AC. Now to search for the missing
>>> radios!!
>>>
>>>
>>> Troy
>>>
>>>
>>>
>>>
>>>
>>> Sent from my Verizon, Samsung Galaxy smartphone
>>>
>>>  Original message 
>>> From: CBB - Jay Fuller <par...@cyberbroadband.net>
>>> Date: 8/31/17 1:25 PM (GMT-05:00)
>>> To: Ubiquiti Users Group <ubnt_users@wispa.org>
>>> Subject: [Ubnt_users] aircontrol won't find 6.0.4 devices
>>>
>>>
>>> Been reading all about it in the ubnt forums - but anyone have any
>>> suggestions around this?
>>>
>>> Thought I'd post it here too -
>>>
>>> Haven't run aircontrol since about 18 months ago.  About nine months ago
>>> I attempted to upgrade to the then current beta but it basically corrupted
>>> my database and would not even start the server service.  Last night late I
>>> started over again from scratch.  Ran into the 6.0.4 problem as one of my
>>> network segments (from a recent purchase) we have manually changed the ip
>>> addresses and put them all on 6.0.4
>>>
>>>
>>> A different segment is still running 5.6.3.  I was planning to move them
>>> all to 6.0.4 and also make a mass change of the username / password.
>>>
>>>
>>>
>>> Left discovering overnight, found all the devices on 5.6.3 on that
>>> particular network segment but did not find any 6.0.4
>>>
>>>
>>>
>>> Today once googling and discovering this issue I downgraded an AP from
>>> 6.0.4 to 5.6.3 and discovery found it immediately.
>>>
>>>
>>>
>>> I don't want to do this to 300 devices.
>>>
>>>
>>>
>>> Aircontrol v.2.0.2.2874.170719.18353 is running on a public IP within
>>> our network.
>>>
>>>
>>>
>>> I tried to new feature tcp scan but no luck (probably because the server
>>> is in public ip space).
>>>
>>>
>>> I thought about temporarily changing the IP but then radios would be
>>> reporting to the wrong IP.
>>>
>>>
>>>
>>> I can manually add the device but have not found a way to do that in
>>> bulk.
>>>
>>>
>>>
>>> I don't know if it is easier for me to upgrade to something higher than
>>> 6.0.4 on all of my devices and use discovery or to manually add 300+
>>> devices.  I am hoping for another option.
>>>
>>>
>>>
>>> Bueller?  Bueller?
>>>
>>>
>>>
>>> Thanks
>>>
>>> ___
>>> Ubnt_users mailing list
>>> Ubnt_users@wispa.org
>>> http://lists.wispa.org/mailman/listinfo/ubnt_users
>>>
>>>
>>
>>
>> ___
>> Ubnt_users mailing 
>> listUbnt_users@wispa.orghttp://lists.wispa.org/mailman/listinfo/ubnt_users
>>
>>
>>
>> ___
>> Ubnt_users mailing list
>> Ubnt_users@wispa.org
>> http://lists.wispa.org/mailman/listinfo/ubnt_users
>>
>>
>
> ___
> Ubnt_users mailing list
> Ubnt_users@wispa.org
> http://lists.wispa.org/mailman/listinfo/ubnt_users
>
>


-- 
-RickG
___
Ubnt_users mailing list
Ubnt_users@wispa.org
http://lists.wispa.org/mailman/listinfo/ubnt_users

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[Phil Curnutt]

AirControl2 2.0.3 is found on Ubnt.com,
Support>Downloads>AirMax>Utilities.  Your have choices of Linux or
Windows10 Servers and Clients and Mac Clients.  I found our 900 radios on
5.6.9, but not the one on 6.0.4, but I was able to add the device manually
using v 2.0.2.

Phil

On Thu, Nov 16, 2017 at 11:18 AM, Jan Van Kort <j.vank...@oregononline.net>
wrote:

> I had an earlier version of air control installed and gave up trying to
> make it work over 2 years ago.  Where do i go to get a current version of
> air control so I can try it again?  I'm wandering around the ubnt.com
> website and can't find it.  Does the current version have the 6.04 issue?
>
> On 08/31/2017 11:05 AM, James Craig via Ubnt_users wrote:
>
> Hi Guys,
>
> This is most likely due to this change in discovery in 6.0.4.  We're
> adding CGN address space in 6.0.7, so moving forward, you will only be able
> to discover from RFC1918 and RFC6598 address. IP range scanning should
> still work.
>
> - Fix: Limit discovery response to queries from private subnets or 
> multicast/broadcast
>
>
> On Thu, Aug 31, 2017 at 1:58 PM, Troy Gibson, Byhalia.net,LLC <
> t...@byhalia.net> wrote:
>
>> I'm on AC2.1 beta 7 and it won't find any 6.0.4 radios, XW or XM.  I had
>> some being monitored on beta 6, so those are still monitored, but show in
>> devices not found column of discovery.  TCP scan only showed prism radios
>> too.
>>
>> I downgraded to 5.6.15 and it was discovered.  I had to downgrade AP and
>> CPE for it to discover the devices on AC. Now to search for the missing
>> radios!!
>>
>>
>> Troy
>>
>>
>>
>>
>>
>> Sent from my Verizon, Samsung Galaxy smartphone
>>
>> ---- Original message ----
>> From: CBB - Jay Fuller <par...@cyberbroadband.net>
>> Date: 8/31/17 1:25 PM (GMT-05:00)
>> To: Ubiquiti Users Group <ubnt_users@wispa.org>
>> Subject: [Ubnt_users] aircontrol won't find 6.0.4 devices
>>
>>
>> Been reading all about it in the ubnt forums - but anyone have any
>> suggestions around this?
>>
>> Thought I'd post it here too -
>>
>> Haven't run aircontrol since about 18 months ago.  About nine months ago
>> I attempted to upgrade to the then current beta but it basically corrupted
>> my database and would not even start the server service.  Last night late I
>> started over again from scratch.  Ran into the 6.0.4 problem as one of my
>> network segments (from a recent purchase) we have manually changed the ip
>> addresses and put them all on 6.0.4
>>
>>
>> A different segment is still running 5.6.3.  I was planning to move them
>> all to 6.0.4 and also make a mass change of the username / password.
>>
>>
>>
>> Left discovering overnight, found all the devices on 5.6.3 on that
>> particular network segment but did not find any 6.0.4
>>
>>
>>
>> Today once googling and discovering this issue I downgraded an AP from
>> 6.0.4 to 5.6.3 and discovery found it immediately.
>>
>>
>>
>> I don't want to do this to 300 devices.
>>
>>
>>
>> Aircontrol v.2.0.2.2874.170719.18353 is running on a public IP within our
>> network.
>>
>>
>>
>> I tried to new feature tcp scan but no luck (probably because the server
>> is in public ip space).
>>
>>
>> I thought about temporarily changing the IP but then radios would be
>> reporting to the wrong IP.
>>
>>
>>
>> I can manually add the device but have not found a way to do that in bulk.
>>
>>
>>
>> I don't know if it is easier for me to upgrade to something higher than
>> 6.0.4 on all of my devices and use discovery or to manually add 300+
>> devices.  I am hoping for another option.
>>
>>
>>
>> Bueller?  Bueller?
>>
>>
>>
>> Thanks
>>
>> ___
>> Ubnt_users mailing list
>> Ubnt_users@wispa.org
>> http://lists.wispa.org/mailman/listinfo/ubnt_users
>>
>>
>
>
> ___
> Ubnt_users mailing 
> listUbnt_users@wispa.orghttp://lists.wispa.org/mailman/listinfo/ubnt_users
>
>
>
> ___
> Ubnt_users mailing list
> Ubnt_users@wispa.org
> http://lists.wispa.org/mailman/listinfo/ubnt_users
>
>
___
Ubnt_users mailing list
Ubnt_users@wispa.org
http://lists.wispa.org/mailman/listinfo/ubnt_users

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[Jan Van Kort]

I had an earlier version of air control installed and gave up trying to 
make it work over 2 years ago.  Where do i go to get a current version 
of air control so I can try it again?  I'm wandering around the ubnt.com 
website and can't find it.  Does the current version have the 6.04 issue?



On 08/31/2017 11:05 AM, James Craig via Ubnt_users wrote:

Hi Guys,

This is most likely due to this change in discovery in 6.0.4.  We're 
adding CGN address space in 6.0.7, so moving forward, you will only be 
able to discover from RFC1918 and RFC6598 address. IP range scanning 
should still work.


- Fix: Limit discovery response to queries from private subnets or 
multicast/broadcast

On Thu, Aug 31, 2017 at 1:58 PM, Troy Gibson, Byhalia.net,LLC 
<t...@byhalia.net <mailto:t...@byhalia.net>> wrote:


I'm on AC2.1 beta 7 and it won't find any 6.0.4 radios, XW or XM. 
I had some being monitored on beta 6, so those are still

monitored, but show in devices not found column of discovery.  TCP
scan only showed prism radios too.

I downgraded to 5.6.15 and it was discovered.  I had to downgrade
AP and CPE for it to discover the devices on AC. Now to search for
the missing radios!!


Troy





Sent from my Verizon, Samsung Galaxy smartphone

 Original message 
From: CBB - Jay Fuller <par...@cyberbroadband.net
<mailto:par...@cyberbroadband.net>>
Date: 8/31/17 1:25 PM (GMT-05:00)
To: Ubiquiti Users Group <ubnt_users@wispa.org
<mailto:ubnt_users@wispa.org>>
    Subject: [Ubnt_users] aircontrol won't find 6.0.4 devices

Been reading all about it in the ubnt forums - but anyone have any
suggestions around this?
Thought I'd post it here too -
Haven't run aircontrol since about 18 months ago.  About nine
months ago I attempted to upgrade to the then current beta but it
basically corrupted my database and would not even start the
server service.  Last night late I started over again from
scratch.  Ran into the 6.0.4 problem as one of my network segments
(from a recent purchase) we have manually changed the ip addresses
and put them all on 6.0.4

A different segment is still running 5.6.3.  I was planning to
move them all to 6.0.4 and also make a mass change of the username
/ password.
Left discovering overnight, found all the devices on 5.6.3 on that
particular network segment but did not find any 6.0.4
Today once googling and discovering this issue I downgraded an AP
from 6.0.4 to 5.6.3 and discovery found it immediately.
I don't want to do this to 300 devices.
Aircontrol v.2.0.2.2874.170719.18353 is running on a public IP
within our network.
I tried to new feature tcp scan but no luck (probably because the
server is in public ip space).

I thought about temporarily changing the IP but then radios would
be reporting to the wrong IP.
I can manually add the device but have not found a way to do that
in bulk.
I don't know if it is easier for me to upgrade to something higher
than 6.0.4 on all of my devices and use discovery or to manually
add 300+ devices.  I am hoping for another option.
Bueller?  Bueller?
Thanks

___
Ubnt_users mailing list
Ubnt_users@wispa.org <mailto:Ubnt_users@wispa.org>
http://lists.wispa.org/mailman/listinfo/ubnt_users
<http://lists.wispa.org/mailman/listinfo/ubnt_users>




___
Ubnt_users mailing list
Ubnt_users@wispa.org
http://lists.wispa.org/mailman/listinfo/ubnt_users


___
Ubnt_users mailing list
Ubnt_users@wispa.org
http://lists.wispa.org/mailman/listinfo/ubnt_users

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[Rick Boucher]

Cool.  Scheduler.  Thanks!!
-


Rick Boucher
Webmaster / Systems Admin
Orcas Online / San Juan Web  
(360) 376-6411
http://www.orcasonline.com 
http://www.sanjuanweb.com
The information source for the San Juan Islands



Plans for the next day - "Work, work from early to late. In fact
I have so much to do that I shall spend the first three hours in prayer."
- Martin Luther


> On Sep 12, 2017, at 2:01 PM, Shawn C. Peppers 
>  wrote:
> 
> I just add each subnet i want to scan in the scheduler.  I program it scan 
> ever day.  I scan the whole /8 this way by separating the subnets out based 
> in what AC allows.  
> 
> Shawn C. Peppers
> Video Direct
> 866-680-8433 Toll Free
> http://www.video-direct.tv
> 
>> On Sep 12, 2017, at 3:54 PM, Rick Boucher  wrote:
>> 
>> I know I can do it manually.  The system says it can only scan so many IPs 
>> in a batch/Discovery attempt.
>> 
>> Aren’t there 256  /16 networks in 10.x.0.0/16 While I don’t use all those 
>> (obviously) I use a very few partials and it is a pain to scan all those.
>> 
>> 
>> Rick
>> 
>> -
>> 
>> 
>> Rick Boucher
>> Webmaster / Systems Admin
>> Orcas Online / San Juan Web  
>> (360) 376-6411
>> http://www.orcasonline.com 
>> http://www.sanjuanweb.com
>> The information source for the San Juan Islands
>> 
>> 
>> 
>> Plans for the next day - "Work, work from early to late. In fact
>> I have so much to do that I shall spend the first three hours in prayer."
>> - Martin Luther
>> 
>> 
>>> On Sep 12, 2017, at 1:38 PM, Shawn C. Peppers 
>>>  wrote:
>>> 
>>> Add two separate /16s? 
>>> 
>>> Shawn C. Peppers
>>> Video Direct
>>> 866-680-8433 Toll Free
>>> http://www.video-direct.tv
>>> 
 On Sep 12, 2017, at 3:29 PM, Rick Boucher  wrote:
 
 I can only add a /16.  How can you scan a /8?
 
 Rick
 -
 
 
 Rick Boucher
 Webmaster / Systems Admin
 Orcas Online / San Juan Web  
 (360) 376-6411
 http://www.orcasonline.com 
 http://www.sanjuanweb.com
 The information source for the San Juan Islands
 
 
 
 Plans for the next day - "Work, work from early to late. In fact
 I have so much to do that I shall spend the first three hours in prayer."
 - Martin Luther
 
 
> On Sep 1, 2017, at 8:18 PM, Jeremy Smith  wrote:
> 
> If you run a scan on the entire /8 subnet that you are using it should 
> find them all.  Assuming that you are only using one /8, of not then scan 
> all of them.  It isn't speedy.
> 
 
 ___
 Ubnt_users mailing list
 Ubnt_users@wispa.org
 http://lists.wispa.org/mailman/listinfo/ubnt_users
>>> ___
>>> Ubnt_users mailing list
>>> Ubnt_users@wispa.org
>>> http://lists.wispa.org/mailman/listinfo/ubnt_users
>> 
>> ___
>> Ubnt_users mailing list
>> Ubnt_users@wispa.org
>> http://lists.wispa.org/mailman/listinfo/ubnt_users
> ___
> Ubnt_users mailing list
> Ubnt_users@wispa.org
> http://lists.wispa.org/mailman/listinfo/ubnt_users

___
Ubnt_users mailing list
Ubnt_users@wispa.org
http://lists.wispa.org/mailman/listinfo/ubnt_users

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[Jeremy Smith]

I guess I haven't been.  I scan 65k IPs at a time, so also a /16.  Mistyped.  
IT definitely finds all of my 6.0.4 though, using version 2.1b7

- Original Message -
From: "Rick Boucher" <rbouc...@sanjuanweb.com>
To: "Ubiquiti Users Group" <ubnt_users@wispa.org>
Sent: Tuesday, September 12, 2017 2:29:47 PM
Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

I can only add a /16.  How can you scan a /8?

Rick
-


Rick Boucher
Webmaster / Systems Admin
Orcas Online / San Juan Web  
(360) 376-6411
http://www.orcasonline.com 
http://www.sanjuanweb.com
The information source for the San Juan Islands



Plans for the next day - "Work, work from early to late. In fact
I have so much to do that I shall spend the first three hours in prayer."
- Martin Luther


> On Sep 1, 2017, at 8:18 PM, Jeremy Smith <jsm...@bluespring.me> wrote:
> 
> If you run a scan on the entire /8 subnet that you are using it should find 
> them all.  Assuming that you are only using one /8, of not then scan all of 
> them.  It isn't speedy.
> 

___
Ubnt_users mailing list
Ubnt_users@wispa.org
http://lists.wispa.org/mailman/listinfo/ubnt_users
___
Ubnt_users mailing list
Ubnt_users@wispa.org
http://lists.wispa.org/mailman/listinfo/ubnt_users

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[Shawn C. Peppers]

I just add each subnet i want to scan in the scheduler.  I program it scan ever 
day.  I scan the whole /8 this way by separating the subnets out based in what 
AC allows.  

Shawn C. Peppers
Video Direct
866-680-8433 Toll Free
http://www.video-direct.tv

> On Sep 12, 2017, at 3:54 PM, Rick Boucher  wrote:
> 
> I know I can do it manually.  The system says it can only scan so many IPs in 
> a batch/Discovery attempt.
> 
> Aren’t there 256  /16 networks in 10.x.0.0/16 While I don’t use all those 
> (obviously) I use a very few partials and it is a pain to scan all those.
> 
> 
> Rick
> 
> -
> 
> 
> Rick Boucher
> Webmaster / Systems Admin
> Orcas Online / San Juan Web  
> (360) 376-6411
> http://www.orcasonline.com 
> http://www.sanjuanweb.com
> The information source for the San Juan Islands
> 
> 
> 
> Plans for the next day - "Work, work from early to late. In fact
> I have so much to do that I shall spend the first three hours in prayer."
> - Martin Luther
> 
> 
>> On Sep 12, 2017, at 1:38 PM, Shawn C. Peppers 
>>  wrote:
>> 
>> Add two separate /16s? 
>> 
>> Shawn C. Peppers
>> Video Direct
>> 866-680-8433 Toll Free
>> http://www.video-direct.tv
>> 
>>> On Sep 12, 2017, at 3:29 PM, Rick Boucher  wrote:
>>> 
>>> I can only add a /16.  How can you scan a /8?
>>> 
>>> Rick
>>> -
>>> 
>>> 
>>> Rick Boucher
>>> Webmaster / Systems Admin
>>> Orcas Online / San Juan Web  
>>> (360) 376-6411
>>> http://www.orcasonline.com 
>>> http://www.sanjuanweb.com
>>> The information source for the San Juan Islands
>>> 
>>> 
>>> 
>>> Plans for the next day - "Work, work from early to late. In fact
>>> I have so much to do that I shall spend the first three hours in prayer."
>>> - Martin Luther
>>> 
>>> 
 On Sep 1, 2017, at 8:18 PM, Jeremy Smith  wrote:
 
 If you run a scan on the entire /8 subnet that you are using it should 
 find them all.  Assuming that you are only using one /8, of not then scan 
 all of them.  It isn't speedy.
 
>>> 
>>> ___
>>> Ubnt_users mailing list
>>> Ubnt_users@wispa.org
>>> http://lists.wispa.org/mailman/listinfo/ubnt_users
>> ___
>> Ubnt_users mailing list
>> Ubnt_users@wispa.org
>> http://lists.wispa.org/mailman/listinfo/ubnt_users
> 
> ___
> Ubnt_users mailing list
> Ubnt_users@wispa.org
> http://lists.wispa.org/mailman/listinfo/ubnt_users
___
Ubnt_users mailing list
Ubnt_users@wispa.org
http://lists.wispa.org/mailman/listinfo/ubnt_users

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[Rick Boucher]

I know I can do it manually.  The system says it can only scan so many IPs in a 
batch/Discovery attempt.

Aren’t there 256  /16 networks in 10.x.0.0/16 While I don’t use all those 
(obviously) I use a very few partials and it is a pain to scan all those.


Rick

-


Rick Boucher
Webmaster / Systems Admin
Orcas Online / San Juan Web  
(360) 376-6411
http://www.orcasonline.com 
http://www.sanjuanweb.com
The information source for the San Juan Islands



Plans for the next day - "Work, work from early to late. In fact
I have so much to do that I shall spend the first three hours in prayer."
- Martin Luther


> On Sep 12, 2017, at 1:38 PM, Shawn C. Peppers 
>  wrote:
> 
> Add two separate /16s? 
> 
> Shawn C. Peppers
> Video Direct
> 866-680-8433 Toll Free
> http://www.video-direct.tv
> 
>> On Sep 12, 2017, at 3:29 PM, Rick Boucher  wrote:
>> 
>> I can only add a /16.  How can you scan a /8?
>> 
>> Rick
>> -
>> 
>> 
>> Rick Boucher
>> Webmaster / Systems Admin
>> Orcas Online / San Juan Web  
>> (360) 376-6411
>> http://www.orcasonline.com 
>> http://www.sanjuanweb.com
>> The information source for the San Juan Islands
>> 
>> 
>> 
>> Plans for the next day - "Work, work from early to late. In fact
>> I have so much to do that I shall spend the first three hours in prayer."
>> - Martin Luther
>> 
>> 
>>> On Sep 1, 2017, at 8:18 PM, Jeremy Smith  wrote:
>>> 
>>> If you run a scan on the entire /8 subnet that you are using it should find 
>>> them all.  Assuming that you are only using one /8, of not then scan all of 
>>> them.  It isn't speedy.
>>> 
>> 
>> ___
>> Ubnt_users mailing list
>> Ubnt_users@wispa.org
>> http://lists.wispa.org/mailman/listinfo/ubnt_users
> ___
> Ubnt_users mailing list
> Ubnt_users@wispa.org
> http://lists.wispa.org/mailman/listinfo/ubnt_users

___
Ubnt_users mailing list
Ubnt_users@wispa.org
http://lists.wispa.org/mailman/listinfo/ubnt_users

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[Shawn C. Peppers]

Add two separate /16s? 

Shawn C. Peppers
Video Direct
866-680-8433 Toll Free
http://www.video-direct.tv

> On Sep 12, 2017, at 3:29 PM, Rick Boucher  wrote:
> 
> I can only add a /16.  How can you scan a /8?
> 
> Rick
> -
> 
> 
> Rick Boucher
> Webmaster / Systems Admin
> Orcas Online / San Juan Web  
> (360) 376-6411
> http://www.orcasonline.com 
> http://www.sanjuanweb.com
> The information source for the San Juan Islands
> 
> 
> 
> Plans for the next day - "Work, work from early to late. In fact
> I have so much to do that I shall spend the first three hours in prayer."
> - Martin Luther
> 
> 
>> On Sep 1, 2017, at 8:18 PM, Jeremy Smith  wrote:
>> 
>> If you run a scan on the entire /8 subnet that you are using it should find 
>> them all.  Assuming that you are only using one /8, of not then scan all of 
>> them.  It isn't speedy.
>> 
> 
> ___
> Ubnt_users mailing list
> Ubnt_users@wispa.org
> http://lists.wispa.org/mailman/listinfo/ubnt_users
___
Ubnt_users mailing list
Ubnt_users@wispa.org
http://lists.wispa.org/mailman/listinfo/ubnt_users

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[Rick Boucher]

I can only add a /16.  How can you scan a /8?

Rick
-


Rick Boucher
Webmaster / Systems Admin
Orcas Online / San Juan Web  
(360) 376-6411
http://www.orcasonline.com 
http://www.sanjuanweb.com
The information source for the San Juan Islands



Plans for the next day - "Work, work from early to late. In fact
I have so much to do that I shall spend the first three hours in prayer."
- Martin Luther


> On Sep 1, 2017, at 8:18 PM, Jeremy Smith  wrote:
> 
> If you run a scan on the entire /8 subnet that you are using it should find 
> them all.  Assuming that you are only using one /8, of not then scan all of 
> them.  It isn't speedy.
> 

___
Ubnt_users mailing list
Ubnt_users@wispa.org
http://lists.wispa.org/mailman/listinfo/ubnt_users

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[Troy Gibson, Byhalia.net,LLC]

A.C. 2.1 beta 6 worked fine, it is beta 7 not finding the 6.0.4 radios for me.
What changed in beta 7?


Sent from my Verizon, Samsung Galaxy smartphone
 Original message From: Steve Barnes <st...@pcswin.com> Date: 
9/3/17  5:10 PM  (GMT-05:00) To: Ubiquiti Users Group <ubnt_users@wispa.org> 
Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices 


Using a 2.0 ga we set a schedule to run every night at 2am on the 3 address 
ranges we use
All new are picked up no issue.6.0.2-6.0.6 no issue.
 
Steve Barnes
Wireless Ops Manager
NLBC.com
 

From: ubnt_users-boun...@wispa.org [mailto:ubnt_users-boun...@wispa.org]
On Behalf Of RickG

Sent: Saturday, September 2, 2017 6:23 PM

To: Ubiquiti Users Group <ubnt_users@wispa.org>

Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
 

What version of AC2 are you using?


 

On Sat, Sep 2, 2017 at 11:59 AM, CBB - Jay Fuller <par...@cyberbroadband.net> 
wrote:



 


having to add each radio manually.


 



- Original Message -



From:

Jeremy Smith 


To:

Ubiquiti Users Group 


Sent: Friday, September 1, 2017 10:18 PM


Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices


 



If you run a scan on the entire /8 subnet that you are using it should find 
them all.  Assuming that you are only using one /8, of not then scan all of 
them.  It
 isn't speedy.


 





From:
"CBB - Jay Fuller" <par...@cyberbroadband.net>

To: "Ubiquiti Users Group" <ubnt_users@wispa.org>

Sent: Thursday, August 31, 2017 12:09:34 PM

Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices


 



 


I may be putting our techs to work... lol


 



- Original Message -



From:

Aaron McKillip 


To:

Ubiquiti Users Group 


Sent: Thursday, August 31, 2017 1:07 PM


Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

 

We just manually add all new radios at the end of the day. easier than 
downgrading and upgrading firmware. Really hope they get the discovery working 
on the new firmware
 soon



Aaron McKillip 

Hamilton Telecommunications


402-694-6655





On Aug 31, 2017, at 1:05 PM, CBB - Jay Fuller <par...@cyberbroadband.net> wrote:




 


My understanding is it is a code change in 6.0.4, and waiting for future 
versions of aircontrol probably won't fix it.


I just don't want to login to 300+ radios / access points to change firmware.  
Ugh!


 


I did notice you can do a broadcast from a manually entered device - but that 
does not appear to work - or it does


not find the equipment...


 


 



- Original Message -



From:
Troy Gibson, Byhalia.net,LLC



To:

Ubiquiti Users Group 


Sent: Thursday, August 31, 2017 12:58 PM


Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

 

I'm on AC2.1 beta 7 and it won't find any 6.0.4 radios, XW or XM.  I had some 
being monitored on beta 6, so those are still monitored, but show in devices 
not found
 column of discovery.  TCP scan only showed prism radios too.

 

I downgraded to 5.6.15 and it was discovered.  I had to downgrade AP and CPE 
for it to discover the devices on AC. Now to search for the missing radios!!

 

Troy












Sent from my Verizon, Samsung Galaxy smartphone


 


 Original message 


From: CBB - Jay Fuller <par...@cyberbroadband.net>



Date: 8/31/17 1:25 PM (GMT-05:00)



To: Ubiquiti Users Group <ubnt_users@wispa.org>



Subject: [Ubnt_users] aircontrol won't find 6.0.4 devices


 


 


Been reading all about it in the ubnt forums - but anyone have any suggestions 
around this?


 


Thought I'd post it here too -



 


Haven't run aircontrol since about 18 months ago.  About nine months ago I 
attempted to upgrade to the then current beta but it basically corrupted my 
database and
 would not even start the server service.  Last night late I started over again 
from scratch.  Ran into the 6.0.4 problem as one of my network segments (from a 
recent purchase) we have manually changed the ip addresses and put them all on 
6.0.4


 




A different segment is still running 5.6.3.  I was planning to move them all to 
6.0.4 and also make a mass change of the username / password.


 


 


 


Left discovering overnight, found all the devices on 5.6.3 on that particular 
network segment but did not find any 6.0.4


 


 


 


Today once googling and discovering this issue I downgraded an AP from 6.0.4 to 
5.6.3 and discovery found it immediately.


 


 


 


I don't want to do this to 300 devices.


 


 


 


Aircontrol v.2.0.2.2874.170719.18353 is running on a public IP within our 
network.


 


 


 


I tried to new feature tcp scan but no luck (probably because the server is in 
public ip space).


 




I thought about temporarily changing the IP but then radios would be reporting 
to the wrong IP.


 


 


 


I can manually add the device but have not found a way to do that in bulk.


 


 


 


I don't kno

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[Steve Barnes]

Using a 2.0 ga we set a schedule to run every night at 2am on the 3 address 
ranges we use
All new are picked up no issue.6.0.2-6.0.6 no issue.

Steve Barnes
Wireless Ops Manager
NLBC.com

From: ubnt_users-boun...@wispa.org [mailto:ubnt_users-boun...@wispa.org] On 
Behalf Of RickG
Sent: Saturday, September 2, 2017 6:23 PM
To: Ubiquiti Users Group <ubnt_users@wispa.org>
Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

What version of AC2 are you using?

On Sat, Sep 2, 2017 at 11:59 AM, CBB - Jay Fuller 
<par...@cyberbroadband.net<mailto:par...@cyberbroadband.net>> wrote:

having to add each radio manually.

- Original Message -
From: Jeremy Smith<mailto:jsm...@bluespring.me>
To: Ubiquiti Users Group<mailto:ubnt_users@wispa.org>
Sent: Friday, September 1, 2017 10:18 PM
Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

If you run a scan on the entire /8 subnet that you are using it should find 
them all.  Assuming that you are only using one /8, of not then scan all of 
them.  It isn't speedy.


From: "CBB - Jay Fuller" 
<par...@cyberbroadband.net<mailto:par...@cyberbroadband.net>>
To: "Ubiquiti Users Group" <ubnt_users@wispa.org<mailto:ubnt_users@wispa.org>>
Sent: Thursday, August 31, 2017 12:09:34 PM
Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices


I may be putting our techs to work... lol

- Original Message -
From: Aaron McKillip<mailto:aaron.mckil...@hamiltontel.com>
To: Ubiquiti Users Group<mailto:ubnt_users@wispa.org>
Sent: Thursday, August 31, 2017 1:07 PM
Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

We just manually add all new radios at the end of the day. easier than 
downgrading and upgrading firmware. Really hope they get the discovery working 
on the new firmware soon

Aaron McKillip
Hamilton Telecommunications
402-694-6655

On Aug 31, 2017, at 1:05 PM, CBB - Jay Fuller 
<par...@cyberbroadband.net<mailto:par...@cyberbroadband.net>> wrote:

My understanding is it is a code change in 6.0.4, and waiting for future 
versions of aircontrol probably won't fix it.
I just don't want to login to 300+ radios / access points to change firmware.  
Ugh!

I did notice you can do a broadcast from a manually entered device - but that 
does not appear to work - or it does
not find the equipment...


- Original Message -
From: Troy Gibson, Byhalia.net,LLC<mailto:t...@byhalia.net>
To: Ubiquiti Users Group<mailto:ubnt_users@wispa.org>
Sent: Thursday, August 31, 2017 12:58 PM
Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

I'm on AC2.1 beta 7 and it won't find any 6.0.4 radios, XW or XM.  I had some 
being monitored on beta 6, so those are still monitored, but show in devices 
not found column of discovery.  TCP scan only showed prism radios too.

I downgraded to 5.6.15 and it was discovered.  I had to downgrade AP and CPE 
for it to discover the devices on AC. Now to search for the missing radios!!

Troy




Sent from my Verizon, Samsung Galaxy smartphone

 Original message 
From: CBB - Jay Fuller 
<par...@cyberbroadband.net<mailto:par...@cyberbroadband.net>>
Date: 8/31/17 1:25 PM (GMT-05:00)
To: Ubiquiti Users Group <ubnt_users@wispa.org<mailto:ubnt_users@wispa.org>>
Subject: [Ubnt_users] aircontrol won't find 6.0.4 devices


Been reading all about it in the ubnt forums - but anyone have any suggestions 
around this?

Thought I'd post it here too -

Haven't run aircontrol since about 18 months ago.  About nine months ago I 
attempted to upgrade to the then current beta but it basically corrupted my 
database and would not even start the server service.  Last night late I 
started over again from scratch.  Ran into the 6.0.4 problem as one of my 
network segments (from a recent purchase) we have manually changed the ip 
addresses and put them all on 6.0.4


A different segment is still running 5.6.3.  I was planning to move them all to 
6.0.4 and also make a mass change of the username / password.



Left discovering overnight, found all the devices on 5.6.3 on that particular 
network segment but did not find any 6.0.4



Today once googling and discovering this issue I downgraded an AP from 6.0.4 to 
5.6.3 and discovery found it immediately.



I don't want to do this to 300 devices.



Aircontrol v.2.0.2.2874.170719.18353 is running on a public IP within our 
network.



I tried to new feature tcp scan but no luck (probably because the server is in 
public ip space).


I thought about temporarily changing the IP but then radios would be reporting 
to the wrong IP.



I can manually add the device but have not found a way to do that in bulk.



I don't know if it is easier for me to upgrade to something higher than 6.0.4 
on all of my devices and use discovery or to manually add 300+ devices.  I am 
hoping for another option.

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[RickG]

What version of AC2 are you using?

On Sat, Sep 2, 2017 at 11:59 AM, CBB - Jay Fuller <par...@cyberbroadband.net
> wrote:

>
> having to add each radio manually.
>
>
> - Original Message -
> *From:* Jeremy Smith <jsm...@bluespring.me>
> *To:* Ubiquiti Users Group <ubnt_users@wispa.org>
> *Sent:* Friday, September 1, 2017 10:18 PM
> *Subject:* Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
>
> If you run a scan on the entire /8 subnet that you are using it should
> find them all.  Assuming that you are only using one /8, of not then scan
> all of them.  It isn't speedy.
>
> --
> *From: *"CBB - Jay Fuller" <par...@cyberbroadband.net>
> *To: *"Ubiquiti Users Group" <ubnt_users@wispa.org>
> *Sent: *Thursday, August 31, 2017 12:09:34 PM
> *Subject: *Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
>
>
> I may be putting our techs to work... lol
>
>
> - Original Message -
> *From:* Aaron McKillip <aaron.mckil...@hamiltontel.com>
> *To:* Ubiquiti Users Group <ubnt_users@wispa.org>
> *Sent:* Thursday, August 31, 2017 1:07 PM
> *Subject:* Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
>
> We just manually add all new radios at the end of the day. easier than
> downgrading and upgrading firmware. Really hope they get the discovery
> working on the new firmware soon
>
> Aaron McKillip
> Hamilton Telecommunications
> 402-694-6655
>
> On Aug 31, 2017, at 1:05 PM, CBB - Jay Fuller <par...@cyberbroadband.net>
> wrote:
>
>
> My understanding is it is a code change in 6.0.4, and waiting for future
> versions of aircontrol probably won't fix it.
> I just don't want to login to 300+ radios / access points to change
> firmware.  Ugh!
>
> I did notice you can do a broadcast from a manually entered device - but
> that does not appear to work - or it does
> not find the equipment...
>
>
>
> - Original Message -
> *From:* Troy Gibson, Byhalia.net,LLC <t...@byhalia.net>
> *To:* Ubiquiti Users Group <ubnt_users@wispa.org>
> *Sent:* Thursday, August 31, 2017 12:58 PM
> *Subject:* Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
>
> I'm on AC2.1 beta 7 and it won't find any 6.0.4 radios, XW or XM.  I had
> some being monitored on beta 6, so those are still monitored, but show in
> devices not found column of discovery.  TCP scan only showed prism radios
> too.
>
> I downgraded to 5.6.15 and it was discovered.  I had to downgrade AP and
> CPE for it to discover the devices on AC. Now to search for the missing
> radios!!
>
>
> Troy
>
>
>
>
>
> Sent from my Verizon, Samsung Galaxy smartphone
>
>  Original message 
> From: CBB - Jay Fuller <par...@cyberbroadband.net>
> Date: 8/31/17 1:25 PM (GMT-05:00)
> To: Ubiquiti Users Group <ubnt_users@wispa.org>
> Subject: [Ubnt_users] aircontrol won't find 6.0.4 devices
>
>
> Been reading all about it in the ubnt forums - but anyone have any
> suggestions around this?
>
> Thought I'd post it here too -
>
> Haven't run aircontrol since about 18 months ago.  About nine months ago I
> attempted to upgrade to the then current beta but it basically corrupted my
> database and would not even start the server service.  Last night late I
> started over again from scratch.  Ran into the 6.0.4 problem as one of my
> network segments (from a recent purchase) we have manually changed the ip
> addresses and put them all on 6.0.4
>
>
> A different segment is still running 5.6.3.  I was planning to move them
> all to 6.0.4 and also make a mass change of the username / password.
>
>
>
> Left discovering overnight, found all the devices on 5.6.3 on that
> particular network segment but did not find any 6.0.4
>
>
>
> Today once googling and discovering this issue I downgraded an AP from
> 6.0.4 to 5.6.3 and discovery found it immediately.
>
>
>
> I don't want to do this to 300 devices.
>
>
>
> Aircontrol v.2.0.2.2874.170719.18353 is running on a public IP within our
> network.
>
>
>
> I tried to new feature tcp scan but no luck (probably because the server
> is in public ip space).
>
>
> I thought about temporarily changing the IP but then radios would be
> reporting to the wrong IP.
>
>
>
> I can manually add the device but have not found a way to do that in bulk.
>
>
>
> I don't know if it is easier for me to upgrade to something higher than
> 6.0.4 on all of my devices and use discovery or to manually add 300+
> devices.  I am hoping for another option.
>
>
>
> Bueller?  Bueller?
>
>
>
> Thanks
>

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[Rory Conaway]

How do you add them manually?

Rory

From: ubnt_users-boun...@wispa.org [mailto:ubnt_users-boun...@wispa.org] On 
Behalf Of CBB - Jay Fuller
Sent: Saturday, September 2, 2017 9:00 AM
To: Ubiquiti Users Group
Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices


having to add each radio manually.

- Original Message -
From: Jeremy Smith<mailto:jsm...@bluespring.me>
To: Ubiquiti Users Group<mailto:ubnt_users@wispa.org>
Sent: Friday, September 1, 2017 10:18 PM
Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

If you run a scan on the entire /8 subnet that you are using it should find 
them all.  Assuming that you are only using one /8, of not then scan all of 
them.  It isn't speedy.


From: "CBB - Jay Fuller" 
<par...@cyberbroadband.net<mailto:par...@cyberbroadband.net>>
To: "Ubiquiti Users Group" <ubnt_users@wispa.org<mailto:ubnt_users@wispa.org>>
Sent: Thursday, August 31, 2017 12:09:34 PM
Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices


I may be putting our techs to work... lol

- Original Message -
From: Aaron McKillip<mailto:aaron.mckil...@hamiltontel.com>
To: Ubiquiti Users Group<mailto:ubnt_users@wispa.org>
Sent: Thursday, August 31, 2017 1:07 PM
Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

We just manually add all new radios at the end of the day. easier than 
downgrading and upgrading firmware. Really hope they get the discovery working 
on the new firmware soon

Aaron McKillip
Hamilton Telecommunications
402-694-6655

On Aug 31, 2017, at 1:05 PM, CBB - Jay Fuller 
<par...@cyberbroadband.net<mailto:par...@cyberbroadband.net>> wrote:

My understanding is it is a code change in 6.0.4, and waiting for future 
versions of aircontrol probably won't fix it.
I just don't want to login to 300+ radios / access points to change firmware.  
Ugh!

I did notice you can do a broadcast from a manually entered device - but that 
does not appear to work - or it does
not find the equipment...


- Original Message -
From: Troy Gibson, Byhalia.net,LLC<mailto:t...@byhalia.net>
To: Ubiquiti Users Group<mailto:ubnt_users@wispa.org>
Sent: Thursday, August 31, 2017 12:58 PM
Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

I'm on AC2.1 beta 7 and it won't find any 6.0.4 radios, XW or XM.  I had some 
being monitored on beta 6, so those are still monitored, but show in devices 
not found column of discovery.  TCP scan only showed prism radios too.

I downgraded to 5.6.15 and it was discovered.  I had to downgrade AP and CPE 
for it to discover the devices on AC. Now to search for the missing radios!!

Troy




Sent from my Verizon, Samsung Galaxy smartphone

 Original message 
From: CBB - Jay Fuller 
<par...@cyberbroadband.net<mailto:par...@cyberbroadband.net>>
Date: 8/31/17 1:25 PM (GMT-05:00)
To: Ubiquiti Users Group <ubnt_users@wispa.org<mailto:ubnt_users@wispa.org>>
Subject: [Ubnt_users] aircontrol won't find 6.0.4 devices


Been reading all about it in the ubnt forums - but anyone have any suggestions 
around this?

Thought I'd post it here too -

Haven't run aircontrol since about 18 months ago.  About nine months ago I 
attempted to upgrade to the then current beta but it basically corrupted my 
database and would not even start the server service.  Last night late I 
started over again from scratch.  Ran into the 6.0.4 problem as one of my 
network segments (from a recent purchase) we have manually changed the ip 
addresses and put them all on 6.0.4


A different segment is still running 5.6.3.  I was planning to move them all to 
6.0.4 and also make a mass change of the username / password.



Left discovering overnight, found all the devices on 5.6.3 on that particular 
network segment but did not find any 6.0.4



Today once googling and discovering this issue I downgraded an AP from 6.0.4 to 
5.6.3 and discovery found it immediately.



I don't want to do this to 300 devices.



Aircontrol v.2.0.2.2874.170719.18353 is running on a public IP within our 
network.



I tried to new feature tcp scan but no luck (probably because the server is in 
public ip space).


I thought about temporarily changing the IP but then radios would be reporting 
to the wrong IP.



I can manually add the device but have not found a way to do that in bulk.



I don't know if it is easier for me to upgrade to something higher than 6.0.4 
on all of my devices and use discovery or to manually add 300+ devices.  I am 
hoping for another option.



Bueller?  Bueller?



Thanks

___
Ubnt_users mailing list
Ubnt_users@wispa.org<mailto:Ubnt_users@wispa.org>
http://lists.wispa.org/mailman/listinfo/ubnt_users
CONFIDENTIALITY NOTE: This email and any attachments are confidential and may 
be protected by legal

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[CBB - Jay Fuller]

I may be putting our techs to work... lol

  - Original Message - 
  From: Aaron McKillip 
  To: Ubiquiti Users Group 
  Sent: Thursday, August 31, 2017 1:07 PM
  Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices


  We just manually add all new radios at the end of the day. easier than 
downgrading and upgrading firmware. Really hope they get the discovery working 
on the new firmware soon

  Aaron McKillip 
  Hamilton Telecommunications
  402-694-6655

  On Aug 31, 2017, at 1:05 PM, CBB - Jay Fuller <par...@cyberbroadband.net> 
wrote:



My understanding is it is a code change in 6.0.4, and waiting for future 
versions of aircontrol probably won't fix it.
I just don't want to login to 300+ radios / access points to change 
firmware.  Ugh!

I did notice you can do a broadcast from a manually entered device - but 
that does not appear to work - or it does
not find the equipment...


  - Original Message - 
  From: Troy Gibson, Byhalia.net,LLC 
  To: Ubiquiti Users Group 
  Sent: Thursday, August 31, 2017 12:58 PM
  Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices


  I'm on AC2.1 beta 7 and it won't find any 6.0.4 radios, XW or XM.  I had 
some being monitored on beta 6, so those are still monitored, but show in 
devices not found column of discovery.  TCP scan only showed prism radios too.


  I downgraded to 5.6.15 and it was discovered.  I had to downgrade AP and 
CPE for it to discover the devices on AC. Now to search for the missing radios!!




  Troy










  Sent from my Verizon, Samsung Galaxy smartphone


   Original message 
  From: CBB - Jay Fuller <par...@cyberbroadband.net> 
  Date: 8/31/17 1:25 PM (GMT-05:00) 
  To: Ubiquiti Users Group <ubnt_users@wispa.org> 
  Subject: [Ubnt_users] aircontrol won't find 6.0.4 devices 



  Been reading all about it in the ubnt forums - but anyone have any 
suggestions around this?

  Thought I'd post it here too - 

  Haven't run aircontrol since about 18 months ago.  About nine months ago 
I attempted to upgrade to the then current beta but it basically corrupted my 
database and would not even start the server service.  Last night late I 
started over again from scratch.  Ran into the 6.0.4 problem as one of my 
network segments (from a recent purchase) we have manually changed the ip 
addresses and put them all on 6.0.4


  A different segment is still running 5.6.3.  I was planning to move them 
all to 6.0.4 and also make a mass change of the username / password.



  Left discovering overnight, found all the devices on 5.6.3 on that 
particular network segment but did not find any 6.0.4



  Today once googling and discovering this issue I downgraded an AP from 
6.0.4 to 5.6.3 and discovery found it immediately.



  I don't want to do this to 300 devices.



  Aircontrol v.2.0.2.2874.170719.18353 is running on a public IP within our 
network.



  I tried to new feature tcp scan but no luck (probably because the server 
is in public ip space).


  I thought about temporarily changing the IP but then radios would be 
reporting to the wrong IP.



  I can manually add the device but have not found a way to do that in bulk.



  I don't know if it is easier for me to upgrade to something higher than 
6.0.4 on all of my devices and use discovery or to manually add 300+ devices.  
I am hoping for another option.



  Bueller?  Bueller?



  Thanks 


--


  ___
  Ubnt_users mailing list
  Ubnt_users@wispa.org
  http://lists.wispa.org/mailman/listinfo/ubnt_users

CONFIDENTIALITY NOTE: This email and any attachments are confidential and 
may be protected by legal privilege. If you have received this email in error, 
please immediately notify the sender by return email and delete all copies of 
this email. 
___
Ubnt_users mailing list
Ubnt_users@wispa.org
http://lists.wispa.org/mailman/listinfo/ubnt_users

  CONFIDENTIALITY NOTE: This email and any attachments are confidential and may 
be protected by legal privilege. If you have received this email in error, 
please immediately notify the sender by return email and delete all copies of 
this email. 


--


  ___
  Ubnt_users mailing list
  Ubnt_users@wispa.org
  http://lists.wispa.org/mailman/listinfo/ubnt_users
___
Ubnt_users mailing list
Ubnt_users@wispa.org
http://lists.wispa.org/mailman/listinfo/ubnt_users

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[Aaron McKillip]

We just manually add all new radios at the end of the day. easier than 
downgrading and upgrading firmware. Really hope they get the discovery working 
on the new firmware soon

Aaron McKillip
Hamilton Telecommunications
402-694-6655

On Aug 31, 2017, at 1:05 PM, CBB - Jay Fuller 
<par...@cyberbroadband.net<mailto:par...@cyberbroadband.net>> wrote:


My understanding is it is a code change in 6.0.4, and waiting for future 
versions of aircontrol probably won't fix it.
I just don't want to login to 300+ radios / access points to change firmware.  
Ugh!

I did notice you can do a broadcast from a manually entered device - but that 
does not appear to work - or it does
not find the equipment...


- Original Message -
From: Troy Gibson, Byhalia.net,LLC<mailto:t...@byhalia.net>
To: Ubiquiti Users Group<mailto:ubnt_users@wispa.org>
Sent: Thursday, August 31, 2017 12:58 PM
Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

I'm on AC2.1 beta 7 and it won't find any 6.0.4 radios, XW or XM.  I had some 
being monitored on beta 6, so those are still monitored, but show in devices 
not found column of discovery.  TCP scan only showed prism radios too.

I downgraded to 5.6.15 and it was discovered.  I had to downgrade AP and CPE 
for it to discover the devices on AC. Now to search for the missing radios!!


Troy





Sent from my Verizon, Samsung Galaxy smartphone

 Original message 
From: CBB - Jay Fuller 
<par...@cyberbroadband.net<mailto:par...@cyberbroadband.net>>
Date: 8/31/17 1:25 PM (GMT-05:00)
To: Ubiquiti Users Group <ubnt_users@wispa.org<mailto:ubnt_users@wispa.org>>
Subject: [Ubnt_users] aircontrol won't find 6.0.4 devices


Been reading all about it in the ubnt forums - but anyone have any suggestions 
around this?

Thought I'd post it here too -

Haven't run aircontrol since about 18 months ago.  About nine months ago I 
attempted to upgrade to the then current beta but it basically corrupted my 
database and would not even start the server service.  Last night late I 
started over again from scratch.  Ran into the 6.0.4 problem as one of my 
network segments (from a recent purchase) we have manually changed the ip 
addresses and put them all on 6.0.4


A different segment is still running 5.6.3.  I was planning to move them all to 
6.0.4 and also make a mass change of the username / password.



Left discovering overnight, found all the devices on 5.6.3 on that particular 
network segment but did not find any 6.0.4



Today once googling and discovering this issue I downgraded an AP from 6.0.4 to 
5.6.3 and discovery found it immediately.



I don't want to do this to 300 devices.



Aircontrol v.2.0.2.2874.170719.18353 is running on a public IP within our 
network.



I tried to new feature tcp scan but no luck (probably because the server is in 
public ip space).


I thought about temporarily changing the IP but then radios would be reporting 
to the wrong IP.



I can manually add the device but have not found a way to do that in bulk.



I don't know if it is easier for me to upgrade to something higher than 6.0.4 
on all of my devices and use discovery or to manually add 300+ devices.  I am 
hoping for another option.



Bueller?  Bueller?



Thanks



___
Ubnt_users mailing list
Ubnt_users@wispa.org<mailto:Ubnt_users@wispa.org>
http://lists.wispa.org/mailman/listinfo/ubnt_users
CONFIDENTIALITY NOTE: This email and any attachments are confidential and may 
be protected by legal privilege. If you have received this email in error, 
please immediately notify the sender by return email and delete all copies of 
this email.
___
Ubnt_users mailing list
Ubnt_users@wispa.org<mailto:Ubnt_users@wispa.org>
http://lists.wispa.org/mailman/listinfo/ubnt_users
CONFIDENTIALITY NOTE: This email and any attachments are confidential and may 
be protected by legal privilege. If you have received this email in error, 
please immediately notify the sender by return email and delete all copies of 
this email.
___
Ubnt_users mailing list
Ubnt_users@wispa.org
http://lists.wispa.org/mailman/listinfo/ubnt_users

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[Josh Luthman]

The Aircontrol probably doesn't recognize that version.

If you just want to upgrade you can do that with SSH. That's what I've
always done.

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

On Aug 31, 2017 2:05 PM, "CBB - Jay Fuller" <par...@cyberbroadband.net>
wrote:

>
> My understanding is it is a code change in 6.0.4, and waiting for future
> versions of aircontrol probably won't fix it.
> I just don't want to login to 300+ radios / access points to change
> firmware.  Ugh!
>
> I did notice you can do a broadcast from a manually entered device - but
> that does not appear to work - or it does
> not find the equipment...
>
>
>
> - Original Message -
> *From:* Troy Gibson, Byhalia.net,LLC <t...@byhalia.net>
> *To:* Ubiquiti Users Group <ubnt_users@wispa.org>
> *Sent:* Thursday, August 31, 2017 12:58 PM
> *Subject:* Re: [Ubnt_users] aircontrol won't find 6.0.4 devices
>
> I'm on AC2.1 beta 7 and it won't find any 6.0.4 radios, XW or XM.  I had
> some being monitored on beta 6, so those are still monitored, but show in
> devices not found column of discovery.  TCP scan only showed prism radios
> too.
>
> I downgraded to 5.6.15 and it was discovered.  I had to downgrade AP and
> CPE for it to discover the devices on AC. Now to search for the missing
> radios!!
>
>
> Troy
>
>
>
>
>
> Sent from my Verizon, Samsung Galaxy smartphone
>
>  Original message 
> From: CBB - Jay Fuller <par...@cyberbroadband.net>
> Date: 8/31/17 1:25 PM (GMT-05:00)
> To: Ubiquiti Users Group <ubnt_users@wispa.org>
> Subject: [Ubnt_users] aircontrol won't find 6.0.4 devices
>
>
> Been reading all about it in the ubnt forums - but anyone have any
> suggestions around this?
>
> Thought I'd post it here too -
>
> Haven't run aircontrol since about 18 months ago.  About nine months ago I
> attempted to upgrade to the then current beta but it basically corrupted my
> database and would not even start the server service.  Last night late I
> started over again from scratch.  Ran into the 6.0.4 problem as one of my
> network segments (from a recent purchase) we have manually changed the ip
> addresses and put them all on 6.0.4
>
>
> A different segment is still running 5.6.3.  I was planning to move them
> all to 6.0.4 and also make a mass change of the username / password.
>
>
>
> Left discovering overnight, found all the devices on 5.6.3 on that
> particular network segment but did not find any 6.0.4
>
>
>
> Today once googling and discovering this issue I downgraded an AP from
> 6.0.4 to 5.6.3 and discovery found it immediately.
>
>
>
> I don't want to do this to 300 devices.
>
>
>
> Aircontrol v.2.0.2.2874.170719.18353 is running on a public IP within our
> network.
>
>
>
> I tried to new feature tcp scan but no luck (probably because the server
> is in public ip space).
>
>
> I thought about temporarily changing the IP but then radios would be
> reporting to the wrong IP.
>
>
>
> I can manually add the device but have not found a way to do that in bulk.
>
>
>
> I don't know if it is easier for me to upgrade to something higher than
> 6.0.4 on all of my devices and use discovery or to manually add 300+
> devices.  I am hoping for another option.
>
>
>
> Bueller?  Bueller?
>
>
>
> Thanks
>
> --
>
> ___
> Ubnt_users mailing list
> Ubnt_users@wispa.org
> http://lists.wispa.org/mailman/listinfo/ubnt_users
>
>
> ___
> Ubnt_users mailing list
> Ubnt_users@wispa.org
> http://lists.wispa.org/mailman/listinfo/ubnt_users
>
>
___
Ubnt_users mailing list
Ubnt_users@wispa.org
http://lists.wispa.org/mailman/listinfo/ubnt_users

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[James Craig via Ubnt_users]

Hi Guys,

This is most likely due to this change in discovery in 6.0.4.  We're adding
CGN address space in 6.0.7, so moving forward, you will only be able to
discover from RFC1918 and RFC6598 address. IP range scanning should still
work.

- Fix: Limit discovery response to queries from private subnets or
multicast/broadcast


On Thu, Aug 31, 2017 at 1:58 PM, Troy Gibson, Byhalia.net,LLC <
t...@byhalia.net> wrote:

> I'm on AC2.1 beta 7 and it won't find any 6.0.4 radios, XW or XM.  I had
> some being monitored on beta 6, so those are still monitored, but show in
> devices not found column of discovery.  TCP scan only showed prism radios
> too.
>
> I downgraded to 5.6.15 and it was discovered.  I had to downgrade AP and
> CPE for it to discover the devices on AC. Now to search for the missing
> radios!!
>
>
> Troy
>
>
>
>
>
> Sent from my Verizon, Samsung Galaxy smartphone
>
>  Original message 
> From: CBB - Jay Fuller <par...@cyberbroadband.net>
> Date: 8/31/17 1:25 PM (GMT-05:00)
> To: Ubiquiti Users Group <ubnt_users@wispa.org>
> Subject: [Ubnt_users] aircontrol won't find 6.0.4 devices
>
>
> Been reading all about it in the ubnt forums - but anyone have any
> suggestions around this?
>
> Thought I'd post it here too -
>
> Haven't run aircontrol since about 18 months ago.  About nine months ago I
> attempted to upgrade to the then current beta but it basically corrupted my
> database and would not even start the server service.  Last night late I
> started over again from scratch.  Ran into the 6.0.4 problem as one of my
> network segments (from a recent purchase) we have manually changed the ip
> addresses and put them all on 6.0.4
>
>
> A different segment is still running 5.6.3.  I was planning to move them
> all to 6.0.4 and also make a mass change of the username / password.
>
>
>
> Left discovering overnight, found all the devices on 5.6.3 on that
> particular network segment but did not find any 6.0.4
>
>
>
> Today once googling and discovering this issue I downgraded an AP from
> 6.0.4 to 5.6.3 and discovery found it immediately.
>
>
>
> I don't want to do this to 300 devices.
>
>
>
> Aircontrol v.2.0.2.2874.170719.18353 is running on a public IP within our
> network.
>
>
>
> I tried to new feature tcp scan but no luck (probably because the server
> is in public ip space).
>
>
> I thought about temporarily changing the IP but then radios would be
> reporting to the wrong IP.
>
>
>
> I can manually add the device but have not found a way to do that in bulk.
>
>
>
> I don't know if it is easier for me to upgrade to something higher than
> 6.0.4 on all of my devices and use discovery or to manually add 300+
> devices.  I am hoping for another option.
>
>
>
> Bueller?  Bueller?
>
>
>
> Thanks
>
> ___
> Ubnt_users mailing list
> Ubnt_users@wispa.org
> http://lists.wispa.org/mailman/listinfo/ubnt_users
>
>
___
Ubnt_users mailing list
Ubnt_users@wispa.org
http://lists.wispa.org/mailman/listinfo/ubnt_users

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[CBB - Jay Fuller]

My understanding is it is a code change in 6.0.4, and waiting for future 
versions of aircontrol probably won't fix it.
I just don't want to login to 300+ radios / access points to change firmware.  
Ugh!

I did notice you can do a broadcast from a manually entered device - but that 
does not appear to work - or it does
not find the equipment...


  - Original Message - 
  From: Troy Gibson, Byhalia.net,LLC 
  To: Ubiquiti Users Group 
  Sent: Thursday, August 31, 2017 12:58 PM
  Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices


  I'm on AC2.1 beta 7 and it won't find any 6.0.4 radios, XW or XM.  I had some 
being monitored on beta 6, so those are still monitored, but show in devices 
not found column of discovery.  TCP scan only showed prism radios too.


  I downgraded to 5.6.15 and it was discovered.  I had to downgrade AP and CPE 
for it to discover the devices on AC. Now to search for the missing radios!!




  Troy










  Sent from my Verizon, Samsung Galaxy smartphone


   Original message 
  From: CBB - Jay Fuller <par...@cyberbroadband.net> 
  Date: 8/31/17 1:25 PM (GMT-05:00) 
  To: Ubiquiti Users Group <ubnt_users@wispa.org> 
  Subject: [Ubnt_users] aircontrol won't find 6.0.4 devices 



  Been reading all about it in the ubnt forums - but anyone have any 
suggestions around this?

  Thought I'd post it here too - 

  Haven't run aircontrol since about 18 months ago.  About nine months ago I 
attempted to upgrade to the then current beta but it basically corrupted my 
database and would not even start the server service.  Last night late I 
started over again from scratch.  Ran into the 6.0.4 problem as one of my 
network segments (from a recent purchase) we have manually changed the ip 
addresses and put them all on 6.0.4


  A different segment is still running 5.6.3.  I was planning to move them all 
to 6.0.4 and also make a mass change of the username / password.



  Left discovering overnight, found all the devices on 5.6.3 on that particular 
network segment but did not find any 6.0.4



  Today once googling and discovering this issue I downgraded an AP from 6.0.4 
to 5.6.3 and discovery found it immediately.



  I don't want to do this to 300 devices.



  Aircontrol v.2.0.2.2874.170719.18353 is running on a public IP within our 
network.



  I tried to new feature tcp scan but no luck (probably because the server is 
in public ip space).


  I thought about temporarily changing the IP but then radios would be 
reporting to the wrong IP.



  I can manually add the device but have not found a way to do that in bulk.



  I don't know if it is easier for me to upgrade to something higher than 6.0.4 
on all of my devices and use discovery or to manually add 300+ devices.  I am 
hoping for another option.



  Bueller?  Bueller?



  Thanks 


--


  ___
  Ubnt_users mailing list
  Ubnt_users@wispa.org
  http://lists.wispa.org/mailman/listinfo/ubnt_users
___
Ubnt_users mailing list
Ubnt_users@wispa.org
http://lists.wispa.org/mailman/listinfo/ubnt_users

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[CBB - Jay Fuller]

I have chosen to go the 2.4 ac route... :)
at least for now

  - Original Message - 
  From: Josh Luthman 
  To: Ubiquiti Users Group 
  Sent: Thursday, August 31, 2017 12:27 PM
  Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices


  Epmp elevate


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


  On Aug 31, 2017 1:25 PM, "CBB - Jay Fuller" <par...@cyberbroadband.net> wrote:


Been reading all about it in the ubnt forums - but anyone have any 
suggestions around this?

Thought I'd post it here too - 

Haven't run aircontrol since about 18 months ago.  About nine months ago I 
attempted to upgrade to the then current beta but it basically corrupted my 
database and would not even start the server service.  Last night late I 
started over again from scratch.  Ran into the 6.0.4 problem as one of my 
network segments (from a recent purchase) we have manually changed the ip 
addresses and put them all on 6.0.4


A different segment is still running 5.6.3.  I was planning to move them 
all to 6.0.4 and also make a mass change of the username / password.



Left discovering overnight, found all the devices on 5.6.3 on that 
particular network segment but did not find any 6.0.4



Today once googling and discovering this issue I downgraded an AP from 
6.0.4 to 5.6.3 and discovery found it immediately.



I don't want to do this to 300 devices.



Aircontrol v.2.0.2.2874.170719.18353 is running on a public IP within our 
network.



I tried to new feature tcp scan but no luck (probably because the server is 
in public ip space).


I thought about temporarily changing the IP but then radios would be 
reporting to the wrong IP.



I can manually add the device but have not found a way to do that in bulk.



I don't know if it is easier for me to upgrade to something higher than 
6.0.4 on all of my devices and use discovery or to manually add 300+ devices.  
I am hoping for another option.



Bueller?  Bueller?



Thanks 

___
Ubnt_users mailing list
Ubnt_users@wispa.org
http://lists.wispa.org/mailman/listinfo/ubnt_users




--


  ___
  Ubnt_users mailing list
  Ubnt_users@wispa.org
  http://lists.wispa.org/mailman/listinfo/ubnt_users
___
Ubnt_users mailing list
Ubnt_users@wispa.org
http://lists.wispa.org/mailman/listinfo/ubnt_users

Re: [Ubnt_users] aircontrol won't find 6.0.4 devices

[Josh Luthman]

Epmp elevate

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

On Aug 31, 2017 1:25 PM, "CBB - Jay Fuller" 
wrote:

>
> Been reading all about it in the ubnt forums - but anyone have any
> suggestions around this?
>
> Thought I'd post it here too -
>
> Haven't run aircontrol since about 18 months ago.  About nine months ago I
> attempted to upgrade to the then current beta but it basically corrupted my
> database and would not even start the server service.  Last night late I
> started over again from scratch.  Ran into the 6.0.4 problem as one of my
> network segments (from a recent purchase) we have manually changed the ip
> addresses and put them all on 6.0.4
>
>
> A different segment is still running 5.6.3.  I was planning to move them
> all to 6.0.4 and also make a mass change of the username / password.
>
>
>
> Left discovering overnight, found all the devices on 5.6.3 on that
> particular network segment but did not find any 6.0.4
>
>
>
> Today once googling and discovering this issue I downgraded an AP from
> 6.0.4 to 5.6.3 and discovery found it immediately.
>
>
>
> I don't want to do this to 300 devices.
>
>
>
> Aircontrol v.2.0.2.2874.170719.18353 is running on a public IP within our
> network.
>
>
>
> I tried to new feature tcp scan but no luck (probably because the server
> is in public ip space).
>
>
> I thought about temporarily changing the IP but then radios would be
> reporting to the wrong IP.
>
>
>
> I can manually add the device but have not found a way to do that in bulk.
>
>
>
> I don't know if it is easier for me to upgrade to something higher than
> 6.0.4 on all of my devices and use discovery or to manually add 300+
> devices.  I am hoping for another option.
>
>
>
> Bueller?  Bueller?
>
>
>
> Thanks
>
> ___
> Ubnt_users mailing list
> Ubnt_users@wispa.org
> http://lists.wispa.org/mailman/listinfo/ubnt_users
>
>
___
Ubnt_users mailing list
Ubnt_users@wispa.org
http://lists.wispa.org/mailman/listinfo/ubnt_users

[Ubnt_users] aircontrol won't find 6.0.4 devices

[CBB - Jay Fuller]

Been reading all about it in the ubnt forums - but anyone have any suggestions 
around this?

Thought I'd post it here too - 

Haven't run aircontrol since about 18 months ago.  About nine months ago I 
attempted to upgrade to the then current beta but it basically corrupted my 
database and would not even start the server service.  Last night late I 
started over again from scratch.  Ran into the 6.0.4 problem as one of my 
network segments (from a recent purchase) we have manually changed the ip 
addresses and put them all on 6.0.4


A different segment is still running 5.6.3.  I was planning to move them all to 
6.0.4 and also make a mass change of the username / password.

 

Left discovering overnight, found all the devices on 5.6.3 on that particular 
network segment but did not find any 6.0.4

 

Today once googling and discovering this issue I downgraded an AP from 6.0.4 to 
5.6.3 and discovery found it immediately.

 

I don't want to do this to 300 devices.

 

Aircontrol v.2.0.2.2874.170719.18353 is running on a public IP within our 
network.

 

I tried to new feature tcp scan but no luck (probably because the server is in 
public ip space).


I thought about temporarily changing the IP but then radios would be reporting 
to the wrong IP.

 

I can manually add the device but have not found a way to do that in bulk.

 

I don't know if it is easier for me to upgrade to something higher than 6.0.4 
on all of my devices and use discovery or to manually add 300+ devices.  I am 
hoping for another option.

 

Bueller?  Bueller?

 

Thanks ___
Ubnt_users mailing list
Ubnt_users@wispa.org
http://lists.wispa.org/mailman/listinfo/ubnt_users