From owner-freebsd-wireless@FreeBSD.ORG Fri Oct 18 17:44:01 2013 Return-Path: Delivered-To: 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 ESMTP id 14AD1BB9; Fri, 18 Oct 2013 17:44:01 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from mail-oa0-x234.google.com (mail-oa0-x234.google.com [IPv6:2607:f8b0:4003:c02::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C1FE723B5; Fri, 18 Oct 2013 17:44:00 +0000 (UTC) Received: by mail-oa0-f52.google.com with SMTP id n10so861877oag.39 for ; Fri, 18 Oct 2013 10:44:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=tl+U8XuUH1i+ke/Lz72XRi9RVXxYZ6HUYZIU1xHBMOc=; b=Ark2UivpX6gNMDX12d9pWAkq54PgmQ68GB82DTjezwp+S7hzznbmL3Xlv9FwWdk0az 8ag6xqOsFg+rAKjhOPQdFmnhRuxC3HsM5GuK8V7CRrbSwzrkCgY8qm8L+nEXv7WfjD/s WRvm0ZyP+UT09BgoaQn9BCcITjxekcNOrYQXkZe1Ukir8QYRE+IVYwyfgpjy+giwb3Qi +FcFMbkcChSSk5A9R2skq82DDfFKyLv+PuPx8k1hdD8TAjkuOt3QNHfBLC0J+fHjfbWh 1RI4Rs6I/MiOVHmT28fEw9lq3I4F8yAg7zx0YqdWiw2zwmjgomx9DHiDKKaVSxWZtvXW i+3g== MIME-Version: 1.0 X-Received: by 10.182.40.134 with SMTP id x6mr6387483obk.31.1382118239976; Fri, 18 Oct 2013 10:43:59 -0700 (PDT) Received: by 10.76.69.104 with HTTP; Fri, 18 Oct 2013 10:43:59 -0700 (PDT) In-Reply-To: References: Date: Fri, 18 Oct 2013 19:43:59 +0200 Message-ID: Subject: Re: Why does ath(4) suck, and what else to buy? From: =?UTF-8?Q?Ulrich_Sp=C3=B6rlein?= To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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: Fri, 18 Oct 2013 17:44:01 -0000 Well, the VAP support is not a hard requirement, as I can just buy one USB fob per AP that I need (I have plenty of USB ports on this little thing). So no USB wireless device with working AP mode? :( What are other people using? Would hardware donations speed things up? Anyo= ne? Sad, Uli 2013/10/17 Adrian Chadd : > .. same deal in 2GHz. There's currently nothing that's rock solid stable = and > works with a large variety of devices. Sorry. > > > -adrian > > > > On 17 October 2013 02:29, Ulrich Sp=C3=B6rlein wro= te: >> >> 2013/10/16 Adrian Chadd : >> > .. and there aren't currently any USB fobs that work rock solid in AP >> > mode >> > in 5GHz. Sorry. >> >> Well, I'm happy to do it the other way round! That is, have the >> minipci ath(4) serve my 5GHz needs (one AP only), and then have a USB >> fob that does 2.4GHz and 2x APs (private + guest AP). >> >> I'm also happy to try patches against ath(4), if you have some that >> might improve stability and stuff. >> >> Cheers, >> Uli > >