On Mon, Feb 2, 2015 at 11:44 AM, Björn Smedman <bs@xxxxxxxxx> wrote: > On Mon, Feb 2, 2015 at 5:21 AM, Avery Pennarun <apenwarr@xxxxxxxxxx> wrote: >> While there is definitely some work to be done in handoff, it seems >> like there are some find implementations of this already in existence. >> Several brands of "enterprise access point" setups seem to do well at >> this. It would be nice if they interoperated, I guess. >> >> The fact that there's no open source version of this kind of handoff >> feature bugs me, but we are working on it here and the work is all >> planned to be open source, for example: (very early version) >> https://gfiber.googlesource.com/vendor/google/platform/+/master/waveguide/ > > We've got an SDN-inspired architecture with 802.11 frame tunneling (a > la CAPWAP), airtime fairness, infrastructure initiated hand-over, > Opportunistic Key Caching (OKC), IEEE 802.11r Fast BSS Transition and > a few more goodies. It's currently free as in beer > (http://anyfi.net/software, > https://github.com/carrierwrt/carrierwrt/pull/7 and > http://www.anyfinetworks.com/download) up to 100 APs, but we're > definitely going to open source in one form or another. > > We've also tried to raise some interest in fixing up CAPWAP > (https://www.ietf.org/mail-archive/web/opsawg/current/msg03196.html), > which is (unfortunately) the best open standard at the moment. > Interest seems marginal though... This sounds cool. Is the CAPWAP/encapsulation stuff separable from the rest? At 802.11ac speeds, a super fast WAN link, and a low-cost SoC, too many layers can be a killer. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
