On Thu, Mar 21, 2013 at 11:31 AM, wrote: > Down at the local Cambridge Micro Center there is a whole pile of new > 3800's. But knowing what Netgear does, this might be a completely > different hardware platform that is incompatible. How does one tell that > it's the right version, in case I want to buy another... (don't know at > this time if I do). > We've only seen one variant of the 3800, so we expect they should be fine. > > > Honestly, my main interest is that I'd like to see 802.11ac supported on > one of the new routers from Netgear or Cisco - but I suspect that the > drivers are probably not easy to get working on Linux. > The thing to do is to find routers based on the Qualcomm Atheros chipset: they've been best about Linux support in open source (as opposed to binary blobs to fit into specific versions of Linux). Even then, validating the driver is a significant amount of work. In the last couple years, broadcom open source driver support has improved, but IIRC, it is still a softmac device and has a blob of firmware, that is not trustworthy. - Jim > > > > > > > > > > -----Original Message----- > From: "Dave Taht" > Sent: Thursday, March 21, 2013 11:19am > To: cerowrt-devel@lists.bufferbloat.net > Subject: [Cerowrt-devel] Buffalo WZR-600DHP (updated WZR-HP-AG300H) > > Given how difficult it is becoming to get 3800s, a device with the > most similar chipset is this one. > > Anyone tried it? They were in use at the other two openwrt based demos at > ietf. > > I am working on getting a steady supply of 3800 refurbs and on other > alternative hardware. > > I note that unless major bugs show up in cerowrt, I'm not planning on > spinning up a new dev cycle until after Linux 3.8 is stable-ish > ... and not until after someone else steps up to be the new > buildmaster, and not until supplies of something suitable are assured. > > About the only major cerowrt thing I need to do in the coming weeks is > start pushing up the stuff to openwrt that works, maybe getting it > also into hipnet, and getting cake restarted. > > As I'll be travelling for the next 2 months - I kind of expect most of > what I'll be coding is prototyping code on x86, if that. > > (note - that doesn't mean development and CI are going to stop, > (although I do need a break), it just means I'm hoping you all enjoy > the current release as is, more than constantly upgrading.) > > Certainly get your feature requests in! What else needs to get into > this puppy to make it rock on ipv6 and naming and bufferbloat and > whatever else you need? > > -- > Dave Täht > > Fixing bufferbloat with cerowrt: > http://www.teklibre.com/cerowrt/subscribe.html > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel > > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel > >