From owner-freebsd-wireless@FreeBSD.ORG Sat Aug 30 16:39:10 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0A114EED for ; Sat, 30 Aug 2014 16:39:10 +0000 (UTC) Received: from DUB004-OMC1S35.hotmail.com (dub004-omc1s35.hotmail.com [157.55.0.234]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 88DC91D17 for ; Sat, 30 Aug 2014 16:39:09 +0000 (UTC) Received: from DUB131-W19 ([157.55.0.239]) by DUB004-OMC1S35.hotmail.com with Microsoft SMTPSVC(7.5.7601.22724); Sat, 30 Aug 2014 09:37:59 -0700 X-TMN: [khkux17uxEIvvJTW5Y9vkEPUrRDtWBhH] X-Originating-Email: [cipher_nl@hotmail.com] Message-ID: From: Dirk E To: "freebsd-wireless@freebsd.org" Subject: FreeBSD wireless support is lacking; needs better documentation Date: Sat, 30 Aug 2014 18:37:59 +0200 Importance: Normal Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 30 Aug 2014 16:37:59.0781 (UTC) FILETIME=[C2A1F950:01CFC470] X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Aug 2014 16:39:10 -0000 Hello guys=2C=0A= =0A= I wrote to the freebsd-wireless@ list on 12 August=2C looking for a working= USB wireless adapter that can work on HOSTAP mode. There was no reply on m= y message and so far i have been unsuccessful in finding any device that wo= rks without some kind of limitation.=0A= =0A= The problems are:=0A= =0A= 1) FreeBSD supports only a limited range of wireless adapters=2C mostly old= er products that are not sold anymore or are hard to come by=0A= =0A= 2) FreeBSD has limitations on supported products=2C such as no working HOST= AP or no working 11n (only 11a/b/g) or no proper power-save features=0A= =0A= 3) FreeBSD lacks up-to-date information about actual supported products=3B = many products have newer revisions which use different chipsets=0A= =0A= 4) Documentation is not complete=3B for example the urtwn manpage does not = specify that HOSTAP is not supported under the CAVEATS section=0A= =0A= 5) Products are sold with different chipsets under the same name=2C product= s sold in the USA may work while the same product sold in the EU does not w= ork=0A= =0A= 6) It is generally very hard to find out what chipset a product uses=0A= =0A= =0A= I've been trying for weeks to find a working solution. I have given up on 1= 1n support=2C i just want things to work. I got fed up after trying two dev= ices which should be supported but didn't work in the end=2C so i bought a = bunch of devices and hoped that one would work:=0A= =0A= Asus WL-167 (supported by rum driver=3B because of missing power-save in HO= STAP mode it only works with some clients=3B andriod phones for example don= 't seem to work=3B they can connect but not perform any IP traffic)=0A= TP-LINK TL-WN822N (supported by urtwn=2C but despite manpage not mentioning= this=2C HOSTAP mode is not supported=3B 11n not supported but documented)= =0A= TP-LINK TL-WN821N=0A= TP-LINK TL-WN722N =0A= TP-LINK TL-WN725N (should be supported by urtwn=2C but only the USA version= s=3B the EU version appears not to be supported by this driver at all=3B no= t documented)=0A= EnGenius EUB9707 (only device that actually works in HOSTAP mode=3B but wit= hout 11n support)=0A= Dlink GO-USB-N150 =0A= Eminent EM4579 (no info about this device)=0A= =0A= =0A= It appears the lack of HOSTAP-mode in the urtwn-driver was known by OpenBSD= =2C from which the driver was imported. So then=2C why is this information = not shared with us by including it in the urtwn manpage? There is a patch f= or the OpenBSD driver to add HOSTAP mode for this driver=3B i am not sure w= hether it can be applied to FreeBSD.=0A= =0A= Long story short=3B FreeBSD's wireless support is lacking. It's almost a co= mplete mess. It takes many time and frustration for a user to get a working= product that works decently with FreeBSD. And even then=2C it often works = without features like 11n and proper power save features. It's one of the a= reas that FreeBSD is much behind in terms of hardware support compared to v= irtually every other operating system out there. That's a shame=3B FreeBSD = would be an excellent wireless access point when paired with pf-firewall.= =0A= =0A= I propose the following: create a wiki with a list of known working wireles= s products. Each product should note which chipset it uses=2C what driver i= t connects to=2C what features are suported (i.e. HOSTAP)=2C what FreeBSD v= ersions are supported=2C whether it is open source / binary blob=2C any lic= ense requirements (like Realtek) and a dmesg snippet where the driver is de= tected. It can be managed by a maintainer that accepts email reports from u= sers who provide the required information. That way=2C we get a list of har= dware that is known to work with FreeBSD that people can actually buy. Even= a NewEgg-link or something to that effect can be provided.=0A= =0A= This website was a lot of help to me in figuring out what chipset a wireles= s product uses: https://wikidevi.com/wiki/Main_Page=0A= I propose something simpler for FreeBSD=3B just a single wiki page that lis= ts products that either work or do not work.=0A= =0A= With very limited hardware support for wireless devices=2C such a list is n= eeded very badly=2C to prevent other people from going through the same hel= lhound that i've gone through. If even just a handful of wireless devices t= hat are still being sold are known to be working with FreeBSD=2C this list = would be very helpful i would presume.=0A= =0A= Anyone who likes this idea?=0A= =