@Dashrender said:

If they are all on the same controller, why does rebooting affect the others? Isn't the controller suppose to managing that?

The point of auto is to have the AP detect what channels are in use around it and pick the best one. That will obviously be different each time any AP reboots. When the first one reboots, it will immediately affect the ones next to it as the signal drops and the unit around it detect a difference. Then once it powers back on, it has to detect what is around it and then determine what channel to use.

High density deployments are much different beasts than an office building with 3 or 4 AP scattered around for coverage.

MPLS capable - that will be interesting!

Good night.

@anonymous said:

Just rebooted 2 more times, no luck. It's a ER-X if that makes any difference.

You have to have offload enabled. A number of things disable the offloading of some packets. Including certain QoS.

http://community.ubnt.com/t5/EdgeMAX/v1-7-0-Wondering-why-traffic-is-not-showing-up-in-the-new-quot/m-p/1287642#U1287642

I have to change my mtu to 1350 I think on 3G. I've seen TCP Window scaling cause similar issues as well (and along with) MTU issues, But I would hope never devices would have issues with it as they both seem to be new enough.

Most WISPs are heavily using Ubquiti Geard (as well a Tranzeo, and Motorola). Many of the WISPs include the cost of a wireless router in the install price because they generally do double natting internally and they want something they've tested to work with their systems. It's better for them to spend a little more (even if it is billed to the customer) up front a make sure they know it will work/the customer should be happy. I can see this being heavily used for home connections with WISPs espcially since they can just power both the Outdoor AP and the router off the Passive POE. I'm not sure what they were thinking for the indoor AP. I think it would have done better if they put just a cheap 2.4/5ghz N AP into the router for the home users.