PDA

View Full Version : Looking for a list of capabilities


neofast
09-03-2009, 01:54 AM
I've not had any bullet M's, etc. But, my network is...errr, dependent heavily upon routing and dhcp built into my clients.

Is there a list of networking and other capabilities that these have?

routing
firewall
dhcp static assignments handed to clients by the AP
How does client end handle DNS?

how does it handle noise?

Does it include such chip based features as compression and similar "super" features like the Atheros chipsets have?



Is there some means of extending the range of the clients? The little nano has a really REALLY small antenna, and I'm rural... I normally use 23 -26 db client antennas for 5 ghz, and 16 - 19 db antennas at 2.4, as a lot of my clients are well into the 20's (miles) for distance. I need 12 miles or so for 5 ghz and 30 for 2.4.

How is this accomplished with nanos or rockets?

Thanks.

UBNT-Mike.Ford
09-03-2009, 09:42 AM
I've not had any bullet M's, etc. But, my network is...errr, dependent heavily upon routing and dhcp built into my clients.

Is there a list of networking and other capabilities that these have?

routing
firewall
dhcp static assignments handed to clients by the AP
How does client end handle DNS?

how does it handle noise?

Does it include such chip based features as compression and similar "super" features like the Atheros chipsets have?



Is there some means of extending the range of the clients? The little nano has a really REALLY small antenna, and I'm rural... I normally use 23 -26 db client antennas for 5 ghz, and 16 - 19 db antennas at 2.4, as a lot of my clients are well into the 20's (miles) for distance. I need 12 miles or so for 5 ghz and 30 for 2.4.

How is this accomplished with nanos or rockets?

Thanks.


Hello,

1. We support basic firewall functionality. At thistime we do not have WeB GUI based routing. It does support STP however.

2. DHCP is generally handled from your NOC.

3. The DNS is supplied by your DHCP server.

4. There are no "Super" feature in the 11n protocol.

5. For these long links you would use Rockets or Bullet's attached to grid or dish style antennas.

Thanks,

Mike

neofast
09-03-2009, 12:36 PM
Hello,

1. We support basic firewall functionality. At thistime we do not have WeB GUI based routing. It does support STP however.

2. DHCP is generally handled from your NOC.

3. The DNS is supplied by your DHCP server.

4. There are no "Super" feature in the 11n protocol.



Mike

I do not have a "NOC" in the typical sense of the word. My network is scattered over many hundreds of square miles, and the traffic routes through provider connections, not through any central point.

My equipment now, does the dhcp for me, right at the ap, so that traffic blockages to somewhere else do not cause an outage.

Why no routing? That's inexcusable, really. bridging a large, high traffic network? come on. My current access points, which have up to 5 radios each, do all the routing, dhcp, and can even do RIP or OSPF or OLSR and include BGP functionality.

Many of my sites do not have AC power, and I am extremely sensitive to power useage because of this. Typically, we're powering up to 8 radios (links in/out, access points) at a site and using less than 30 watts of power, average.

These are advertised as "carrier class", and the advertised performance seems to be so, but you're lacking some very basic functionality for a wholly wireless network. Please consider adding at least some of the basic networking functionality.

neofast
09-03-2009, 12:40 PM
Hello,


5. For these long links you would use Rockets or Bullet's attached to grid or dish style antennas.
Mike

Are there antenna guidelines, requirements, etc? Presumably there's some needs as it concerns the horizontal and vertical planes of the receiving elements - their individual distances from the access point, etc.

CzechEnglishFrenchGermanItalianPolishPortugueseRussianSpanish
Translated to other languages supported by vB Enterprise Translator 3.5.4