That's basically how I've been monitoring our Ubiquiti stuff for years. It's a pretty simple way to go, you just need some mechanism to get the scripts onto the radios.
________________________________ From: [email protected] [[email protected]] on behalf of Kristian Hoffmann [[email protected]] Sent: Wednesday, December 03, 2014 3:45 PM To: WISPA General List Subject: Re: [WISPA] groundcontrol project Right, so you can scrape the data from /proc, iwinfo, or wherever else, you can push that back to the server using some kind of HTTP call. It just depends on what's handy and what they've included in their busybox build. Like... #!/bin/sh cat /proc/net/wireless | grep ath | sed 's/[ ]\+/,/g' | while read ATHSTAT; do wget -O /dev/null "http://gcserver/stat?dev=foo&athstats=$ATHSTAT";<http://gcserver/stat?dev=foo&athstats=$ATHSTAT> done -Kristian On 12/03/2014 01:21 PM, Josh Reynolds wrote: The idea is that we're going to pull stuff from the radios that aren't even exposed via the GUIs... josh reynolds :: chief information officer spitwspots :: www.spitwspots.com<http://www.spitwspots.com> On 12/03/2014 12:14 PM, Kristian Hoffmann wrote: For at least MikroTik and Ubnt devices, you could push the stats from the device to the server with a REST call using wget and /tool fetch, respectively. For everything else, you're probably going to have to just poll with SNMP, which isn't (shouldn't be) terrible and would be the most widely supported approach. -Kristian On 12/03/2014 01:10 PM, Josh Reynolds wrote: Mmmm there's still ssh keys in devices that are used for C&C to AC2 severs. They did build a "custom protocol" that runs inside that tunnel though. josh reynolds :: chief information officer spitwspots :: www.spitwspots.com<http://www.spitwspots.com> On 12/03/2014 12:07 PM, Mathew Howard wrote: Didn't they change the provisioning mechanism in aircontrol 2? I thought they had moved from SSH to something that was supposed to be more efficient. ________________________________ From: [email protected]<mailto:[email protected]> [[email protected]<mailto:[email protected]>] on behalf of Josh Reynolds [[email protected]<mailto:[email protected]>] Sent: Wednesday, December 03, 2014 2:56 PM To: [email protected]<mailto:[email protected]> Subject: Re: [WISPA] groundcontrol project I've done a bit of work previously to reverse engineering the provisioning mechanism, and I see nothing that would be a problem collecting stats via that method. You'd still have to use groundcontrol to initially connect/provision the units first to exchange SSH keys, and you'd want it to be on a different ip that your previous aircontrol server. A nasty thing about ubnt provisioning... if you replace the server on the same ip or a different ip, all of the radios that were previously provisioned will always try to connect to the old ip/server, which causes quite a bit of arp traffic. .... one thing I'd like to do is create a "cleanup tool" for that, though pssh (parallel ssh) + wireshark helped me clean up that mess "manually" in the past. josh reynolds :: chief information officer spitwspots :: www.spitwspots.com<http://www.spitwspots.com> On 12/03/2014 11:09 AM, Randy Cosby wrote: Would it pay to see if UBNT would allow us to continue to use some of the provisioning mechanisms built into the radios for aircontrol? It's nice to have subscriber units "phone home." On 12/3/2014 12:39 PM, Jay Weekley wrote: I was wondering if that might come about. Maybe another wisp that uses their own software might offer something. Mike Hammett wrote: Further driven by today's post that summed up says, "We don't care what you want. This is what you get." ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com ------------------------------------------------------------------------ *From: *"Josh Reynolds" <[email protected]><mailto:[email protected]> *To: *"WISPA General List" <[email protected]><mailto:[email protected]>, "Ubiquiti Users Group" <[email protected]><mailto:[email protected]>, [email protected]<mailto:[email protected]> *Sent: *Wednesday, December 3, 2014 1:19:23 PM *Subject: *[WISPA] groundcontrol project For those of you who haven't heard, several of us started a new project yesterday. https://github.com/esseph/groundcontrol Licensing is tentatively set as falling under GPLv2. We have already been offered code snippets, a dev box, a db server, and several people have decided to volunteer time to make this happen. The initial idea is that the system itself will be free, with a possibly paid support/features option, or maybe a model similar to observium where the is a "community" (free as in beer) version that comes out every 6mo or so, and a "paid" version with newer features and direct support. We're not sure yet, but we want to make this project accessible and fairly vendor-neutral. If any of you could volunteer time, support, code, documentation, ideas, etc.it would be greatly appreciated. This is a project by and for the WISP community. Thank you! -- josh reynolds :: chief information officer spitwspots ::www.spitwspots.com _______________________________________________ Wireless mailing list [email protected]<mailto:[email protected]> http://lists.wispa.org/mailman/listinfo/wireless _______________________________________________ Wireless mailing list [email protected]<mailto:[email protected]> http://lists.wispa.org/mailman/listinfo/wireless _______________________________________________ Wireless mailing list [email protected]<mailto:[email protected]> http://lists.wispa.org/mailman/listinfo/wireless -- [cid:[email protected]]<http://www.infowest.com/> Randy Cosby InfoWest, Inc 435-674-0165 x 2010 infowest.com<http://www.infowest.com/> This e-mail message contains information from InfoWest, Inc and is for the sole use of the intended recipient(s) and may contain privileged, proprietary or confidential information. Unauthorized use, distribution, review or disclosure is prohibited. If you are not the intended recipient, please contact [email protected]<mailto:[email protected]> by reply email and destroy the original message, all attachments and copies. _______________________________________________ Wireless mailing list [email protected]<mailto:[email protected]> http://lists.wispa.org/mailman/listinfo/wireless _______________________________________________ Wireless mailing list [email protected]<mailto:[email protected]> http://lists.wispa.org/mailman/listinfo/wireless _______________________________________________ Wireless mailing list [email protected]<mailto:[email protected]> http://lists.wispa.org/mailman/listinfo/wireless _______________________________________________ Wireless mailing list [email protected]<mailto:[email protected]> http://lists.wispa.org/mailman/listinfo/wireless _______________________________________________ Wireless mailing list [email protected]<mailto:[email protected]> http://lists.wispa.org/mailman/listinfo/wireless
_______________________________________________ Wireless mailing list [email protected] http://lists.wispa.org/mailman/listinfo/wireless
