I'd say it's possible, the basic Cambium HTTP server may not be designed to
survive pubic brute-forcing.

On Thu, Apr 7, 2016 at 10:09 PM, Craig House <[email protected]>
wrote:

> These devices are on public IP's .  Our upstream for this tower just
> recently changed a bunch of routing and firewall stuff.  Is it possible
> this is a brute force attempt that is overloading the radios in this subnet
> and causing the to reboot ??
>
> Craig
>
>
> ------------------------------
> *From: *"Colin Stanners" <[email protected]>
> *To: *[email protected]
> *Sent: *Thursday, April 7, 2016 10:03:18 PM
> *Subject: *Re: [AFMUG] Odd power cycling issues
>
> Could it be a problem with the GPS sync that's making the water tower
> reboot? As for the slave rebooting could be an old software bug?
>
> On Thu, Apr 7, 2016 at 9:55 PM, Craig House <[email protected]>
> wrote:
>
>> I know this is old legacy FSK equipment but it is what is on the tower so
>> we have an odd situation going on.
>>
>> Water tower fed with a 5.2 BH20 link from a bank that is 800' away.  Only
>> equipment in use on the tower is a 900 omni.  The Master BH and the 900
>> omni are on a CMM at the base of the tower.  For the last few days the
>> equipment will reboot itself every 60 minutes or less on average.   Not so
>> odd that the CMM and the equipment on the tower reboots but so does the
>> slave Bh at the bank at the exact same time.   OK  I thought Power issues,
>> I replaced the UPS at the base of the tower.  Problem still persists.  I
>> can find no place where the equipment can have a ping watchdog and there is
>> not a web power switch at the base of the tower either.  The odd part is
>> that out of desperation I logged into the AP and the CMM and factory
>> defaulted the devices and reconfigured them.  When I rebooted the CMM to
>> apply the reconfiguration, the Remote BH power cycled at the same exact
>> time.   This equipment has been in service for over 2 years and is running
>> old firmware 9.3 on the BH20's but have never been a problem until now.   I
>> even changed the passwords thinking someone might be accessing them and
>> causing these issues but I'm stumped.
>>
>> Craig
>>
>
>
>

Reply via email to