<customers radios on public IP> --- (big hairy internet) --- <NAT 
ROUTER> --- (my office with several virtual servers running services 
including AirControl)

I don't think I'll overload the router. :)

ryan

On 10/19/2011 9:23 AM, Josh Luthman wrote:
> That seems like you're asking for trouble.  I wouldn't masquerade
> between the AirControl server and the radios themselves - that is a
> ton of overhead.
>
> Josh Luthman
> Office: 937-552-2340
> Direct: 937-552-2343
> 1100 Wayne St
> Suite 1337
> Troy, OH 45373
>
>
>
> On Wed, Oct 19, 2011 at 12:17 PM, Ryan Spott<rsp...@irongoat.net>  wrote:
>> Admin Tab ->  System Settings ->  Air Control Server Address
>> Make sure this is an IP address. If not then your CPE will fail to talk to
>> your server. It obviously needs to be the wan port of your router.
>>
>> I ran into this while listening to the UBNT talk. I was trying to add a
>> bunch of CPE and found that they would not talk to my server behind NAT. I
>> figured since a DNS server is a forced settings item the CPE would do
>> nslookup for the proper server. They don't!
>>
>> ryan
>>
>>
>> On 10/19/2011 8:50 AM, Josh Luthman wrote:
>>> Too many Air products.
>>>
>>> If you're doing a broadcast discovery they need to be in the same
>>> collision domain, same interface of the router, etc.  I expect you're
>>> probably trying that and they are on a different collision domain so
>>> what you do is add an IP range in the scan box (ie 10.10.10.0/24 and
>>> 172.16.2.0/24 and 192.168.233.0/24)
>>>
>>> Josh Luthman
>>> Office: 937-552-2340
>>> Direct: 937-552-2343
>>> 1100 Wayne St
>>> Suite 1337
>>> Troy, OH 45373
>>>
>>>
>>>
>>> On Wed, Oct 19, 2011 at 11:48 AM, Patrick D. Nix, Jr
>>> <pni...@cnetworksolutions.com>    wrote:
>>>> Cameras? No cameras, just managing the APs and CPEs.  All of my APs are
>>>> added as infrastructure already, still not working.  Are there any
>>>> additional ports that need to be open to establish communication?
>>>>
>>>> Patrick Nix, Jr.,
>>>> Computer Network Solutions
>>>> CSWEB.NET Internet Services
>>>> IT Manager
>>>> http://www.cnetworksolutions.com
>>>> http://www.csweb.net
>>>> (918) 235-0414
>>>>
>>>>
>>>> Attention: This e-mail and any attachments may contain confidential and
>>>> privileged information. If you are not the intended recipient, please 
>>>> notify
>>>> the sender immediately by return e-mail, delete this e-mail and destroy any
>>>> copies. Any dissemination or use of this information by a person other than
>>>> the intended recipient is unauthorized and may be illegal.
>>>>
>>>> -----Original Message-----
>>>> From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On
>>>> Behalf Of Josh Luthman
>>>> Sent: Wednesday, October 19, 2011 10:41 AM
>>>> To: WISPA General List
>>>> Subject: Re: [WISPA] Aircontrol for UBNT
>>>>
>>>> Just add the cameras as infrastructure.  It's the easiest way and best
>>>> way (it's documented!!!)
>>>>
>>>> Josh Luthman
>>>> Office: 937-552-2340
>>>> Direct: 937-552-2343
>>>> 1100 Wayne St
>>>> Suite 1337
>>>> Troy, OH 45373
>>>>
>>>>
>>>>
>>>> On Wed, Oct 19, 2011 at 11:39 AM, Patrick D. Nix, Jr
>>>> <pni...@cnetworksolutions.com>    wrote:
>>>>> Having trouble establishing communication to radios via aircontrol.  It
>>>>> is
>>>>> definitely an issue with our firewall (using a imagestream rebel running
>>>>> iptables via powercode) because when I initiate a rebuild the
>>>>> communication
>>>>> comes up after the services process it goes down again.  I already have
>>>>> port
>>>>> 22 and port 9080 open.  Any ideas?
>>>>>
>>>>>
>>>>>
>>>>> Pat
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --------------------------------------------------------------------------------
>>>>> WISPA Wants You! Join today!
>>>>> http://signup.wispa.org/
>>>>>
>>>>> --------------------------------------------------------------------------------
>>>>>
>>>>> WISPA Wireless List: wireless@wispa.org
>>>>>
>>>>> Subscribe/Unsubscribe:
>>>>> http://lists.wispa.org/mailman/listinfo/wireless
>>>>>
>>>>> Archives: http://lists.wispa.org/pipermail/wireless/
>>>>>
>>>>
>>>> --------------------------------------------------------------------------------
>>>> WISPA Wants You! Join today!
>>>> http://signup.wispa.org/
>>>>
>>>> --------------------------------------------------------------------------------
>>>>
>>>> WISPA Wireless List: wireless@wispa.org
>>>>
>>>> Subscribe/Unsubscribe:
>>>> http://lists.wispa.org/mailman/listinfo/wireless
>>>>
>>>> Archives: http://lists.wispa.org/pipermail/wireless/
>>>>
>>>>
>>>>
>>>> --------------------------------------------------------------------------------
>>>> WISPA Wants You! Join today!
>>>> http://signup.wispa.org/
>>>>
>>>> --------------------------------------------------------------------------------
>>>>
>>>> WISPA Wireless List: wireless@wispa.org
>>>>
>>>> Subscribe/Unsubscribe:
>>>> http://lists.wispa.org/mailman/listinfo/wireless
>>>>
>>>> Archives: http://lists.wispa.org/pipermail/wireless/
>>>>
>>>
>>> --------------------------------------------------------------------------------
>>> WISPA Wants You! Join today!
>>> http://signup.wispa.org/
>>>
>>> --------------------------------------------------------------------------------
>>>
>>> WISPA Wireless List: wireless@wispa.org
>>>
>>> Subscribe/Unsubscribe:
>>> http://lists.wispa.org/mailman/listinfo/wireless
>>>
>>> Archives: http://lists.wispa.org/pipermail/wireless/
>>



--------------------------------------------------------------------------------
WISPA Wants You! Join today!
http://signup.wispa.org/
--------------------------------------------------------------------------------
 
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

Reply via email to