I had this idea today since many of us are always trying to put really fast computers on tall towers and often times fall prey to heat problems and reliability. The RB532's of today aren't fast enough to run an NStreme AP. And it's far too expensive to mount 4 or 5 P4's on a tower just for redundancy sake (I hate having a single AP computer that is the primary source for failure on a tower). We're always struggling trying 533mhz VIA C3's and such, when a RB532 CAN do it but can't do it and everything else too.
So I propose a "dumb" software AP running on an RB112 or RB532 - one that uses a faster, ethernet connected "controller" Mikrotik that could be mounted indoors in the tower control room, that can control multiple "dumb" AP's. This could be a way to move towards a GPS synchronized AP NStreme cluster. I would hope that it would be possible to use 2 controllers to support a failover arrangement as well. This could also be used for backhauls as well - so everything comes into the controller computer as raw data from these APs & links, and it takes care of all of the heavy processing tasks, while the dumb AP's do nothing other than bridge packets between themselves and the actual controller.
I'm not proposing to make a new distribution, but rather a simple package set, on the dumb AP, system + wireless-remote, designed to do nothing more than send raw data (not IP but actual 802.11 raw data) back and forth between a faster computer mounted below.
On the controller, system + wireless-controller + all the other packages, that is designed to take care of authentication, encryption, packet aggregation, routing, bridging, conn-track, etc (all of the CPU intensive tasks), and acts as if it were just another interface (RemoteWLAN as an idea). So you can have a tower with 6 AP's on it, and the machine below will list 6 "virtual" remote AP's above, and do everything for those APs.
Any thoughts on this?