From owner-freebsd-wireless@FreeBSD.ORG Sun Aug 10 06:41:33 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 51B2EFDA; Sun, 10 Aug 2014 06:41:33 +0000 (UTC) Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 063922D4E; Sun, 10 Aug 2014 06:41:32 +0000 (UTC) Received: by mail-qc0-f173.google.com with SMTP id w7so647188qcr.32 for ; Sat, 09 Aug 2014 23:41:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=pg6zNhqKtd7w3wYqd7Gp0NaPTyTmjwbvfnlf0qUhEkA=; b=XfL+61wnKbZ+CvXPddbH2PG/UXVga4X6VRFnc6ji/B6vuXibt5onQS5Kgwj7s67pyW EduIiI8i+97tjJjVGiQG8V5P0d73a1taOtUxoiCgB6bXj6ulkmlhCvm8SUdDsk7RCg5H SXiDpM8urSlEH13NOBWNQlmKhQMuJRlGYx+W/0mZ6YdDgEz0tAL2OFeP9INK5m5WpvB6 96GYXeEWWs6dzLye+MQhLddoma6iJ2bGKD8UbN75pwmOAb9dTnAlZ3vtL99D3TboZHpq o3vThGegGICH/d2SbNEU2Hn+/0mgWXYNOo4ADAdsLfIUsaLNQu2oPTadriRUOZfl2+sK BzoQ== MIME-Version: 1.0 X-Received: by 10.140.41.133 with SMTP id z5mr36483236qgz.99.1407652892080; Sat, 09 Aug 2014 23:41:32 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.41.6 with HTTP; Sat, 9 Aug 2014 23:41:32 -0700 (PDT) Date: Sat, 9 Aug 2014 23:41:32 -0700 X-Google-Sender-Auth: LbUeRuk5SmZyiL3t9SIeH9yWlu0 Message-ID: Subject: [rfc] INJECT mode for net80211 From: Adrian Chadd To: "freebsd-wireless@freebsd.org" , "freebsd-arch@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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: Sun, 10 Aug 2014 06:41:33 -0000 Hi! I kinda got fed up with the lack of functioning inject. * monitor mode isn't inject mode; * ahdemo mode seems .. less useful. So I just created IEEE80211_M_INJECT and taught net80211 / ath about it. This is like monitor mode (straight to RUN, no need to set an SSID, no auto scanning by default) but it allows transmit and populates the node table with temporary node entries. So: http://people.freebsd.org/~adrian/ath/20140809-net80211-ath-inject-1.diff I'd like to commit this in the next couple of days. I've also tested this with aircrack-ng - the built port didn't work with monitor mode modified to inject frames. I don't know why. Rebuilt from source worked fine. I've just modified my local copy to set the IFM_IEEE80211_INJECT flag rather than monitor flag and it seems it's all okay. The only issue I've seen with packet injection is that aircrack-ng isn't waiting until the interface is up before trying to send frames, so some are rejected rather than buffered. -a From owner-freebsd-wireless@FreeBSD.ORG Sun Aug 10 07:54:12 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 90D9BAB; Sun, 10 Aug 2014 07:54:12 +0000 (UTC) Received: from felyko.com (felyko.com [65.49.80.26]) by mx1.freebsd.org (Postfix) with ESMTP id 7AF9E24AB; Sun, 10 Aug 2014 07:54:12 +0000 (UTC) Received: from [IPv6:2601:9:8280:5fd:d5a4:20d0:8128:6903] (unknown [IPv6:2601:9:8280:5fd:d5a4:20d0:8128:6903]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by felyko.com (Postfix) with ESMTPSA id 7806334AAC9; Sun, 10 Aug 2014 00:54:11 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [rfc] INJECT mode for net80211 From: Rui Paulo In-Reply-To: Date: Sun, 10 Aug 2014 00:54:26 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <80DB3DCF-496E-4596-B9F3-4D86AC82DEC5@FreeBSD.org> References: To: Adrian Chadd X-Mailer: Apple Mail (2.1878.6) Cc: "freebsd-wireless@freebsd.org" , "freebsd-arch@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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: Sun, 10 Aug 2014 07:54:12 -0000 On Aug 9, 2014, at 23:41, Adrian Chadd wrote: > Hi! >=20 > I kinda got fed up with the lack of functioning inject. >=20 > * monitor mode isn't inject mode; > * ahdemo mode seems .. less useful. >=20 > So I just created IEEE80211_M_INJECT and taught net80211 / ath about > it. This is like monitor mode (straight to RUN, no need to set an > SSID, no auto scanning by default) but it allows transmit and > populates the node table with temporary node entries. >=20 > So: >=20 > = http://people.freebsd.org/~adrian/ath/20140809-net80211-ath-inject-1.diff This patch looks incomplete. Did you forget to diff sys/net? > I'd like to commit this in the next couple of days. >=20 > I've also tested this with aircrack-ng - the built port didn't work > with monitor mode modified to inject frames. I don't know why. Rebuilt > from source worked fine. I've just modified my local copy to set the > IFM_IEEE80211_INJECT flag rather than monitor flag and it seems it's > all okay. >=20 > The only issue I've seen with packet injection is that aircrack-ng > isn't waiting until the interface is up before trying to send frames, > so some are rejected rather than buffered. In general, I'd prefer to have one mode. aircrack used to work in = monitor mode, so I'm surprised the problem is the lack of an inject = mode. Looking at the code, you're pretty much defining INJECT to be = MONITOR mode. -- Rui Paulo From owner-freebsd-wireless@FreeBSD.ORG Sun Aug 10 08:02:55 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 78507455; Sun, 10 Aug 2014 08:02:55 +0000 (UTC) Received: from mail-qg0-x236.google.com (mail-qg0-x236.google.com [IPv6:2607:f8b0:400d:c04::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 183A2256A; Sun, 10 Aug 2014 08:02:55 +0000 (UTC) Received: by mail-qg0-f54.google.com with SMTP id z60so7533257qgd.41 for ; Sun, 10 Aug 2014 01:02:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=N2pVFlTcrQI7sHhImRcFlsYCPWOLJq8VjYaZdzFmrio=; b=b1jGoQ21Fz/7cDf49psjp1uWJiCBG/IyATp2VgrLrC/6A/KIgNxel5q+Gn1gH3nJxs cEqYXfS1Ea/HJKKT4+ktzLF3+bsiO6jRWqMts6W8sr2UDC3BzbQuZGzSiV8OfI/8wlmR gk/7ND1dAYMNnWKexqvG7RK2wu55XIodlarl+nqkm3H1M0eoqU7IA9+UFOi/KT4+Sfx4 F5B5DEOn1ixqy7Dx31CPxoUW6IZ6MMb653Uj1eQOLkzl7uuAc54DCjFx9kClMZ9EUK/v hMhquolIOdwhwuUkROGFFAR5f4UQvPjm3q08Zhsxlnl+RbHG+0X2MIycDkXdn6yvjuOr wVoA== MIME-Version: 1.0 X-Received: by 10.229.73.70 with SMTP id p6mr52293368qcj.13.1407657774195; Sun, 10 Aug 2014 01:02:54 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.41.6 with HTTP; Sun, 10 Aug 2014 01:02:54 -0700 (PDT) In-Reply-To: <80DB3DCF-496E-4596-B9F3-4D86AC82DEC5@FreeBSD.org> References: <80DB3DCF-496E-4596-B9F3-4D86AC82DEC5@FreeBSD.org> Date: Sun, 10 Aug 2014 01:02:54 -0700 X-Google-Sender-Auth: Kq-FoBV3ymBFn6OJH7SKLETfNqY Message-ID: Subject: Re: [rfc] INJECT mode for net80211 From: Adrian Chadd To: Rui Paulo Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" , "freebsd-arch@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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: Sun, 10 Aug 2014 08:02:55 -0000 On 10 August 2014 00:54, Rui Paulo wrote: > On Aug 9, 2014, at 23:41, Adrian Chadd wrote: > >> Hi! >> >> I kinda got fed up with the lack of functioning inject. >> >> * monitor mode isn't inject mode; >> * ahdemo mode seems .. less useful. >> >> So I just created IEEE80211_M_INJECT and taught net80211 / ath about >> it. This is like monitor mode (straight to RUN, no need to set an >> SSID, no auto scanning by default) but it allows transmit and >> populates the node table with temporary node entries. >> >> So: >> >> http://people.freebsd.org/~adrian/ath/20140809-net80211-ath-inject-1.diff > > This patch looks incomplete. Did you forget to diff sys/net? Hm, try: http://people.freebsd.org/~adrian/ath/20140809-net80211-ath-inject-2.diff > In general, I'd prefer to have one mode. aircrack used to work in monitor mode, so I'm surprised the problem is the lack of an inject mode. Looking at the code, you're pretty much defining INJECT to be MONITOR mode. How did it used to work? * monitor mode very specifically doesn't define output methods at all; * there's no temporary nodes created when transmitting, so it all simply ends up being dropped because no txnode was found. So perhaps there was some path via the raw output method which no longer is working. The _output() method supposedly permits BPF injected packets to work by sending packets using a node == vap->iv_bss, but that can't possibly work with the existing monitor mode because code in ieee80211.c doesn't set the output methods for monitor mode. -a From owner-freebsd-wireless@FreeBSD.ORG Sun Aug 10 08:19:43 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 059B2761; Sun, 10 Aug 2014 08:19:43 +0000 (UTC) Received: from mail-qa0-x22f.google.com (mail-qa0-x22f.google.com [IPv6:2607:f8b0:400d:c00::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 993B3266A; Sun, 10 Aug 2014 08:19:42 +0000 (UTC) Received: by mail-qa0-f47.google.com with SMTP id i13so6966297qae.6 for ; Sun, 10 Aug 2014 01:19:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=I9nybPXIqZ4l2OuA9vcjY4RjTg/wuH9WpXNdxVXQHPs=; b=ne+HAbfeMrcAplYdomCiEO6AshinECM5BFM/nhvN3NJb5CzaKo8Q+mkfffkACE8yvn 2YC9d0tgs9maXwMn70YXLkscCPI0D2LiuaFUVTPtmadgbVKo9gc0hR82lJpLhCkEW4KE kDP8MQf1B6H5+5D/z/YcSvVROQ9V44C4m1j2pJzkcSXqp2Dh+egUb5rc6Bf3+e6lIrwf 1e/u0sKcVQioiUzLygHTnngP3reDi1+2e90lH3GxT6TOimqNNM0WWu+0n0DseVWbXNA/ GT77KS2jCVJHx/cfcFeo8FnBA3XA0vSGEnwxJYwWPPpMHtinSlk0ScWwowLT7JaXcRCg KykQ== MIME-Version: 1.0 X-Received: by 10.224.120.138 with SMTP id d10mr54303961qar.55.1407658781766; Sun, 10 Aug 2014 01:19:41 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.41.6 with HTTP; Sun, 10 Aug 2014 01:19:41 -0700 (PDT) In-Reply-To: References: <80DB3DCF-496E-4596-B9F3-4D86AC82DEC5@FreeBSD.org> Date: Sun, 10 Aug 2014 01:19:41 -0700 X-Google-Sender-Auth: swgpTu3LF9mwFkNO4dKolbB9h7A Message-ID: Subject: Re: [rfc] INJECT mode for net80211 From: Adrian Chadd To: Rui Paulo Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" , "freebsd-arch@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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: Sun, 10 Aug 2014 08:19:43 -0000 ah, sam disabled it in r195846 due to regulatory constraints. Hm. I wonder what else rotted in the meantime. -a From owner-freebsd-wireless@FreeBSD.ORG Sun Aug 10 08:28:23 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F02F6A39; Sun, 10 Aug 2014 08:28:23 +0000 (UTC) Received: from mail-qg0-x235.google.com (mail-qg0-x235.google.com [IPv6:2607:f8b0:400d:c04::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8EEA02728; Sun, 10 Aug 2014 08:28:23 +0000 (UTC) Received: by mail-qg0-f53.google.com with SMTP id q107so7484988qgd.40 for ; Sun, 10 Aug 2014 01:28:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=iOLHBPLcTXTPcreGRJDx1CRtqevSFZPek5luWTmk+JU=; b=NzGZHdHmL7ruoxgqdEjZvwV+iFMz6nhxw6/LWGikGpCoGAOLWaVXFL4k/fb43luMVI 3cKSSWk9w9qoU7c0tO+E2sG7gYfvAvNOBPOuwKk4dGpqB7m1Zn3Cvb8i4BUTsiPrSWsU F9IxvzFZ+pOTLOtm9nHHIawAcfAyWhiMlbSq5+doZQSGml+ze29DBUfgTDLFC0eHCIe3 u/wVw6++XhPvjGfpVygH4riOBz08DawXvlltotR6sQ9Q9//bV32N/bIkrd/sXisL0XmZ PCcbMmfqFhJ065wx/kcjwDYokmrTTY90T62pEyF59bBe1CqCddM9PMhmUGeiYcOK4j/q Fkyw== MIME-Version: 1.0 X-Received: by 10.229.38.3 with SMTP id z3mr52303939qcd.17.1407659302757; Sun, 10 Aug 2014 01:28:22 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.41.6 with HTTP; Sun, 10 Aug 2014 01:28:22 -0700 (PDT) In-Reply-To: References: <80DB3DCF-496E-4596-B9F3-4D86AC82DEC5@FreeBSD.org> Date: Sun, 10 Aug 2014 01:28:22 -0700 X-Google-Sender-Auth: O2Eex4biiv7KYNlpYvWhjPpDxXE Message-ID: Subject: Re: [rfc] INJECT mode for net80211 From: Adrian Chadd To: Rui Paulo Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" , "freebsd-arch@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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: Sun, 10 Aug 2014 08:28:24 -0000 ... interesting. Ok, so: * if I just "remove" sam's patch there, monitor mode works to inject; * I've patched kismet so it reads the radiotap data using the example parser and added XCHANNEL support - so now it actually works nicely; * aircrack-ng from ports doensn't send - it's triggering on this in net80211: wh = mtod(m, struct ieee80211_frame *); if ((wh->i_fc[0] & IEEE80211_FC0_VERSION_MASK) != IEEE80211_FC0_VERSION_0) senderr(EIO); /* XXX */ .. I haven't looked into why yet. * but, aircrack-ng built from source works, save for when it tries to transmit too quickly after changing channels. Ok, so I'm going to just revert that change for now and see about figuring out some other way to enforce regulatory concerns on monitor mode transmit. (Likely by allowing receive, but failing transmit on non-regulatory channels.) I'll speak to the Kismet author here tomorrow and see about getting this replacement radiotap parser in so it works correctly again in FreeBSD. And as for aircrack-ng - guess I'll poke the port maintainer. -a From owner-freebsd-wireless@FreeBSD.ORG Sun Aug 10 08:42:15 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 E07791F1; Sun, 10 Aug 2014 08:42:14 +0000 (UTC) Received: from mail.0x20.net (mail.0x20.net [217.69.76.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 95110289D; Sun, 10 Aug 2014 08:42:14 +0000 (UTC) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id 315536A6005; Sun, 10 Aug 2014 10:42:11 +0200 (CEST) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.7/8.14.7) with ESMTP id s7A8gBj8050615; Sun, 10 Aug 2014 10:42:11 +0200 (CEST) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.7/8.14.7/Submit) id s7A8gA76050233; Sun, 10 Aug 2014 10:42:10 +0200 (CEST) (envelope-from lars) Date: Sun, 10 Aug 2014 10:42:10 +0200 From: Lars Engels To: Adrian Chadd Subject: Re: [rfc] INJECT mode for net80211 Message-ID: <20140810084210.GA56043@e-new.0x20.net> References: <80DB3DCF-496E-4596-B9F3-4D86AC82DEC5@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="LQksG6bCIzRHxTLp" Content-Disposition: inline In-Reply-To: X-Editor: VIM - Vi IMproved 7.4 X-Operation-System: FreeBSD 8.4-RELEASE-p4 User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "freebsd-wireless@freebsd.org" , Rui Paulo , "freebsd-arch@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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: Sun, 10 Aug 2014 08:42:15 -0000 --LQksG6bCIzRHxTLp Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 10, 2014 at 01:28:22AM -0700, Adrian Chadd wrote: > ... interesting. Ok, so: >=20 > * if I just "remove" sam's patch there, monitor mode works to inject; > * I've patched kismet so it reads the radiotap data using the example > parser and added XCHANNEL support - so now it actually works nicely; > * aircrack-ng from ports doensn't send - it's triggering on this in net80= 211: >=20 > wh =3D mtod(m, struct ieee80211_frame *); > if ((wh->i_fc[0] & IEEE80211_FC0_VERSION_MASK) !=3D > IEEE80211_FC0_VERSION_0) > senderr(EIO); /* XXX */ >=20 > .. I haven't looked into why yet. >=20 > * but, aircrack-ng built from source works, save for when it tries to > transmit too quickly after changing channels. >=20 > Ok, so I'm going to just revert that change for now and see about > figuring out some other way to enforce regulatory concerns on monitor > mode transmit. (Likely by allowing receive, but failing transmit on > non-regulatory channels.) >=20 > I'll speak to the Kismet author here tomorrow and see about getting > this replacement radiotap parser in so it works correctly again in > FreeBSD. >=20 > And as for aircrack-ng - guess I'll poke the port maintainer. >=20 Which is me. :) Thanks a lot for working on this, let me know if you need any assistance for the aircrack-ng port. BTW the aircrack-ng developers are very helpful and FreeBSD-friendly, so we should get patches upstream. --LQksG6bCIzRHxTLp Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQF8BAEBCgBmBQJT5zBiXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4RjQwMDE3RTRERjUzMTI1N0FGRTUxNDlF NTRDQjM3RDNBMDg5RDZEAAoJEOVMs306CJ1tPCoIAK8aQcJYSRSwIFlx5mahl7Lq lR3saWlYyhOTeCVOjwKAoQJiV1z7NbKYRlEPC9nCiC892T62pmcW47YLnTla70Rq EAJ3meeUnGxopSAIfq9VUF9K6Sc92XU99FDHD8k4FA6FokSPJ8MSgYrR6oUxCwyE iQW+GW5u5R0Qo0Ltl7Mx12xWr4OWd7yDSJ9u8DP25aK3xonvQc6aPN465+dtoxAJ GKm89ezD548vdOCqUHqaARr23Xos7R3+ZNWsNo9A3yl4fhbio7sP5MwAUCBQw7eW j9jEIAqnbJiaCvsghv3hDT2GQlFbjM4Xo7V9IZvPk3NFjE99PnZDcmge/DRbKmY= =E3Af -----END PGP SIGNATURE----- --LQksG6bCIzRHxTLp-- From owner-freebsd-wireless@FreeBSD.ORG Sun Aug 10 12:45:26 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 58D3418C for ; Sun, 10 Aug 2014 12:45:26 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 413002FFF for ; Sun, 10 Aug 2014 12:45:26 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s7ACjQiW074075 for ; Sun, 10 Aug 2014 12:45:26 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 176104] [iwn] iwn0: iwn_intr: fatal firmware error Date: Sun, 10 Aug 2014 12:45:25 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 10.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rene@FreeBSD.org X-Bugzilla-Status: In Discussion X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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: Sun, 10 Aug 2014 12:45:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=176104 Rene Ladan changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rene@FreeBSD.org --- Comment #10 from Rene Ladan --- I'm seeing the same (or quite similar) fatal firmware errors on my Acer 7738G with this chip: iwn0: mem 0xf5200000-0xf5201fff irq 17 at device 0.0 on pci3 This is on 10.0-RELEASE amd64, with firmware version iwlwifi-5150-8.24.2.2 -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 11 00:10:43 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5593AED for ; Mon, 11 Aug 2014 00:10:43 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2500020B5 for ; Mon, 11 Aug 2014 00:10:43 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s7B0AhGb087225 for ; Mon, 11 Aug 2014 00:10:43 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192567] New: [ath] AR9331 regulator programming is checking OTP but reading garbage Date: Mon, 11 Aug 2014 00:10:43 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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: Mon, 11 Aug 2014 00:10:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192567 Bug ID: 192567 Summary: [ath] AR9331 regulator programming is checking OTP but reading garbage Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: wireless Assignee: freebsd-wireless@FreeBSD.org Reporter: adrian@freebsd.org The AR9331 HAL is programming the regulator during reset. However, it's reading values from the OTP which seems to (a) read correctly from the OTP, but (b) read 0xbadc0ffe. I'm not sure why that is yet (eg is the OTP hardware off?) Now, on the AR9331 boards I have (eg carambola 2) the calibration data is in the NOR flash rather than OTP. So, this won't .. work. I'm not sure which boards will use OTP in this instance. But the code seems to check and use the OTP value. Ie: ar9300_internal_regulator_apply(): ... if ((reg_val & 0x80) == 0x80){ usb_valid = 1; reg_usb = reg_val & 0x000000ff; } ... if ((reg_val & 0x80000000) == 0x80000000){ pmu_valid = 1; reg_pmu = (reg_val & 0xff000000) >> 24; } ... 0xbadc0ffe has both of those bits set! ath9k doesn't bother checking the OTP here. It just uses some local values to program in. So, what should be done? * Is the code correct but OTP isn't on for some reason? * Should I be checking the in-flash calibration data? * should I just ignore OTP and use hard-coded values like ath9k? -a -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 11 00:12:17 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6D76413C for ; Mon, 11 Aug 2014 00:12:17 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 420C7213D for ; Mon, 11 Aug 2014 00:12:17 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s7B0CHUw025394 for ; Mon, 11 Aug 2014 00:12:17 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192415] [ath] AR933x power save causes the AR9331 to stop DMA Date: Mon, 11 Aug 2014 00:12:17 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: Issue Resolved X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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: Mon, 11 Aug 2014 00:12:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192415 Adrian Chadd changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Triage |Issue Resolved Resolution|--- |FIXED --- Comment #2 from Adrian Chadd --- This has been fixed in r269748. Well, "fixed" - it just cold resets the NIC as appropriately rather than trying to figure out why it's failing. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 11 08:00:21 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 BE34BA96 for ; Mon, 11 Aug 2014 08:00:21 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9FB982D68 for ; Mon, 11 Aug 2014 08:00:21 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s7B80LYf093753 for ; Mon, 11 Aug 2014 08:00:21 GMT (envelope-from bugzilla-noreply@freebsd.org) Message-Id: <201408110800.s7B80LYf093753@kenobi.freebsd.org> From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bugzilla] Commit Needs MFC MIME-Version: 1.0 X-Bugzilla-Type: whine X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated Date: Mon, 11 Aug 2014 08:00:21 +0000 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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: Mon, 11 Aug 2014 08:00:21 -0000 Hi, You have a bug in the "Needs MFC" state which has not been touched in 7 or more days. This email serves as a reminder that you may want to MFC this bug or marked it as completed. In the event you have a longer MFC timeout you may update this bug with a comment and I won't remind you again for 7 days. This reminder is only sent on Mondays. Please file a bug about concerns you may have. This search was scheduled by eadler@FreeBSD.org. (7 bugs) Bug 140567: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] [patch] ath is not worked on my notebook PC Bug 154598: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] Atheros 5424/2424 can't connect to WPA network Bug 163312: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [panic] [ath] kernel panic: page fault with ath0 taskq Bug 166190: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] TX hangs and frames stuck in TX queue Bug 166357: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the software queue Bug 166642: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a station in powersave cripples AP TX. Bug 169362: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC Error bit set as well as the PHY errors From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 11 10:15:42 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5D001D2B for ; Mon, 11 Aug 2014 10:15:42 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3FB952E8D for ; Mon, 11 Aug 2014 10:15:42 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s7BAFgsx035597 for ; Mon, 11 Aug 2014 10:15:42 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192423] FreeBSD-10 with AR9220, console spam and reboot with both hostap and client wlan-s on the same ath0 Date: Mon, 11 Aug 2014 10:15:42 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 10.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ndenev@gmail.com X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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: Mon, 11 Aug 2014 10:15:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192423 --- Comment #4 from Nikolay Denev --- So, just for the experiment, I've commented out the "currrates != sc_currates!" device_printf line and recompiled. Now, when I crete both wlan devices one, AP one STA, they seem to work, but after a while (a few minutes) of iperf traffic over wlan1 (the AP) I see a lot of these on the console and wifi clients lose IP connectivity while still show "associated": Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39fbbc0: seqno 2434: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39eaef0: seqno 2435: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39e9f00: seqno 2436: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39ecdc0: seqno 2437: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f4d40: seqno 2438: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f0d80: seqno 2439: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39e8e00: seqno 2440: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39e7150: seqno 2441: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39fa790: seqno 2442: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39e0820: seqno 2443: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39eb660: seqno 2444: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39e89c0: seqno 2445: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39e8470: seqno 2446: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f8f20: seqno 2447: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f21b0: seqno 2428: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f01d0: seqno 2453: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39da550: seqno 2454: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39ea780: seqno 2455: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39eeeb0: seqno 2456: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39eced0: seqno 2458: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39e3c30: seqno 2459: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39dda70: seqno 2460: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39ea670: seqno 2461: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f6170: seqno 2462: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f5f50: seqno 2463: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39dffa0: seqno 2464: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f1930: seqno 2465: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39dc860: seqno 2466: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f23d0: seqno 2467: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f78d0: seqno 2468: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f02e0: seqno 2469: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f4e50: seqno 2470: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f14f0: seqno 2471: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39eea70: seqno 2472: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39e4180: seqno 2473: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39e3190: seqno 2474: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39edec0: seqno 2475: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39e26f0: seqno 2476: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f3f70: seqno 2477: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39dca80: seqno 2478: bf_next not NULL! Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39fa9b0: seqno 2479: bf_next not NULL! -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 11 10:18:08 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 7F418DA5 for ; Mon, 11 Aug 2014 10:18:08 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 665222EBE for ; Mon, 11 Aug 2014 10:18:08 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s7BAI87e037315 for ; Mon, 11 Aug 2014 10:18:08 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192423] FreeBSD-10 with AR9220, console spam and reboot with both hostap and client wlan-s on the same ath0 Date: Mon, 11 Aug 2014 10:18:08 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 10.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ndenev@gmail.com X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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: Mon, 11 Aug 2014 10:18:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192423 --- Comment #5 from Nikolay Denev --- So, I'm absolutely not familiar with the inner workings of the 80211 layer, but if the ""currrates != sc_currates!"" condition is not something really weird in my case, maybe I can try to turn this into a counter, so that the console is not spammed to a livelock of the machine. (offtopic, but ideally kernel printf should have had some rate limiting) -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 11 17:17:30 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 7FA88F26 for ; Mon, 11 Aug 2014 17:17:30 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 65E0F2685 for ; Mon, 11 Aug 2014 17:17:30 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s7BHHULH059163 for ; Mon, 11 Aug 2014 17:17:30 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192423] FreeBSD-10 with AR9220, console spam and reboot with both hostap and client wlan-s on the same ath0 Date: Mon, 11 Aug 2014 17:17:30 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 10.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: In Discussion X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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: Mon, 11 Aug 2014 17:17:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192423 Adrian Chadd changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Triage |In Discussion --- Comment #6 from Adrian Chadd --- Ah, I only noticed just now that you're using it as STA and AP. So, the only supported (read: tested) setup with a STA + AP VAP on the same device is when running it as a wireless extension using WDS. Also, I think I fixed that bf_next issue in -HEAD. Would you consider running that instead for ath+11n? -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 11 18:14:30 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 ACE6C5A2 for ; Mon, 11 Aug 2014 18:14:30 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 934C22DEE for ; Mon, 11 Aug 2014 18:14:30 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s7BIEUH9053856 for ; Mon, 11 Aug 2014 18:14:30 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192423] FreeBSD-10 with AR9220, console spam and reboot with both hostap and client wlan-s on the same ath0 Date: Mon, 11 Aug 2014 18:14:30 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 10.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ndenev@gmail.com X-Bugzilla-Status: In Discussion X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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: Mon, 11 Aug 2014 18:14:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192423 --- Comment #7 from Nikolay Denev --- I will give it a try (running CURRENT) if time permits, as the full rebuild will take me some time (I don't have a separate build env setup correctly, and rebuilding on the Soekris itslef takes a few days :D ) Anyways, I've just tried a shortcut and manually applied a bf_next fix I've found : http://svnweb.freebsd.org/base?view=revision&revision=264710 And not I no longer see these messages. Apart from having to do a "ifconfig wlan1 down && ifconfig wlan1 up" after reboot[1] it seems to work and I just pushed a 60 secs of iperf over the AP wlan : [ 5] local 10.0.0.1 port 5001 connected with 10.0.0.173 port 61317 [ 5] 0.0-60.0 sec 615 MBytes 86.0 Mbits/sec [1]: after reboot I see wlan1 as "no carrier", while it is UP and hostapd is runing. If I do down/up if starts working. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Tue Aug 12 06:45:15 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 B84B3421 for ; Tue, 12 Aug 2014 06:45:15 +0000 (UTC) Received: from mail-ig0-x235.google.com (mail-ig0-x235.google.com [IPv6:2607:f8b0:4001:c05::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8C3FB2E69 for ; Tue, 12 Aug 2014 06:45:15 +0000 (UTC) Received: by mail-ig0-f181.google.com with SMTP id h3so5773991igd.14 for ; Mon, 11 Aug 2014 23:45:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=o259FTOwqwp9qHomLaajgb27LwDxgDmW+dpVJjWiubI=; b=fN36GxtQ/pObgy1cme+xuI4a0Z9mBfhXbh8YPckg5bbblCDb77eZJwPjgxPLgASA1S HTak64VFDpFv0PrpGi6+dVC8z39DtfRIuiFJSAGX3svi97Gm4CFVlGJ2Zt0lGT8kTDEt /flCxmGQ8H1pszJpJr2U8G6mTBdTzV1knk2bWtSRJsDkHTyV0TtLrPWmQ8G7K7/55TMF ZL6mmAihIqDIkRt7fC5D5nI33ITtR7khqAzDvkUCAqYfqZj3sYxgoBmPxiSnWoCGQhGt PV1Ses6sE6/fxxfXEc9pjiJnsmDiZCf4bYibEC3e5MXkMgMY88IbNXrxykc/rBgIJrTL 3i0Q== MIME-Version: 1.0 X-Received: by 10.50.61.145 with SMTP id p17mr25582078igr.41.1407825914641; Mon, 11 Aug 2014 23:45:14 -0700 (PDT) Received: by 10.107.153.208 with HTTP; Mon, 11 Aug 2014 23:45:14 -0700 (PDT) Date: Tue, 12 Aug 2014 02:45:14 -0400 Message-ID: Subject: recommended 802.11n adapter to buy as AP on 10.0-R From: Peter Lai To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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: Tue, 12 Aug 2014 06:45:15 -0000 I'm looking to get a new wifi adapter which will be plugged into an Atom D2550 board, so it can be either pci-e x1 or usb3. The adapter needs to run as a single access point to support phones and tablets (iphone 4S only does n at 2.4ghz though). The box is running FreeBSD 10.0-RELEASE-p7 amd64. Can anyone throw out some least-hassle favorite cards for me to consider? Thanks From owner-freebsd-wireless@FreeBSD.ORG Tue Aug 12 08:59:28 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 0CC59E33 for ; Tue, 12 Aug 2014 08:59:28 +0000 (UTC) Received: from mail-qc0-x231.google.com (mail-qc0-x231.google.com [IPv6:2607:f8b0:400d:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C21B32D3A for ; Tue, 12 Aug 2014 08:59:27 +0000 (UTC) Received: by mail-qc0-f177.google.com with SMTP id x13so2589365qcv.36 for ; Tue, 12 Aug 2014 01:59:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=OI+cl+IVmiO2FoXgCon1CqAcjii/5KyuWi+Abyo4vU4=; b=QT7B9WVreGIq2c/yfjyz9DYU5uJ9o8syLes+BpPwUyihWA7V0ABkMlKxVzSAtq2C+w PH8dkvptW3xxZ1LpPaU7LHfKLKPukWZRvkjDPNaEV7xTrPv/1xUmOBsCbJ8y8Mk3tG/v xu0vPeJB2PGxj55xYgYViirUi8xRJ9PITyH0JqjcOJc2FYGSinqY4glYdsjefxcrLn0v Fw5LHRhauZXt/rAPp6aPVKuEMWfmhlgpKofq/zCYm1kfXulfHuxj1izVQVX7QGelFfQ/ +siEtzhGA6eS18M+TV5oYlLPTm6NWadI7SDpUlibwGeeR15IM8Gq+91J4HiC5JUsACdj JCLA== MIME-Version: 1.0 X-Received: by 10.224.3.67 with SMTP id 3mr4142426qam.26.1407833966926; Tue, 12 Aug 2014 01:59:26 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.41.6 with HTTP; Tue, 12 Aug 2014 01:59:26 -0700 (PDT) In-Reply-To: References: Date: Tue, 12 Aug 2014 01:59:26 -0700 X-Google-Sender-Auth: Fi56QZohkBjGRHEteQW5wzvsuAk Message-ID: Subject: Re: recommended 802.11n adapter to buy as AP on 10.0-R From: Adrian Chadd To: Peter Lai Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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: Tue, 12 Aug 2014 08:59:28 -0000 Anything Atheros, that is PCIe and isn't the 11ac NIC. I recommend AR9280 or later. So, AR9287 for 2 antenna, AR9285 for one antenna, or AR9380 for 3 antennas. (Or anything AR93xx, AR94xx, AR95xx will be fine.) -a On 11 August 2014 23:45, Peter Lai wrote: > I'm looking to get a new wifi adapter which will be plugged into an > Atom D2550 board, so it can be either pci-e x1 or usb3. > > The adapter needs to run as a single access point to support phones > and tablets (iphone 4S only does n at 2.4ghz though). The box is > running FreeBSD 10.0-RELEASE-p7 amd64. > > Can anyone throw out some least-hassle favorite cards for me to consider? > > Thanks > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Tue Aug 12 12:03:24 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F1E188F8; Tue, 12 Aug 2014 12:03:23 +0000 (UTC) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 51AC524CC; Tue, 12 Aug 2014 12:03:23 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id f8so6890616wiw.3 for ; Tue, 12 Aug 2014 05:03:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ORaUZqFnsM0yIgIU5ZNa+N9UWSk57iXKx1VDBHMB0V0=; b=sfoQgX1ZJsJ0ixnEwwDN3+wnEvHSZMEjyc6ewDfDD1efsS/EFiqXlSpUPqCwGaeY4x +qUOmob8nMUNNc2elVgMO8A9T2z35mHRnVDA3vsNESMbhGtcmzCpwku118mhUB5XiGdP ILzY9LARDr1RMfpPYC1GAD4scU8/LlkM6ib69RxgGV58QSyMiaRUjMOK+gXJEokxzGPU VuWNNffhh4XxuNebXVrrstHwARhnJUn1W2ToWALkhxSpi28yvzkBysN3qrVEnPFuIEvv 6aglMzclwgsUOOIQQmobSVQ2GyzlsaDvsyc0PGZkZCTjyIWMMfloa8BC+93quVSpU6y0 Y/TQ== X-Received: by 10.180.10.166 with SMTP id j6mr32803119wib.73.1407845001083; Tue, 12 Aug 2014 05:03:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.24.163 with HTTP; Tue, 12 Aug 2014 05:03:00 -0700 (PDT) In-Reply-To: <20140805092636.GA41308@ns.kevlo.org> References: <53DE4FD2.8050309@FreeBSD.org> <20140805092636.GA41308@ns.kevlo.org> From: Miguel Clara Date: Tue, 12 Aug 2014 13:03:00 +0100 Message-ID: Subject: Re: FreeBSD current RT3071 can't connect to 5G network To: Kevin Lo Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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: Tue, 12 Aug 2014 12:03:24 -0000 Sorry for the delay in replying, I was out of the office for the last week, I'm recompiling now to try this and will give feedback ASAP. Melhores Cumprimentos // Best Regards ----------------------------------------------- *Miguel Clara* *IT - Sys Admin & Developer* *E-mail: *miguelmclara@gmail.com www.linkedin.com/in/miguelmclara/ On Tue, Aug 5, 2014 at 10:26 AM, Kevin Lo wrote: > On Sun, Aug 03, 2014 at 11:05:54PM +0800, Kevin Lo wrote: > > > > On Tue, Jul 29, 2014 at 11:35:00PM +0100, Miguel Clara wrote: > > > Hi, > > > > Hi Miguel, > > > > > > > > I just brought a TP-Link N600 Wireless Dual Band USB Adpater (model > > > TL-WDN3200) and its correctly recognized in FreeBSD as a ranlink. > > > > > > Dmesg shows: > > > wlan0: Ethernet address: e8:94:f6:12:98:9d > > > run0: firmware RT3071 ver. 0.33 loaded > > > > > > > > > So the module and firmware seem to be loaded fine and I'm able to > connect > > > to my 2.4g wireless fine. > > > > > > However I'm having no luck connecting to the 5G network, I've pasted > the > > > scans and wpa_supplicant log, and I see: > > > "wlan0: Authentication with 60:a4:4c:28:13:c4 timed out. > > > Added BSSID 60:a4:4c:28:13:c4 into blacklist" > > > which I'm guessing means that for some reason the auth time-out, but I > > > don't really know why, all other 5G devices connect fine! > > > > > > (Also if its important the router is a RT-N66U running the latest > > > Asus-Merlin firmware) > > > > > > > > > First Scan: > > > > > > ~% ifconfig wlan0 scan > > > SSID/MESH ID BSSID CHAN RATE S:N INT CAPS > > > ****** a4:b1:e9:ef:1c:68 1 54M -36:-68 100 EP RSN > HTCAP > > > WPS WPA WME > > > ****** 9c:97:26:34:b7:cd 11 54M -41:-78 100 EP RSN > HTCAP > > > WPS WPA WME > > > ****** 24:ec:99:39:4a:12 11 54M -33:-62 100 EP RSN > HTCAP > > > WPS WPA WME > > > ****** 26:ec:99:39:4a:13 11 54M -31:-60 100 ES HTCAP > WME > > > ****** 10:fe:ed:c3:77:51 7 54M -40:-76 100 EPS RSN > HTCAP > > > WPA WME ATH WPS > > > Mynetwork5G 60:a4:4c:28:13:c4 44 54M -12:-20 100 EP RSN > HTCAP WME > > > > > > Second Scan > > > > > > % ifconfig wlan0 scan > > > SSID/MESH ID BSSID CHAN RATE S:N INT CAPS > > > ****** a4:b1:e9:ef:1c:68 1 54M -36:-68 100 EP RSN > HTCAP > > > WPS WPA WME > > > ****** 9c:97:26:34:b7:cd 11 54M -41:-78 100 EP RSN > HTCAP > > > WPS WPA WME > > > ****** 24:ec:99:39:4a:12 11 54M -33:-62 100 EP RSN > HTCAP > > > WPS WPA WME > > > ****** 26:ec:99:39:4a:13 11 54M -31:-60 100 ES HTCAP > WME > > > ****** 10:fe:ed:c3:77:51 7 54M -40:-76 100 EPS RSN > HTCAP > > > WPA WME ATH WPS > > > Mynetwork5G 60:a4:4c:28:13:c4 44 54M -12:-20 100 EP RSN > HTCAP WME > > > Mynetwork 60:a4:4c:28:13:c0 3 54M -18:-32 100 EP RSN > HTCAP WME > > > > > > > > > log from --> wpa_supplicant -i wlano -c /etc/wpa_supplicant.conf -d > > > NOTE: while doing this in wpa_supplicant.conf I only have my 5g > network! > > > > I have the same wlan dongle as yours but I have no problems connecting to > > the TL-WDR4300 on the 5 GHz band. This email is sent over the 5 GHz. > > I'll investigate further, thanks. > > > > # dmesg | grep run0 > > run0: <1.0> on usbus0 > > run0: MAC/BBP RT5592 (rev 0x0222), RF RT5592 (MIMO 2T2R), address > > f8:1a:67:2a:df:3f > > run0: firmware RT3071 ver. 0.33 loaded > > > > # ifconfig wlan0 > > wlan0: flags=8843 metric 0 mtu > 1500 > > ether f8:1a:67:2a:df:3f > > inet 192.168.0.101 netmask 0xffffff00 broadcast 192.168.0.255 > > nd6 options=29 > > media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11a > > status: associated > > ssid wng_5g channel 149 (5745 MHz 11a) bssid 64:66:b3:c2:3b:d4 > > country US authmode WPA2/802.11i privacy ON deftxkey UNDEF > > TKIP 2:128-bit txpower 0 bmiss 7 mcastrate 6 mgmtrate 6 > > scanvalid 60 > > wme roaming MANUAL > > Please try Akinori Furukoshi's patch, thanks. > > Index: sys/dev/usb/wlan/if_run.c > =================================================================== > --- sys/dev/usb/wlan/if_run.c (revision 269566) > +++ sys/dev/usb/wlan/if_run.c (working copy) > @@ -3255,13 +3255,13 @@ run_set_tx_desc(struct run_softc *sc, struct run_t > txwi = (struct rt2860_txwi *)(txd + 1); > txwi->len = htole16(m->m_pkthdr.len - pad); > if (rt2860_rates[ridx].phy == IEEE80211_T_DS) { > - txwi->phy = htole16(RT2860_PHY_CCK); > + mcs |= RT2860_PHY_CCK; > if (ridx != RT2860_RIDX_CCK1 && > (ic->ic_flags & IEEE80211_F_SHPREAMBLE)) > mcs |= RT2860_PHY_SHPRE; > } else > - txwi->phy = htole16(RT2860_PHY_OFDM); > - txwi->phy |= htole16(mcs); > + mcs |= RT2860_PHY_OFDM; > + txwi->phy = htole16(mcs); > > /* check if RTS/CTS or CTS-to-self protection is required */ > if (!IEEE80211_IS_MULTICAST(wh->i_addr1) && > @@ -3338,7 +3338,7 @@ run_tx(struct run_softc *sc, struct mbuf *m, struc > > /* pickup a rate index */ > if (IEEE80211_IS_MULTICAST(wh->i_addr1) || > - type != IEEE80211_FC0_TYPE_DATA) { > + type != IEEE80211_FC0_TYPE_DATA || m->m_flags & M_EAPOL) { > ridx = (ic->ic_curmode == IEEE80211_MODE_11A) ? > RT2860_RIDX_OFDM6 : RT2860_RIDX_CCK1; > ctl_ridx = rt2860_rates[ridx].ctl_ridx; > @@ -4998,7 +4998,7 @@ run_updateprot_cb(void *arg) > tmp = RT2860_RTSTH_EN | RT2860_PROT_NAV_SHORT | > RT2860_TXOP_ALLOW_ALL; > /* setup protection frame rate (MCS code) */ > tmp |= (ic->ic_curmode == IEEE80211_MODE_11A) ? > - rt2860_rates[RT2860_RIDX_OFDM6].mcs : > + rt2860_rates[RT2860_RIDX_OFDM6].mcs | RT2860_PHY_OFDM : > rt2860_rates[RT2860_RIDX_CCK11].mcs; > > /* CCK frames don't require protection */ > From owner-freebsd-wireless@FreeBSD.ORG Tue Aug 12 18:29:50 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 98E6F514 for ; Tue, 12 Aug 2014 18:29:50 +0000 (UTC) Received: from astart2.astart.com (108-248-95-193.lightspeed.sndgca.sbcglobal.net [108.248.95.193]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 727753D1C for ; Tue, 12 Aug 2014 18:29:50 +0000 (UTC) Received: from laptop_93.private (localhost [127.0.0.1]) by astart2.astart.com (8.14.4/8.14.4) with ESMTP id s7CITlvc085731 for ; Tue, 12 Aug 2014 11:29:47 -0700 (PDT) (envelope-from papowell@astart.com) Message-ID: <53EA5D1D.6010505@astart.com> Date: Tue, 12 Aug 2014 11:29:49 -0700 From: Patrick Powell Reply-To: papowell@astart.com Organization: Astart Technologies User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org Subject: Recommend Off the Shelf USB Wireless N - FreeBSD 9.3/10.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 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: Tue, 12 Aug 2014 18:29:50 -0000 Could anybody please please recommend a USB adapter for Wireless N that: a) works with the current set of drivers for FreeBSD 9.3-RELEASE or 10.0-RELEASE OR works with an update driver, and give the SVN release id. OR there are Windows Drivers for amd64, that can be converted using NDIS and that actually work... the .INF and .SYS files need to be provided/specified b) Can be bought via Amazon, or Rakuten, or a similar online store... even Ebay... If it is for Wireless G, or X or whatever flavor you have, I would still be interested. I'll bet there are other folks besides myself who would be grateful for such a posting. Also, this would be an opportunity to update the FreeBSD USB Adapter list. If there are responses to this posting, I would suggest that a summary be posted to one of the more general FreeBSD mailing lists. From owner-freebsd-wireless@FreeBSD.ORG Tue Aug 12 20:30:33 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 60515C12 for ; Tue, 12 Aug 2014 20:30:33 +0000 (UTC) Received: from mail-la0-x231.google.com (mail-la0-x231.google.com [IPv6:2a00:1450:4010:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DFD6E2D73 for ; Tue, 12 Aug 2014 20:30:32 +0000 (UTC) Received: by mail-la0-f49.google.com with SMTP id hz20so8160879lab.8 for ; Tue, 12 Aug 2014 13:30:30 -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; bh=authN4Y5yXFx87w4+fR+QnZAbEsTbSPYYPA0tS6unuM=; b=ruuneRMTyCPhIHlxqoaVIhV/t+erO9UjWUyk1sw9kCkJmvIyi4PLzmyCFKtQu1QmxV WRrtWa8jU9yLoTRAcYEp8gzLH0AUjSgPKLB4aSt63XRjloVNADBnsTDP0JeIGoZSucRl XTo12ftuCG2QR63JYUSQaFSP/TNO2A8QusTWmujOseNNBoIisyJIi1G8nCTiOhZqNTUJ kQKndEUrMKDw0P7JFQ8yoqt/kO/WhrB3ACbP63xWVLJ+s5cc0m5dHYWnSRm1iHhA46nv /3YA4Pwso1Mc8KY++9Rv6HMRfhJO0o4LPg90salHt6MGfGKkjF40Kl0EZ2UV5wURiOQl sYzg== MIME-Version: 1.0 X-Received: by 10.153.6.7 with SMTP id cq7mr58184lad.9.1407875430779; Tue, 12 Aug 2014 13:30:30 -0700 (PDT) Received: by 10.114.81.73 with HTTP; Tue, 12 Aug 2014 13:30:30 -0700 (PDT) In-Reply-To: <53EA5D1D.6010505@astart.com> References: <53EA5D1D.6010505@astart.com> Date: Tue, 12 Aug 2014 13:30:30 -0700 Message-ID: Subject: Re: Recommend Off the Shelf USB Wireless N - FreeBSD 9.3/10.0 From: hiren panchasara To: papowell@astart.com Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" 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: Tue, 12 Aug 2014 20:30:33 -0000 On Tue, Aug 12, 2014 at 11:29 AM, Patrick Powell wrote: > Could anybody please please recommend a USB adapter for Wireless N that: > > a) works with the current set of drivers for FreeBSD 9.3-RELEASE or > 10.0-RELEASE I think Edimax EW-7811Un - http://www.amazon.com/Edimax-EW-7811Un-Adapter-Raspberry-Supports/dp/B003MTTJOY/ref=sr_1_1?ie=UTF8&qid=1407874904&sr=8-1&keywords=Edimax+EW-7811Un should work on 10.0-RELEASE. 'man 4 urtwn' for more details. [skip] > > I'll bet there are other folks besides myself who would be grateful for such > a posting. > > Also, this would be an opportunity to update the FreeBSD USB Adapter list. > If there are responses to this posting, I would suggest that a summary be > posted to one of the more general FreeBSD mailing lists. fwiw, http://www.freebsd.org/relnotes/CURRENT/hardware/support.html mentions urtwn and the chipset. cheers, Hiren From owner-freebsd-wireless@FreeBSD.ORG Tue Aug 12 21:24:48 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EE378CA2 for ; Tue, 12 Aug 2014 21:24:48 +0000 (UTC) Received: from DUB004-OMC1S21.hotmail.com (dub004-omc1s21.hotmail.com [157.55.0.220]) (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 700BA252F for ; Tue, 12 Aug 2014 21:24:47 +0000 (UTC) Received: from DUB129-W82 ([157.55.0.239]) by DUB004-OMC1S21.hotmail.com with Microsoft SMTPSVC(7.5.7601.22712); Tue, 12 Aug 2014 14:23:37 -0700 X-TMN: [WDvoUagHcK6b9NxlZcaWiqe739ArifUE] X-Originating-Email: [cipher_nl@hotmail.com] Message-ID: From: CiPHER nl To: "freebsd-wireless@FreeBSD.org" Subject: Best supported WiFi adapter Date: Tue, 12 Aug 2014 23:23:37 +0200 Importance: Normal Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 12 Aug 2014 21:23:37.0976 (UTC) FILETIME=[AE5B7F80:01CFB673] 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: Tue, 12 Aug 2014 21:24:49 -0000 Dear BSD users=2C=0A= =0A= I am looking for the 'best supported WiFi adapter' for use with FreeBSD. I'= ve searched a bit=2C but could use some help.=0A= =0A= My requirements would be:=0A= - use with hostapd (to act as access point=3B not as client)=0A= - reliable operation without packet loss with a variety of clients in a hom= e network (i.e. not many clients)=0A= - WPA2 security=0A= =0A= Nice extra's would be:=0A= - support power saving mode (low power consumption)=0A= - 802.11n support (up to 300Mbps)=0A= =0A= At the moment i am using a USB WiFi adapter that uses the 'rum' driver. Tho= ugh it works in hostap mode=2C it does not support client power saving. Thi= s causes some clients to work while others can only connect to the WiFi but= not communicate or ping or do anything. Obviously this is not desirable=3B= i need something that works! Additionally=2C as someone who is very keen o= n lowering power consumption especially for 24/7 equipment=2C i would love = the power consumption to be lowered of both the server and the clients conn= ecting via WiFi. Thus power saving mode is highly desired. Having a more mo= dern 'n' 300Mbps network is a nice extra=2C but no hard requirement. Note t= hat i am in Europe=2C and 5GHz is not available/allowed as far as i know. 2= .4GHz is the norm here.=0A= =0A= Now i did some homework=2C like looking at the Wiki and reading manpages. A= lso looked at the hardware notes of 10.0-RELEASE. But what i am missing is = a list of 'best supported' network adapters=2C and product names which are = known to work properly. Perhaps this should be added to the Wiki=2C since i= can't believe i am the only one looking for a well supported WiFi adapter = for use with FreeBSD.=0A= =0A= Any suggestion or help is highly appreciated!=0A= =0A= Links:=0A= =0A= Manpage of rum(4)=2C describing the bug/issue that client power saving has = to be disabled=3B but not all clients offer this option - like Android phon= es.=0A= - http://www.freebsd.org/cgi/man.cgi?query=3Drum&apropos=3D0&sektion=3D0&ma= npath=3DFreeBSD+10.0-RELEASE&arch=3Ddefault&format=3Dhtml=0A= =0A= Wiki on WiFi with many links:=0A= - https://wiki.freebsd.org/WiFi=0A= =0A= Wiki listing support for newer chips like Atheros AR9287=2C but no products= mentioned which use these chips=0A= - https://wiki.freebsd.org/WiFi80211n=0A= - https://wiki.freebsd.org/dev/ath%284%29=0A= =0A= Manpage of Atheros ath(4) driver=2C listing limitations with power saving= =2C incompatbility with WPA with one chipset and even worse=2C the newer ch= ips like AR9287 are not mentioned:=0A= - http://www.freebsd.org/cgi/man.cgi?query=3Dath&apropos=3D0&sektion=3D0&ma= npath=3DFreeBSD+10.0-RELEASE&arch=3Ddefault&format=3Dhtml=0A= = From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 13 10:20:06 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 096BB92A for ; Wed, 13 Aug 2014 10:20:06 +0000 (UTC) Received: from mail.0x20.net (mail.0x20.net [217.69.76.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B775A20AE for ; Wed, 13 Aug 2014 10:20:05 +0000 (UTC) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id 399D76A6004; Wed, 13 Aug 2014 12:20:02 +0200 (CEST) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.7/8.14.7) with ESMTP id s7DAK1UO079265; Wed, 13 Aug 2014 12:20:01 +0200 (CEST) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.7/8.14.7/Submit) id s7DAK1Es078777; Wed, 13 Aug 2014 12:20:01 +0200 (CEST) (envelope-from lars) Date: Wed, 13 Aug 2014 12:20:01 +0200 From: Lars Engels To: hiren panchasara Subject: Re: Recommend Off the Shelf USB Wireless N - FreeBSD 9.3/10.0 Message-ID: <20140813102000.GB26895@e-new.0x20.net> References: <53EA5D1D.6010505@astart.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="6FinHCQBQ0zFDOqT" Content-Disposition: inline In-Reply-To: X-Editor: VIM - Vi IMproved 7.4 X-Operation-System: FreeBSD 8.4-RELEASE-p4 User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "freebsd-wireless@freebsd.org" 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: Wed, 13 Aug 2014 10:20:06 -0000 --6FinHCQBQ0zFDOqT Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 12, 2014 at 01:30:30PM -0700, hiren panchasara wrote: > On Tue, Aug 12, 2014 at 11:29 AM, Patrick Powell wr= ote: > > Could anybody please please recommend a USB adapter for Wireless N that: > > > > a) works with the current set of drivers for FreeBSD 9.3-RELEASE or > > 10.0-RELEASE > I think >=20 > Edimax EW-7811Un - > http://www.amazon.com/Edimax-EW-7811Un-Adapter-Raspberry-Supports/dp/B003= MTTJOY/ref=3Dsr_1_1?ie=3DUTF8&qid=3D1407874904&sr=3D8-1&keywords=3DEdimax+E= W-7811Un >=20 > should work on 10.0-RELEASE. >=20 > 'man 4 urtwn' for more details. >=20 > [skip] > > > > I'll bet there are other folks besides myself who would be grateful for= such > > a posting. > > > > Also, this would be an opportunity to update the FreeBSD USB Adapter l= ist. > > If there are responses to this posting, I would suggest that a summar= y be > > posted to one of the more general FreeBSD mailing lists. >=20 > fwiw, http://www.freebsd.org/relnotes/CURRENT/hardware/support.html > mentions urtwn and the chipset. =46rom http://www.freebsd.org/cgi/man.cgi?query=3Durtwn&apropos=3D0&sektion=3D0&ma= npath=3DFreeBSD+11-current&arch=3Ddefault&format=3Dhtml CAVEATS The urtwn driver does not support any of the 802.11n capabilities offe= red by the adapters. --6FinHCQBQ0zFDOqT Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQF8BAEBCgBmBQJT6zvQXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4RjQwMDE3RTRERjUzMTI1N0FGRTUxNDlF NTRDQjM3RDNBMDg5RDZEAAoJEOVMs306CJ1tNDwH/ij5jjAAzwTKqjDCF1RttOtU n8rZNgcPJvYE5jgWk3Cir+qmbQFva86BTVTpcj6RnaLLgU4h4M3do5J/itu0HkwK QPb2/IsjVeT4P5RNNcVr9XlIw/4WqJbttT47EiK3UEDLy7xrIiA8wUO2NW1hrtPi PsUf+j+k1ee0pe8FbsXqjw+w0z9bijOLYJFgh1o/IKTBMVplL8b2WlghAiWM1T5W MzLTwmZDMiIPId/RaWcECQTyb9S8CgE/cANveYXr5xnM7BfTW4Xb+cbrbmenKD1S Nxxjq9RhQjV1pnrVZz6fWxX9xbybo9DzBnQCitLibscNjS2WRBai6FDK1Jbd9xU= =AB/M -----END PGP SIGNATURE----- --6FinHCQBQ0zFDOqT-- From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 13 13:25:38 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 4D7A979C for ; Wed, 13 Aug 2014 13:25:38 +0000 (UTC) Received: from mail-pd0-x233.google.com (mail-pd0-x233.google.com [IPv6:2607:f8b0:400e:c02::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 244562758 for ; Wed, 13 Aug 2014 13:25:38 +0000 (UTC) Received: by mail-pd0-f179.google.com with SMTP id v10so8573376pde.10 for ; Wed, 13 Aug 2014 06:25:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:message-id:date:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=iWX7yDA1e0XFxghCa36xDDyrixvf0+rxJuewqZ+s2Pw=; b=il8O6kNlxSFEM/yJORSB2XM+H8W+AZ/kR+gq4GYEl0xkPXz+3MprxetQJdtLySaeX2 Z2RNZL6mmMpD528onoN6Rhgfpff74jNS/AWEvNZdXR0fbe6SGx/S4tBKfKNv1xOSqpUW okjL2f0zQC2VPQ1Yv1fJt8L8gRV0MyFtBZpXof6fTi0saVBahwRwI7swnUsOroK4PsGG ttmWwHH46hWUDHqvAecWWOLv4IP42E/pjg/cYgbPZEgisulgAJj8OMfX/uYvhQlrISFd eZEvL3Qpy1bo8Y5AJgPtWAqSz/DNRmfK4H7h/4jLFKFt8ch4Tnofqb72m4Z8y9WP/2CS guWg== X-Received: by 10.68.69.8 with SMTP id a8mr929879pbu.165.1407936337530; Wed, 13 Aug 2014 06:25:37 -0700 (PDT) Received: from limbo.b1t.lan (167.203-pool.nikopol.net. [213.111.203.167]) by mx.google.com with ESMTPSA id fh2sm2140314pbb.89.2014.08.13.06.25.35 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Aug 2014 06:25:36 -0700 (PDT) From: Volodymyr Kostyrko X-Google-Original-From: Volodymyr Kostyrko Message-ID: <53EB674D.30403@b1t.name> Date: Wed, 13 Aug 2014 16:25:33 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: freebsd-wireless@FreeBSD.org Subject: old new device: another sample of DWA-125 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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: Wed, 13 Aug 2014 13:25:38 -0000 Hi all. I have something called DWA-125 (model D1A, h/w ver: D1, f/w ver: 4.00). # usbconfig -d 6.2 dump_device_desc ugen6.2: at usbus6, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0000 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0040 idVendor = 0x2001 idProduct = 0x330f bcdDevice = 0x0000 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 bNumConfigurations = 0x0001 Patch to detect it: Index: sys/dev/usb/usbdevs =================================================================== --- sys/dev/usb/usbdevs (revision 269923) +++ sys/dev/usb/usbdevs (working copy) @@ -1624,6 +1624,7 @@ product DLINK RTL8192CU_1 0x3307 RTL8192CU product DLINK RTL8192CU_2 0x3309 RTL8192CU product DLINK RTL8192CU_3 0x330a RTL8192CU +product DLINK RTL8192CU_4 0x330f RTL8192CU product DLINK DWA131B 0x330d DWA-131 rev B product DLINK2 RTL8192SU_1 0x3300 RTL8192SU product DLINK2 RTL8192SU_2 0x3302 RTL8192SU Index: sys/dev/usb/wlan/if_urtwn.c =================================================================== --- sys/dev/usb/wlan/if_urtwn.c (revision 269923) +++ sys/dev/usb/wlan/if_urtwn.c (working copy) @@ -112,6 +112,7 @@ URTWN_DEV(DLINK, RTL8192CU_1), URTWN_DEV(DLINK, RTL8192CU_2), URTWN_DEV(DLINK, RTL8192CU_3), + URTWN_DEV(DLINK, RTL8192CU_4), URTWN_DEV(DLINK, DWA131B), URTWN_DEV(EDIMAX, EW7811UN), URTWN_DEV(EDIMAX, RTL8192CU), # kldload urtwn Aug 13 16:10:19 limbo kernel: urtwn0: on usbus6 Aug 13 16:10:20 limbo kernel: urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R urtwn0: flags=8802 metric 0 mtu 2290 ether 00:00:a8:1d:f3:b7 nd6 options=21 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier # ifconfig wlan0 create wlandev urtwn0 # ifconfig wlan0 country ua # ifconfig wlan0 up scan Gives nothing. # ifconfig wlan0 wlan0: flags=8843 metric 0 mtu 1500 ether 00:00:a8:1d:f3:b7 inet6 fe80::200:a8ff:fe1d:f3b7%wlan0 prefixlen 64 scopeid 0x7 nd6 options=21 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid "" channel 1 (2412 MHz 11b) regdomain NONE country UA authmode OPEN privacy OFF txpower 30 bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 1 bintval 0 # ifconfig wlan0 list caps drivercaps=2181c001 Is there any easy way to make it work or should I just dump it? -- Sphinx of black quartz judge my vow. From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 13 16:05:46 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 47D32AD8 for ; Wed, 13 Aug 2014 16:05:46 +0000 (UTC) Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com [IPv6:2a00:1450:4010:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C8BC62A4E for ; Wed, 13 Aug 2014 16:05:45 +0000 (UTC) Received: by mail-lb0-f171.google.com with SMTP id l4so8534457lbv.30 for ; Wed, 13 Aug 2014 09:05:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=BXyF/1E2sFdSyAXw/BqkeNrer0fu5pTdwC972gMyBLE=; b=KPDUsKCAHASugOJOlM5Qpg2w76+8ESBtGiCjDVV+jTwei4ymo17yr35ubRBOuWROH+ Uono3z8cHNtekcFYMuKCBA1YyT9Cdyr8/ZeKHUcVN/pmiDQyZeE/YcGRiJ3KclTZAsOX lYHXwRZEyk08yoZbDdc6EhRxP/WOzZE9lE4Lmfgl6I3UP9fZMEpslguaTkv4+bsqKsA+ EtPK8itWGYD3ivKpVmMIWSdCbjMyb65X41TvOjy8o12iIEkPSnvHRUtD9lru78Uz7T// h11cKsKaJfzvkNHUO1MrzTcfEAWR0etS/S8aqOwVQGnNCbqxhXkDUjfLECXhgJjfSUqi +x+w== MIME-Version: 1.0 X-Received: by 10.112.106.67 with SMTP id gs3mr5379517lbb.84.1407945943596; Wed, 13 Aug 2014 09:05:43 -0700 (PDT) Received: by 10.112.164.99 with HTTP; Wed, 13 Aug 2014 09:05:43 -0700 (PDT) Date: Wed, 13 Aug 2014 09:05:43 -0700 Message-ID: Subject: DMA Errors with Broadcom 4312 on FreeBSD 10.0 From: Chris W To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 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: Wed, 13 Aug 2014 16:05:46 -0000 I've got a Broadcom 4312 LP PHY device that is giving me DMA errors. device = 'BCM4312 802.11b/g LP-PHY' I'm loading the module on boot: if_bwn_load="YES" bwn_v4_lp_ucode="YES" I'm able to connect to an access point for about 5 minutes after startup; however, I then lose connectivity and unable to reconnect without a reboot. Performing an ifconfig wlan0 down/up does not work. Here's a summary of dmesg: bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) bwn0: Fatal DMA error: 0x400 0 0 0 0 0 bwn0: HW reset: DMA error bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) bwn0: Fatal DMA error: 0x400 0 0 0 0 0 bwn0: HW reset: DMA error This just continues to fill up /var/log/messages. Does anybody know if there's a fix for this? Or if there's a even a maintainer at this point? Thanks for the help. From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 13 16:51:01 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F381CD7F for ; Wed, 13 Aug 2014 16:51:00 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D4B3420A4 for ; Wed, 13 Aug 2014 16:51:00 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s7DGp0jE085930 for ; Wed, 13 Aug 2014 16:51:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192641] New: [iwn] panic in AMPDU tx code "ni: no node" Date: Wed, 13 Aug 2014 16:51:00 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Wed, 13 Aug 2014 16:51:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D192641 Bug ID: 192641 Summary: [iwn] panic in AMPDU tx code "ni: no node" Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: wireless Assignee: freebsd-wireless@FreeBSD.org Reporter: adrian@freebsd.org (kgdb) bt #0 doadump (textdump=3D-1059352868) at pcpu.h:233 #1 0xc04f92cd in db_fncall (dummy1=3D-332454048, dummy2=3D0, dummy3=3D-951= 087536, dummy4=3D0xec2f274c "=EF=BF=BD&R=EF=BF=BD=EF=BF=BD\216=EF=BF=BD=EF=BF=BD") = at /usr/home/adrian/work/freebsd/head/src/sys/ddb/db_command.c:578 #2 0xc04f8fab in db_command (cmd_table=3D) at /usr/home/adrian/work/freebsd/head/src/sys/ddb/db_command.c:449 #3 0xc04f8cf0 in db_command_loop () at /usr/home/adrian/work/freebsd/head/src/sys/ddb/db_command.c:502 #4 0xc04fb640 in db_trap (type=3D, code=3D) at /usr/home/adrian/work/freebsd/head/src/sys/ddb/db_main.c:231 #5 0xc06c2bf4 in kdb_trap (type=3D, code=3D, tf=3D) at /usr/home/adrian/work/freebsd/head/src/sys/kern/subr_kdb.c:654 #6 0xc093df67 in trap (frame=3D) at /usr/home/adrian/work/freebsd/head/src/sys/i386/i386/trap.c:693 #7 0xc0926a7c in calltrap () at /usr/home/adrian/work/freebsd/head/src/sys/i386/i386/exception.s:169 #8 0xc06c247d in kdb_enter (why=3D0xc09ba864 "panic", msg=3D) at cpufunc.h:71 #9 0xc0687f61 in vpanic (fmt=3D, ap=3D) at /usr/home/adrian/work/freebsd/head/src/sys/kern/kern_shutdown.c:739 #10 0xc0687e13 in kassert_panic (fmt=3D) at /usr/home/adrian/work/freebsd/head/src/sys/kern/kern_shutdown.c:634 #11 0xc8f14751 in iwn_ampdu_tx_done (sc=3D0xc8f21000, qid=3D10, idx=3D, nframes=3D1, stat=3D) at /usr/home/adrian/work/freebsd/head/src/sys/modules/iwn/../../dev/iwn/if_iwn= .c:3613 #12 0xc8f13eb5 in iwn5000_tx_done (sc=3D, desc=3D, data=3D) at /usr/home/adrian/work/freebsd/head/src/sys/modules/iwn/../../dev/iwn/if_iwn= .c:3411 #13 0xc8f0b9ff in iwn_notif_intr (sc=3D0xc8f21000) at /usr/home/adrian/work/freebsd/head/src/sys/modules/iwn/../../dev/iwn/if_iwn= .c:3696 #14 0xc8f0b2e0 in iwn_intr (arg=3D0xc8f21000) at /usr/home/adrian/work/freebsd/head/src/sys/modules/iwn/../../dev/iwn/if_iwn= .c:3995 #15 0xc0655913 in intr_event_execute_handlers (ie=3D) = at /usr/home/adrian/work/freebsd/head/src/sys/kern/kern_intr.c:1252 #16 0xc0656213 in ithread_loop (arg=3D0xc85e6ee0) at /usr/home/adrian/work/freebsd/head/src/sys/kern/kern_intr.c:1265 #17 0xc0652e2f in fork_exit (callout=3D0xc0656180 ) at /usr/home/adrian/work/freebsd/head/src/sys/kern/kern_fork.c:977 #18 0xc0926b24 in fork_trampoline () at /usr/home/adrian/work/freebsd/head/src/sys/i386/i386/exception.s:278 Current language: auto; currently minimal (kgdb) frame 11 #11 0xc8f14751 in iwn_ampdu_tx_done (sc=3D0xc8f21000, qid=3D10, idx=3D, nframes=3D1, stat=3D) at /usr/home/adrian/work/freebsd/head/src/sys/modules/iwn/../../dev/iwn/if_iwn= .c:3613 3613 KASSERT(ni !=3D NULL, ("no node")); (kgdb) print ni $1 =3D (kgdb)=20 .. and leading up to it: Unread portion of the kernel message buffer: iwn0: iwn_tx_data: m=3D0xc9572900: seqno (53004) (12) !=3D ring index (0) ! iwn0: iwn_tx_data: m=3D0xc896f200: seqno (53005) (13) !=3D ring index (1) ! panic: no node cpuid =3D 1 KDB: stack backtrace: db_trace_self_wrapper(c09bf552,ec2f29b8,fc,10000000,0,...) at db_trace_self_wrapper+0x2d/frame 0xec2f29a0 kdb_backtrace(c09fc9a7,1,c8f18b78,ec2f2a8c,ec2f2a30,...) at kdb_backtrace+0x30/frame 0xec2f2a08 vpanic(c0af9f18,100,c8f18b78,ec2f2a8c,4000ace,...) at vpanic+0x11d/frame 0xec2f2a44 kassert_panic(c8f18b78,5,cdd25c00,cdd25c00,c8d6dc00,...) at kassert_panic+0x153/frame 0xec2f2a80 iwn_ampdu_tx_done(0,1,cae8f028,c0671aa1,c8f2100c,...) at iwn_ampdu_tx_done+0x251/frame 0xec2f2adc iwn5000_tx_done(c8f21000,cae8f000,c8f3a934,bd2,c8f0dea0,...) at iwn5000_tx_done+0xe5/frame 0xec2f2b20 iwn_notif_intr(c8f2101c,0,c8f18029,f5a,c0b07b80,...) at iwn_notif_intr+0x4bf/frame 0xec2f2bd0 iwn_intr(c8f21000,c09b3975,4e0,c09b3b43,c09b3b68,...) at iwn_intr+0x7c0/fra= me 0xec2f2c3c intr_event_execute_handlers(c7492bc0,c86c6480,c09b3975,55a,3c9,...) at intr_event_execute_handlers+0xe3/frame 0xec2f2c80 ithread_loop(c85e6ee0,ec2f2d08,c09b367a,3c9,0,...) at ithread_loop+0x93/fra= me 0xec2f2ccc fork_exit(c0656180,c85e6ee0,ec2f2d08) at fork_exit+0x7f/frame 0xec2f2cf4 fork_trampoline() at fork_trampoline+0x8/frame 0xec2f2cf4 --- trap 0, eip =3D 0, esp =3D 0xec2f2d40, ebp =3D 0 --- KDB: enter: panic .. so something went a little pear shaped and we didn't handle it right. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 13 18:11:04 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 2BA8F601; Wed, 13 Aug 2014 18:11:04 +0000 (UTC) Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 962A329C1; Wed, 13 Aug 2014 18:11:03 +0000 (UTC) Received: by mail-wi0-f172.google.com with SMTP id n3so7812621wiv.11 for ; Wed, 13 Aug 2014 11:11:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=mAcfWPJzK7vSN7SC5XjG5GHz2DeXMnZpa31MOhjgge4=; b=CMYxDqdQ3eO7E8FZztEdVaJrYT3QrIyaTTlckaefhn4rlawEcc9Aqm4XCZJIOtIQhT GMfG9eQoqfzMGZ1UzCgh0kFtBzHiNXJpA4EjOK8ruOsli7bA8AOIR8hdKt1tLqtuaqcb 7ZVmM2AlURluIH9gqwYsjaTcUI8FCrZmwAHJeb4uJKA6hF6rHIEXSPPkF/ckHKQuumnC 1W6d0L8hFtjUsQxHIpgSk2RQHgLyQg5m0JuUjI4hp704TsY0F5MJGJAYB2ekd1i8zPGu xXOqbFcBQsyLJDvZ9ULH4iJzkdcIQIRIl4R2tzE+kcBrAPK8Tk6eVKEYU1rJOatylqcU /cWg== X-Received: by 10.180.38.39 with SMTP id d7mr6438455wik.24.1407953461505; Wed, 13 Aug 2014 11:11:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.121.37 with HTTP; Wed, 13 Aug 2014 11:10:41 -0700 (PDT) In-Reply-To: References: <53DE4FD2.8050309@FreeBSD.org> <20140805092636.GA41308@ns.kevlo.org> From: Miguel Clara Date: Wed, 13 Aug 2014 19:10:41 +0100 Message-ID: Subject: Re: FreeBSD current RT3071 can't connect to 5G network To: Kevin Lo Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-wireless@freebsd.org 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: Wed, 13 Aug 2014 18:11:04 -0000 Hi, just wanted to report that the patch made no difference. However I created a guest network in my router with the same password and also using WPA2, and it connects to it. the only difference is the BSSID, so I wonder if this is a issue with wpa and nothing to to with the driver? But the performance is still horrible! From owner-freebsd-wireless@FreeBSD.ORG Thu Aug 14 13:13:36 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 E20CCB48 for ; Thu, 14 Aug 2014 13:13:36 +0000 (UTC) Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7AF2E2568 for ; Thu, 14 Aug 2014 13:13:36 +0000 (UTC) Received: by mail-wi0-f172.google.com with SMTP id n3so8901066wiv.11 for ; Thu, 14 Aug 2014 06:13:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:cc :content-type; bh=TqrxtqdrBwklc072Tjv+ZQZnZy3Lep6HltagbqTkyHo=; b=lK+SctrIhO5EDQeyY4aI5awDqPLbgPHIDm761LdkRrZyEOa6urxNnk2J4T5BPdJrXP fkpEzNQxu13RVsphjlBYU0nvLPEbxkSbQIOGbs665oTkOyIFgz2N8hF9V8gtZXtW5N8Q DOqn05MkruY8XVHPuCWvTZyML0e1xuLz4BaoIQ43uTN/y9rVAWq+ipEb9j9EJvN17e0v EuHHEY+AY5YBHUU775s8X1Rfgml4EctCFS6yG7yWn7RAKwLfzHwn1W8LFokvSFFUcVAB 1JHpj9bgYN6vf8seDkvHvQr85svhoLKFZV8exkgsjNNK27izfC9HQfc5iY5MrEDHGKyj w4RQ== X-Received: by 10.180.104.163 with SMTP id gf3mr45726235wib.24.1408022013411; Thu, 14 Aug 2014 06:13:33 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.121.37 with HTTP; Thu, 14 Aug 2014 06:13:13 -0700 (PDT) In-Reply-To: References: <53DE4FD2.8050309@FreeBSD.org> <20140805092636.GA41308@ns.kevlo.org> From: Miguel Clara Date: Thu, 14 Aug 2014 14:13:13 +0100 Message-ID: Subject: Re: FreeBSD current RT3071 can't connect to 5G network Cc: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 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: Thu, 14 Aug 2014 13:13:37 -0000 On Wed, Aug 13, 2014 at 7:10 PM, Miguel Clara wrote: > Hi, just wanted to report that the patch made no difference. > > However I created a guest network in my router with the same password and > also using WPA2, and it connects to it. > > the only difference is the BSSID, so I wonder if this is a issue with wpa > and nothing to to with the driver? > NOTE: it works well if using ath driivers so the problem is probably in the driver indeed! > But the performance is still horrible! > > > > From owner-freebsd-wireless@FreeBSD.ORG Thu Aug 14 14:09:49 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 05846F50 for ; Thu, 14 Aug 2014 14:09:49 +0000 (UTC) Received: from mail-we0-x235.google.com (mail-we0-x235.google.com [IPv6:2a00:1450:400c:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 85D672AB3 for ; Thu, 14 Aug 2014 14:09:48 +0000 (UTC) Received: by mail-we0-f181.google.com with SMTP id k48so1130557wev.26 for ; Thu, 14 Aug 2014 07:09:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=NJ98e/0+MmZydAhfHcbh0XDh6nPH4bL2SZARiE86Xts=; b=ccZQQc4hJPHMT3hPiJfoaKvQNe0uu5MQIz/57SKqSKsOHZEZFpWeGFL5lnUHjPqiFZ 9bpHD+SmxtzAdwdj5nJaf32MqlYfH3Q+VFn7jUTkxMmRoLnDGHovUYJwR+Pd7thTgc42 QQOAesXy/1uo42vKz99Lesgq/51AfRPieGG9mWDcsUrLWOxWQd5aeflU6LfVye22PZaG vbeYpF0yXJWzvdBdSBXzRxHoJ0QzVlz9TIo5NIrMQ815bOEF6PjKZDj4ilutuhc1XEY8 yJyPDjhrtVQCUTAMp/t40COwpx6acZHYs2D4QgzT44JPl1uRKgtaJxXa/L4WELQUdh/d GJqg== X-Received: by 10.180.21.208 with SMTP id x16mr12733010wie.73.1408025384198; Thu, 14 Aug 2014 07:09:44 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.121.37 with HTTP; Thu, 14 Aug 2014 07:09:23 -0700 (PDT) In-Reply-To: References: <53DE4FD2.8050309@FreeBSD.org> <20140805092636.GA41308@ns.kevlo.org> From: Miguel Clara Date: Thu, 14 Aug 2014 15:09:23 +0100 Message-ID: Subject: Re: FreeBSD current RT3071 can't connect to 5G network To: Miguel Clara Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-wireless@freebsd.org 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: Thu, 14 Aug 2014 14:09:49 -0000 Duh, I figured it out... by default the Asus Guest netwroks are created in "auto" mode, so both N and legacy, while my 5G network was set to N only (2.4 is set to auto too). This also explain the poor performance now... for some reason 11n is not working only 11g/a. ifconfig wlan0 mode 11na or 11ng gives me device is not configured (This works fine for the ath card tough)! Melhores Cumprimentos // Best Regards ----------------------------------------------- *Miguel Clara* *IT - Sys Admin & Developer* *E-mail: *miguelmclara@gmail.com www.linkedin.com/in/miguelmclara/ On Thu, Aug 14, 2014 at 2:13 PM, Miguel Clara wrote: > > > On Wed, Aug 13, 2014 at 7:10 PM, Miguel Clara > wrote: > >> Hi, just wanted to report that the patch made no difference. >> >> However I created a guest network in my router with the same password and >> also using WPA2, and it connects to it. >> >> the only difference is the BSSID, so I wonder if this is a issue with wpa >> and nothing to to with the driver? >> > > NOTE: it works well if using ath driivers so the problem is probably in > the driver indeed! > > >> But the performance is still horrible! >> >> >> >> > From owner-freebsd-wireless@FreeBSD.ORG Thu Aug 14 22:00:16 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 5A4C0DB for ; Thu, 14 Aug 2014 22:00:16 +0000 (UTC) Received: from mail.0x20.net (mail.0x20.net [217.69.76.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A10A93292 for ; Thu, 14 Aug 2014 20:42:52 +0000 (UTC) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id 352346A6004; Thu, 14 Aug 2014 22:42:49 +0200 (CEST) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.7/8.14.7) with ESMTP id s7EKgmJW061412; Thu, 14 Aug 2014 22:42:48 +0200 (CEST) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.7/8.14.7/Submit) id s7EKgmRe060102; Thu, 14 Aug 2014 22:42:48 +0200 (CEST) (envelope-from lars) Date: Thu, 14 Aug 2014 22:42:48 +0200 From: Lars Engels To: Miguel Clara Subject: Re: FreeBSD current RT3071 can't connect to 5G network Message-ID: <20140814204247.GK98029@e-new.0x20.net> References: <53DE4FD2.8050309@FreeBSD.org> <20140805092636.GA41308@ns.kevlo.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="pN9MePJoZbRKbUk1" Content-Disposition: inline In-Reply-To: X-Editor: VIM - Vi IMproved 7.4 X-Operation-System: FreeBSD 8.4-RELEASE-p4 User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-wireless@freebsd.org 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: Thu, 14 Aug 2014 22:00:16 -0000 --pN9MePJoZbRKbUk1 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 14, 2014 at 03:09:23PM +0100, Miguel Clara wrote: > Duh, I figured it out... by default the Asus Guest netwroks are created in > "auto" mode, so both N and legacy, while my 5G network was set to N only > (2.4 is set to auto too). >=20 > This also explain the poor performance now... for some reason 11n is not > working only 11g/a. >=20 > ifconfig wlan0 mode 11na or 11ng gives me device is not configured (This > works fine for the ath card tough)! Thanks a lot, I had just the same issue with my=20 run0: MAC/BBP RT5390 (rev 0x0502), RF RT5370 (MIMO 1T1R), address 7c:dd:90:= 30:b6:a1 device. Now switched to mixed mode and it just works. :) --pN9MePJoZbRKbUk1 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQF8BAEBCgBmBQJT7R9HXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4RjQwMDE3RTRERjUzMTI1N0FGRTUxNDlF NTRDQjM3RDNBMDg5RDZEAAoJEOVMs306CJ1twywH/2YuGGUQCfFJwMg5YLmK4QBS MrfGwrZf6r9AK67t5z9lmHhEvsu5RFO0GQIKVvUQ7MhZe8gzD0EUStrs0Nh2flH2 va90qNRxFIs/3IUk+nuG3x6+SdkO8le6qUiLtumBWwWkH7hpg6sWhuNaDE0GrYea PHiFhlRj9lypJ6SNteTTL5C6weXMDHrkrqghsHmbSl/bbGCWubh9v1p3VGCeh1LM gb9PLeYD6UHI+pec+ITH9Q+nWIujc6nTC9xtIOy0B1v059+DiIBtPSMdExfWlMZx FjXwN5riPOdheHAXh7VBT3iakqL8fRT4R9m9EJEUBkrxy6b5TvxwrUx/rCwJsNc= =8UZC -----END PGP SIGNATURE----- --pN9MePJoZbRKbUk1-- From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 15 01:41:58 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 9534878A for ; Fri, 15 Aug 2014 01:41:58 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 491AA2DAE for ; Fri, 15 Aug 2014 01:41:54 +0000 (UTC) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.14.8/8.14.8) with ESMTP id s7F1fJ3c035516 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 15 Aug 2014 09:41:19 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.14.8/8.14.8/Submit) id s7F1fJHY035515; Fri, 15 Aug 2014 09:41:19 +0800 (CST) (envelope-from kevlo) Date: Fri, 15 Aug 2014 09:41:18 +0800 From: Kevin Lo To: Volodymyr Kostyrko Subject: Re: old new device: another sample of DWA-125 Message-ID: <20140815014118.GA35503@ns.kevlo.org> References: <53EB674D.30403@b1t.name> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53EB674D.30403@b1t.name> User-Agent: Mutt/1.5.22 (2013-10-16) Cc: freebsd-wireless@FreeBSD.org 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: Fri, 15 Aug 2014 01:41:58 -0000 On Wed, Aug 13, 2014 at 04:25:33PM +0300, Volodymyr Kostyrko wrote: > > Hi all. Hi, > I have something called DWA-125 (model D1A, h/w ver: D1, f/w ver: 4.00). > > # usbconfig -d 6.2 dump_device_desc > ugen6.2: at usbus6, cfg=0 md=HOST > spd=HIGH (480Mbps) pwr=ON (500mA) > > bLength = 0x0012 > bDescriptorType = 0x0001 > bcdUSB = 0x0200 > bDeviceClass = 0x0000 > bDeviceSubClass = 0x0000 > bDeviceProtocol = 0x0000 > bMaxPacketSize0 = 0x0040 > idVendor = 0x2001 > idProduct = 0x330f > bcdDevice = 0x0000 > iManufacturer = 0x0001 > iProduct = 0x0002 > iSerialNumber = 0x0003 > bNumConfigurations = 0x0001 > > Patch to detect it: > > Index: sys/dev/usb/usbdevs > =================================================================== > --- sys/dev/usb/usbdevs (revision 269923) > +++ sys/dev/usb/usbdevs (working copy) > @@ -1624,6 +1624,7 @@ > product DLINK RTL8192CU_1 0x3307 RTL8192CU > product DLINK RTL8192CU_2 0x3309 RTL8192CU > product DLINK RTL8192CU_3 0x330a RTL8192CU > +product DLINK RTL8192CU_4 0x330f RTL8192CU > product DLINK DWA131B 0x330d DWA-131 rev B > product DLINK2 RTL8192SU_1 0x3300 RTL8192SU > product DLINK2 RTL8192SU_2 0x3302 RTL8192SU > Index: sys/dev/usb/wlan/if_urtwn.c > =================================================================== > --- sys/dev/usb/wlan/if_urtwn.c (revision 269923) > +++ sys/dev/usb/wlan/if_urtwn.c (working copy) > @@ -112,6 +112,7 @@ > URTWN_DEV(DLINK, RTL8192CU_1), > URTWN_DEV(DLINK, RTL8192CU_2), > URTWN_DEV(DLINK, RTL8192CU_3), > + URTWN_DEV(DLINK, RTL8192CU_4), > URTWN_DEV(DLINK, DWA131B), > URTWN_DEV(EDIMAX, EW7811UN), > URTWN_DEV(EDIMAX, RTL8192CU), > > # kldload urtwn > Aug 13 16:10:19 limbo kernel: urtwn0: class 0/0, rev 2.00/0.00, addr 1> on usbus6 > Aug 13 16:10:20 limbo kernel: urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R > > urtwn0: flags=8802 metric 0 mtu 2290 > ether 00:00:a8:1d:f3:b7 > nd6 options=21 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > > # ifconfig wlan0 create wlandev urtwn0 > # ifconfig wlan0 country ua > # ifconfig wlan0 up scan > > Gives nothing. > > # ifconfig wlan0 > wlan0: flags=8843 metric 0 mtu 1500 > ether 00:00:a8:1d:f3:b7 > inet6 fe80::200:a8ff:fe1d:f3b7%wlan0 prefixlen 64 scopeid 0x7 > nd6 options=21 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > ssid "" channel 1 (2412 MHz 11b) > regdomain NONE country UA authmode OPEN privacy OFF txpower 30 > bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 > roam:rssi 7 > roam:rate 1 bintval 0 > > # ifconfig wlan0 list caps > drivercaps=2181c001 > > Is there any easy way to make it work or should I just dump it? The D-Link DWA-125 rev D1 uses the RTL8188EU chip. Please try this patch, thanks. Index: sys/dev/usb/usbdevs =================================================================== --- sys/dev/usb/usbdevs (revision 270007) +++ sys/dev/usb/usbdevs (working copy) @@ -1592,6 +1592,7 @@ product DLINK DUBE100 0x1a00 10/100 Ethernet product DLINK DUBE100C1 0x1a02 DUB-E100 rev C1 product DLINK DSB650TX4 0x200c 10/100 Ethernet product DLINK DWL120E 0x3200 DWL-120 rev E +product DLINK DWA125D1 0x330f DWA-125 rev D1 product DLINK DWL122 0x3700 DWL-122 product DLINK DWLG120 0x3701 DWL-G120 product DLINK DWL120F 0x3702 DWL-120 rev F Index: sys/dev/usb/wlan/if_urtwn.c =================================================================== --- sys/dev/usb/wlan/if_urtwn.c (revision 270007) +++ sys/dev/usb/wlan/if_urtwn.c (working copy) @@ -152,6 +152,7 @@ static const STRUCT_USB_HOST_ID urtwn_devs[] = { URTWN_DEV(TRENDNET, RTL8192CU), URTWN_DEV(ZYXEL, RTL8192CU), /* URTWN_RTL8188E */ + URTWN_RTL8188E_DEV(DLINK, DWA125D1), URTWN_RTL8188E_DEV(REALTEK, RTL8188ETV), URTWN_RTL8188E_DEV(REALTEK, RTL8188EU), #undef URTWN_RTL8188E_DEV From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 15 03:07:01 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 75B2BF67 for ; Fri, 15 Aug 2014 03:07:01 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C036D2758 for ; Fri, 15 Aug 2014 03:07:00 +0000 (UTC) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.14.8/8.14.8) with ESMTP id s7F36WEL036072 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 15 Aug 2014 11:06:32 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.14.8/8.14.8/Submit) id s7F36W7W036071; Fri, 15 Aug 2014 11:06:32 +0800 (CST) (envelope-from kevlo) Date: Fri, 15 Aug 2014 11:06:31 +0800 From: Kevin Lo To: Miguel Clara Subject: Re: FreeBSD current RT3071 can't connect to 5G network Message-ID: <20140815030631.GA36062@ns.kevlo.org> References: <53DE4FD2.8050309@FreeBSD.org> <20140805092636.GA41308@ns.kevlo.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.22 (2013-10-16) Cc: freebsd-wireless@freebsd.org 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: Fri, 15 Aug 2014 03:07:01 -0000 All USB wifi dongles in FreeBSD don't support 11n yet. Kevin On Thu, Aug 14, 2014 at 03:09:23PM +0100, Miguel Clara wrote: > > Duh, I figured it out... by default the Asus Guest netwroks are created in > "auto" mode, so both N and legacy, while my 5G network was set to N only > (2.4 is set to auto too). > > This also explain the poor performance now... for some reason 11n is not > working only 11g/a. > > ifconfig wlan0 mode 11na or 11ng gives me device is not configured (This > works fine for the ath card tough)! > > > Melhores Cumprimentos // Best Regards > ----------------------------------------------- > *Miguel Clara* > *IT - Sys Admin & Developer* > *E-mail: *miguelmclara@gmail.com > www.linkedin.com/in/miguelmclara/ > > > On Thu, Aug 14, 2014 at 2:13 PM, Miguel Clara > wrote: > > > > > > > On Wed, Aug 13, 2014 at 7:10 PM, Miguel Clara > > wrote: > > > >> Hi, just wanted to report that the patch made no difference. > >> > >> However I created a guest network in my router with the same password and > >> also using WPA2, and it connects to it. > >> > >> the only difference is the BSSID, so I wonder if this is a issue with wpa > >> and nothing to to with the driver? > >> > > > > NOTE: it works well if using ath driivers so the problem is probably in > > the driver indeed! > > > > > >> But the performance is still horrible! > >> > >> > >> > >> > > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" > From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 15 13:30:45 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2CA8FAE6 for ; Fri, 15 Aug 2014 13:30:45 +0000 (UTC) Received: from astart2.astart.com (108-248-95-193.lightspeed.sndgca.sbcglobal.net [108.248.95.193]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D7B832D70 for ; Fri, 15 Aug 2014 13:30:44 +0000 (UTC) Received: from laptop_93.private (localhost [127.0.0.1]) by astart2.astart.com (8.14.4/8.14.4) with ESMTP id s7FDUhQe097946 for ; Fri, 15 Aug 2014 06:30:43 -0700 (PDT) (envelope-from papowell@astart.com) Message-ID: <53EE0B83.8020404@astart.com> Date: Fri, 15 Aug 2014 06:30:43 -0700 From: Patrick Powell Reply-To: papowell@astart.com Organization: Astart Technologies User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org Subject: Re: FreeBSD current RT3071 can't connect to 5G network References: <53DE4FD2.8050309@FreeBSD.org> <20140805092636.GA41308@ns.kevlo.org> <20140815030631.GA36062@ns.kevlo.org> In-Reply-To: <20140815030631.GA36062@ns.kevlo.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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: Fri, 15 Aug 2014 13:30:45 -0000 Is it possible to provide a SHORT list of a COUPLE that do, and are either supported out of the box or with a few simple mods to the driver (patch?). And perhaps a link to a site where they might be purchased? On 08/14/14 20:06, Kevin Lo wrote: > All USB wifi dongles in FreeBSD don't support 11n yet. > > Kevin > > On Thu, Aug 14, 2014 at 03:09:23PM +0100, Miguel Clara wrote: >> Duh, I figured it out... by default the Asus Guest netwroks are created in >> "auto" mode, so both N and legacy, while my 5G network was set to N only >> (2.4 is set to auto too). >> >> This also explain the poor performance now... for some reason 11n is not >> working only 11g/a. >> >> ifconfig wlan0 mode 11na or 11ng gives me device is not configured (This >> works fine for the ath card tough)! >> >> >> Melhores Cumprimentos // Best Regards >> ----------------------------------------------- >> *Miguel Clara* >> *IT - Sys Admin & Developer* >> *E-mail: *miguelmclara@gmail.com >> www.linkedin.com/in/miguelmclara/ >> >> >> On Thu, Aug 14, 2014 at 2:13 PM, Miguel Clara >> wrote: >> >>> >>> On Wed, Aug 13, 2014 at 7:10 PM, Miguel Clara >>> wrote: >>> >>>> Hi, just wanted to report that the patch made no difference. >>>> >>>> However I created a guest network in my router with the same password and >>>> also using WPA2, and it connects to it. >>>> >>>> the only difference is the BSSID, so I wonder if this is a issue with wpa >>>> and nothing to to with the driver? >>>> >>> NOTE: it works well if using ath driivers so the problem is probably in >>> the driver indeed! >>> >>> >>>> But the performance is still horrible! >>>> >>>> >>>> >>>> >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" > From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 15 23:57:34 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 C8B6BC0A; Fri, 15 Aug 2014 23:57:34 +0000 (UTC) Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2210B2D7E; Fri, 15 Aug 2014 23:57:33 +0000 (UTC) Received: by mail-la0-f43.google.com with SMTP id gi9so287239lab.30 for ; Fri, 15 Aug 2014 16:57:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:message-id:date:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=mvDBRCYk05s6Yi/71fCx6Z2NSiEqqv6PCySuiG2NeiY=; b=HYbr1fifZGVdMmoDTV1z1fi6QzioJ9z42jMH2a8KjH8Hsvn2p8ivCpWsM+l2n62a4t LkmMC8t4jOFoWt+Qwgu4FKBnUF4pNzdB/VRb5/UsYTUFJtGtSrAwoC1kB6CQiEQRQRXz +NFwqYXVjlK6bVsI4veWHDV/cw01rwPC/iT6CHfet/B/x/E5U+/46vzduhNutfYqQG7N V10065x8twq5ViMb71HaSoH03AJl7B/jhmK6iNJ+yURUnz+qQ/zqViSdZWAYdCukQt3Z RGVG9LHISUrsxBy2Wc52Q16LKvBJbmfr/iwKRrV71AOQOs1bPLlOUjHjrMusPxPkQiqB 3ClA== X-Received: by 10.112.167.170 with SMTP id zp10mr13917260lbb.2.1408147051953; Fri, 15 Aug 2014 16:57:31 -0700 (PDT) Received: from limbo.b1t.lan (167.203-pool.nikopol.net. [213.111.203.167]) by mx.google.com with ESMTPSA id k1sm5815132lah.26.2014.08.15.16.57.30 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 15 Aug 2014 16:57:30 -0700 (PDT) From: Volodymyr Kostyrko X-Google-Original-From: Volodymyr Kostyrko Message-ID: <53EE9E68.50606@b1t.name> Date: Sat, 16 Aug 2014 02:57:28 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Kevin Lo , Volodymyr Kostyrko Subject: Re: old new device: another sample of DWA-125 References: <53EB674D.30403@b1t.name> <20140815014118.GA35503@ns.kevlo.org> In-Reply-To: <20140815014118.GA35503@ns.kevlo.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@FreeBSD.org 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: Fri, 15 Aug 2014 23:57:35 -0000 On 15.08.2014 04:41, Kevin Lo wrote: > The D-Link DWA-125 rev D1 uses the RTL8188EU chip. > Please try this patch, thanks. Hm, looks better: # ifconfig wlan0 list scan SSID/MESH ID BSSID CHAN RATE S:N INT CAPS NS 54:04:a6:5b:03:80 1 54M -140:-95 100 EP RSN HTCAP WPS WME ms18883 a0:f3:c1:b5:ec:08 1 54M -140:-95 100 EPS RSN HTCAP WME ATH WPS TP-LINK_7EAADE a0:f3:c1:7e:aa:de 6 54M -140:-95 100 EPS RSN HTCAP WPA WME ATH WPS TP-LINK_58DE70 10:fe:ed:58:de:70 6 54M -140:-95 100 ES HTCAP WME ATH WPS kyivstar21 10:fe:ed:59:71:1a 11 54M -140:-95 100 EPS RSN HTCAP WME ATH WPS Kyivstar-ho... f8:1a:67:76:54:10 11 54M -140:-95 100 EPS RSN HTCAP WPA WME ATH WPS TP-LINK_C9C02C c0:4a:00:c9:c0:2c 1 54M -140:-95 100 EPS RSN HTCAP WPA WME ATH WPS But it still can't join the network, two minutes passed: wlan0: flags=8c43 metric 0 mtu 1500 ether c4:a8:1d:f3:b7:4a inet6 fe80::c6a8:1dff:fef3:b74a%wlan0 prefixlen 64 scopeid 0x7 nd6 options=21 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid TP-LINK_58DE70 channel 8 (2447 MHz 11g) regdomain NONE country UA authmode OPEN privacy OFF txpower 30 bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS bintval 0 Same configuration, ath_pci: wlan0: flags=8843 metric 0 mtu 1500 ether c0:4a:00:eb:4c:17 inet6 fe80::c24a:ff:feeb:4c17%wlan0 prefixlen 64 scopeid 0x6 inet 192.168.1.105 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=21 media: IEEE 802.11 Wireless Ethernet MCS mode 11ng status: associated ssid TP-LINK_58DE70 channel 6 (2437 MHz 11g ht/40-) bssid 10:fe:ed:58:de:70 regdomain NONE country UA indoor ecm authmode OPEN privacy OFF txpower 30 bmiss 7 scanvalid 60 protmode CTS ampdulimit 64k shortgi wme burst -- Sphinx of black quartz judge my vow. From owner-freebsd-wireless@FreeBSD.ORG Sat Aug 16 15:25:14 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 73BBF2AE for ; Sat, 16 Aug 2014 15:25:14 +0000 (UTC) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 327E5275F for ; Sat, 16 Aug 2014 15:25:13 +0000 (UTC) Received: from [93.104.19.168] (helo=localhost.my.domain) by ms-10.1blu.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1XIfqx-0002I6-9c for freebsd-wireless@freebsd.org; Sat, 16 Aug 2014 17:25:11 +0200 Received: from localhost.my.domain (localhost [127.0.0.1]) by localhost.my.domain (8.14.7/8.14.3) with ESMTP id s7GFPAI0001551 for ; Sat, 16 Aug 2014 17:25:10 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.14.7/8.14.3/Submit) id s7GFP90r001550 for freebsd-wireless@freebsd.org; Sat, 16 Aug 2014 17:25:09 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Sat, 16 Aug 2014 17:25:09 +0200 From: Matthias Apitz To: freebsd-wireless@freebsd.org Subject: Broadcom BCM4312 802.11b/g in 11-CURRENT Message-ID: <20140816152509.GA1529@La-Habana> Reply-To: Matthias Apitz MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline X-Operating-System: FreeBSD 9.0-CURRENT r214444 (i386) User-Agent: Mutt/1.5.21 (2010-09-15) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 93.104.19.168 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, 16 Aug 2014 15:25:14 -0000 Hello, I have a 11-CURRENT from August 8, and ports from the day after: FreeBSD tiny-r269739 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r269739M: Fri Aug 15 18:07:41 CEST 2014 guru@vm-tiny-r269739:/usr/obj/usr/src/sys/GENERIC i386 The configuration used for the Wifi card is: rc.conf: wlans_bwn0="wlan0" ifconfig_wlan0="WPA DHCP" loader.conf if_bwn_load="YES" bwn_v4_lp_ucode_load="YES" The Wifi comes up fine on boot with WPA and DHCP assigns IP addr and routing: wlan0: flags=8843 metric 0 mtu 1500 ether 90:4c:e5:00:06:ce inet 192.168.2.100 netmask 0xffffff00 broadcast 192.168.2.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g status: associated ssid tarara channel 7 (2442 MHz 11g) bssid 00:13:f7:0d:08:48 country US authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 4:128-bit txpower 30 bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme roaming MANUAL I even can do a DNS lookup and transfer some ~10 PING to Internet, but after this it gets stuck. Below is a 'dmesg | fgrep -i bwn'. Let me know if someone needs a complete dmesg output. What else can I do to help debugging? Is this card supported at all in 11-CURRENT? Thanks matthias Preloaded elf module "/boot/kernel/if_bwn.ko" at 0xc18478e8. Preloaded elf module "/boot/kernel/siba_bwn.ko" at 0xc1847cbc. Preloaded elf module "/boot/modules/bwn_v4_lp_ucode.ko" at 0xc184806c. firmware: 'bwn_v4_lp_ucode' version 0: 0 bytes loaded at 0xc181b084 firmware: 'bwn_v4_lp_ucode5' version 0: 22264 bytes loaded at 0xc181b084 firmware: 'bwn_v4_lp_ucode11' version 0: 32776 bytes loaded at 0xc182077c firmware: 'bwn_v4_lp_ucode13' version 0: 31440 bytes loaded at 0xc1828784 firmware: 'bwn_v4_lp_ucode14' version 0: 31000 bytes loaded at 0xc1830254 firmware: 'bwn_v4_lp_ucode15' version 0: 34672 bytes loaded at 0xc1837b6c firmware: 'bwn_v4_lp_pcm5' version 0: 1320 bytes loaded at 0xc18402dc firmware: 'bwn_v4_lp_a0g1initvals5' version 0: 1848 bytes loaded at 0xc1840804 firmware: 'bwn_v4_lp_a0g0initvals5' version 0: 1848 bytes loaded at 0xc1840f3c firmware: 'bwn_v4_lp_b0g0initvals5' version 0: 1848 bytes loaded at 0xc1841674 firmware: 'bwn_v4_lp_b0g0initvals13' version 0: 2126 bytes loaded at 0xc1841dac firmware: 'bwn_v4_lp_a0g1bsinitvals5' version 0: 178 bytes loaded at 0xc18425fa firmware: 'bwn_v4_lp_a0g0bsinitvals5' version 0: 178 bytes loaded at 0xc18426ac firmware: 'bwn_v4_lp_b0g0bsinitvals5' version 0: 178 bytes loaded at 0xc184275e firmware: 'bwn_v4_lp_lp0initvals13' version 0: 3664 bytes loaded at 0xc1842810 firmware: 'bwn_v4_lp_lp0initvals14' version 0: 2110 bytes loaded at 0xc1843660 firmware: 'bwn_v4_lp_lp0initvals15' version 0: 2282 bytes loaded at 0xc1843e9e firmware: 'bwn_v4_lp_lp0bsinitvals13' version 0: 178 bytes loaded at 0xc1844788 firmware: 'bwn_v4_lp_lp0bsinitvals14' version 0: 178 bytes loaded at 0xc184483a firmware: 'bwn_v4_lp_lp0bsinitvals15' version 0: 178 bytes loaded at 0xc18448ec firmware: 'bwn_v4_lp_n0bsinitvals11' version 0: 178 bytes loaded at 0xc184499e siba_bwn0: mem 0x57100000-0x57103fff irq 16 at device 0.0 on pci1 bwn0 on siba_bwn0 bwn0: WLAN (chipid 0x4312 rev 15) PHY (analog 6 type 5 rev 1) RADIO (manuf 0x17f ver 0x2062 rev 2) bwn0: DMA (64 bits) bwn0: MSI count : 1 siba_bwn0: attempting to allocate 1 MSI vectors (1 supported) siba_bwn0: using IRQ 257 for MSI bwn0: Using 1 MSI messages bwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps bwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) bwn0: need multicast update callback bwn0: RX decryption attempted (old 0 keyidx 0x3) bwn0: RX decryption attempted (old 0 keyidx 0x3) bwn0: RX decryption attempted (old 0 keyidx 0x3) bwn0: RX decryption attempted (old 0 keyidx 0x3) bwn0: RX decryption attempted (old 0 keyidx 0x3) bwn0: RX decryption attempted (old 0 keyidx 0x3) bwn0: need multicast update callback bwn0: need multicast update callback bwn0: RX decryption attempted (old 0 keyidx 0x3) bwn0: RX decryption attempted (old 0 keyidx 0x3) bwn0: RX decryption attempted (old 0 keyidx 0x3) bwn0: RX decryption attempted (old 0 keyidx 0x3) bwn0: RX decryption attempted (old 0 keyidx 0x3) bwn0: RX decryption attempted (old 0 keyidx 0x3) bwn0: RX decryption attempted (old 0 keyidx 0x3) bwn0: RX decryption attempted (old 0 keyidx 0x3) bwn0: RX decryption attempted (old 0 keyidx 0x3) bwn0: RX decryption attempted (old 0 keyidx 0x3) bwn0: RX decryption attempted (old 0 keyidx 0x3) bwn0: RX decryption attempted (old 0 keyidx 0x3) bwn0: RX decryption attempted (old 0 keyidx 0x3) bwn0: RX decryption attempted (old 0 keyidx 0x3) bwn0: RX decryption attempted (old 0 keyidx 0x3) bwn0: RX decryption attempted (old 0 keyidx 0x3) bwn0: RX decryption attempted (old 0 keyidx 0x3) bwn0: RX decryption attempted (old 0 keyidx 0x3) bwn0: RX decryption attempted (old 0 keyidx 0x3) bwn0: RX decryption attempted (old 0 keyidx 0x3) -- Matthias Apitz | /"\ ASCII Ribbon Campaign: E-mail: guru@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X - No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign From owner-freebsd-wireless@FreeBSD.ORG Sat Aug 16 20:07:52 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 45AB9EA9; Sat, 16 Aug 2014 20:07:52 +0000 (UTC) Received: from mail-we0-x22d.google.com (mail-we0-x22d.google.com [IPv6:2a00:1450:400c:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9825324C7; Sat, 16 Aug 2014 20:07:51 +0000 (UTC) Received: by mail-we0-f173.google.com with SMTP id q58so3536977wes.32 for ; Sat, 16 Aug 2014 13:07:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=UOpWlMNjjBtQYWVE0lXnNos/Yt0bM6hfydPlM8KvHNs=; b=CmRwV3Rh/nUtbKAPkC8yOadNTJh1uEmi/7o7dD9ngr3+gq7hoPAf+NrwjqxlyVJdAR nsSq+JqaDhOd5rbGLzVnV6JvxbgSFz/y6qUbvyWTY3AfPoOH4AesF6dhQklZsNwmE4Lo 4terKRGjvU6pwct5f+m2UQq6InLojeKGz34zr9+PJDB/G5+m0qmfwYD/IZwWey2Spykf sc8GXsXHqA9oSHWcDReb0P62eFNjnGntlatqWby1E7QbHn//QZMmi8obTaNnjKhe/Roy ao/QhaveFPjt/kdQ3wXgXkHI8UZ0pVPfWFQtWlz8yHDWEQruHNmmkD4qFSzxtUEt0RAZ pflQ== X-Received: by 10.180.185.228 with SMTP id ff4mr30362393wic.76.1408219669873; Sat, 16 Aug 2014 13:07:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.121.37 with HTTP; Sat, 16 Aug 2014 13:07:29 -0700 (PDT) In-Reply-To: <20140815030631.GA36062@ns.kevlo.org> References: <53DE4FD2.8050309@FreeBSD.org> <20140805092636.GA41308@ns.kevlo.org> <20140815030631.GA36062@ns.kevlo.org> From: Miguel Clara Date: Sat, 16 Aug 2014 21:07:29 +0100 Message-ID: Subject: Re: FreeBSD current RT3071 can't connect to 5G network To: Kevin Lo Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-wireless@freebsd.org 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, 16 Aug 2014 20:07:52 -0000 On Fri, Aug 15, 2014 at 4:06 AM, Kevin Lo wrote: > All USB wifi dongles in FreeBSD don't support 11n yet. > > Kevin > > I was not aware of that, is this really true for all USB wifi dongles or do you mean ralink only?