From owner-freebsd-wireless@FreeBSD.ORG Sun Oct 26 01:05:48 2014
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 9CCFF74B
for <freebsd-wireless@freebsd.org>; Sun, 26 Oct 2014 01:05:48 +0000 (UTC)
Received: from sender1.zohomail.com (sender1.zohomail.com [74.201.84.156])
(using TLSv1 with cipher RC4-SHA (128/128 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id 671EC1E8
for <freebsd-wireless@freebsd.org>; Sun, 26 Oct 2014 01:05:48 +0000 (UTC)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com;
h=subject:from:to:in-reply-to:references:content-type:date:message-id:mime-version;
b=Q9hrnH6PVb7Rrqa09IWcBYZZCUjn3Q0PiTfhSupeGWFiTE7BHfuqeRNWYe7MA942iAkWqgUI4RXH
sprymvLm9ug9s92b1jZ6n6satexf5DVXRvMotQSwpuB7w6+Bbcbb
Received: from [192.168.11.5] (46.229.54.117 [46.229.54.117]) by
mx.zohomail.com with SMTPS id 1414285540227411.6076544807504;
Sat, 25 Oct 2014 18:05:40 -0700 (PDT)
Subject: Re: pcap_inject() ruins my handmade packets
From: clutton <clutton@zoho.com>
To: freebsd-wireless@freebsd.org
In-Reply-To: <CAJ-Vmo=b7xgFHseZJbUpLYY++Fh2jt6D74dPw6BYtaKBHA=+UQ@mail.gmail.com>
References: <1414110110.1395.14.camel@eva02.mbsd>
<CAJ-Vmo=b7xgFHseZJbUpLYY++Fh2jt6D74dPw6BYtaKBHA=+UQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Sun, 26 Oct 2014 03:05:36 +0200
Message-ID: <1414285536.12280.6.camel@eva02.mbsd>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port
Content-Transfer-Encoding: 7bit
X-ZohoMail: Ss SS_10 UW UB ZCF-710TPL UW UB SF_TD_EXT SGR3_1_23094_577
X-ZohoMail-Owner: <1414285536.12280.6.camel@eva02.mbsd>+zmo_0_<clutton@zoho.com>
X-ZohoMail-Sender: 46.229.54.117
X-Zoho-Virus-Status: 2
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." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Oct 2014 01:05:48 -0000
On Thu, 2014-10-23 at 17:32 -0700, Adrian Chadd wrote:
> Which version of FreeBSD are you using?
>
> I only recently fixed raw frame injection in monitor mode in
> FreeBSD-11. How are you trying to do raw frame injection?
>
>
> -adrian
>
Any ideas? Why this doesn't work for me using pcap and works using
sockets?
https://www.kernel.org/doc/Documentation/networking/mac80211-injection.txt
As I understand monitor mode can be used for injections now, is it
right?
As I remember some discussion here (a long time ago) said that the
monitor mode is for monitoring :) and people should use other modes for
injections. But since new pcap API was introduced, we can see that the
monitor mode is not only for monitoring.
> On 23 October 2014 17:21, clutton <clutton@zoho.com> wrote:
> > Hi list.
> >
> > I'm porting a Linux application [reaver], and have a tough time figuring
> > out what is wrong.
> >
> > The way how Linux users use it doesn't work I mean building packet like
> > radiotap_header+frame+payload and use pcap_inject() for injections.
> >
> > Nevertheless, using the same packets with sockets work like a charm.
> > Since I didn't find any working example with packet injections
> > conjugates with pcap_inject for FreeBSD, I starting think it doesn't
> > work on FreeBSD platform.
> >
> > Right now, I started using LD_PRELOAD with my own version of libpcap,
> > because after end of day it uses write(), but why it is ruins my packets
> > is not obvious for me yet.
> >
> > May be somebody could explain me? May be it's well known not fixable
> > bug, and I'm just wasting my time.
> >
> > I really want to do this using libpcap! Using sockets is quicker
> > approach for me, but you know, fixing libpcap will bring a lot of others
> > apps to FreeBSD realm.
> >
> >
> > _______________________________________________
> > 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 Sun Oct 26 02:54:21 2014
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id A5C242F0
for <freebsd-wireless@freebsd.org>; Sun, 26 Oct 2014 02:54:21 +0000 (UTC)
Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com
[IPv6:2a00:1450:400c:c00::230])
(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 3FBE6CB4
for <freebsd-wireless@freebsd.org>; Sun, 26 Oct 2014 02:54:21 +0000 (UTC)
Received: by mail-wg0-f48.google.com with SMTP id m15so1522913wgh.7
for <freebsd-wireless@freebsd.org>; Sat, 25 Oct 2014 19:54:18 -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=kIJird82CqbL/nQRqbTxJ1gmy+q8Ov1QhSfiY896kVg=;
b=xTexxJ8M2fUFhMyUdNmmIKMcbUmCHgVPvnCRbblg5ps2+fhmBCPv4kpmiDsXmaYfUz
yKT/5TGJ6GkccCGDiMu/eMJPFZ8SJX1sly15pK47DwaJm6qrfsyzOJoLxdpR8FXy/yxE
XtHXr/LzvhuzdabsVItL25ibqcW5HjbS6SbrWAlByhph3ndXbJkQNJ5ZmrZt6scXdYya
AErPXOeiikMayl5SpPJSPX0dgU8OydYpXj+dYfiz7TfBVRHhLY1oH0RIY/pjz+kx7WrB
rrBfR7GrTGfz7hahE15iOgryFiF1zKEiGAsd77yw2/4WY0XjNtO+n0UERMQ3wcvn2k9W
9SGw==
MIME-Version: 1.0
X-Received: by 10.194.216.162 with SMTP id or2mr14243378wjc.68.1414292058375;
Sat, 25 Oct 2014 19:54:18 -0700 (PDT)
Sender: adrian.chadd@gmail.com
Received: by 10.216.106.136 with HTTP; Sat, 25 Oct 2014 19:54:18 -0700 (PDT)
In-Reply-To: <1414285536.12280.6.camel@eva02.mbsd>
References: <1414110110.1395.14.camel@eva02.mbsd>
<CAJ-Vmo=b7xgFHseZJbUpLYY++Fh2jt6D74dPw6BYtaKBHA=+UQ@mail.gmail.com>
<1414285536.12280.6.camel@eva02.mbsd>
Date: Sat, 25 Oct 2014 19:54:18 -0700
X-Google-Sender-Auth: U40mK8tAo8XenhO0_7liFq1p2DM
Message-ID: <CAJ-Vmonv9t5UcVgNnyvKz5wqaxgOojLO_pYhaAkXaAGxRAvTuA@mail.gmail.com>
Subject: Re: pcap_inject() ruins my handmade packets
From: Adrian Chadd <adrian@freebsd.org>
To: clutton <clutton@zoho.com>
Content-Type: text/plain; charset=UTF-8
Cc: "freebsd-wireless@freebsd.org" <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." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Oct 2014 02:54:21 -0000
On 25 October 2014 18:05, clutton <clutton@zoho.com> wrote:
> On Thu, 2014-10-23 at 17:32 -0700, Adrian Chadd wrote:
>> Which version of FreeBSD are you using?
>>
>> I only recently fixed raw frame injection in monitor mode in
>> FreeBSD-11. How are you trying to do raw frame injection?
>>
>>
>> -adrian
>>
>
> Any ideas? Why this doesn't work for me using pcap and works using
> sockets?
> https://www.kernel.org/doc/Documentation/networking/mac80211-injection.txt
>
> As I understand monitor mode can be used for injections now, is it
> right?
>
> As I remember some discussion here (a long time ago) said that the
> monitor mode is for monitoring :) and people should use other modes for
> injections. But since new pcap API was introduced, we can see that the
> monitor mode is not only for monitoring.
It should be working. I haven't coded anything up recently to use
monitor mode and inject, but I do know it now works.
-adrian
From owner-freebsd-wireless@FreeBSD.ORG Sun Oct 26 07:36:14 2014
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 9B15774A;
Sun, 26 Oct 2014 07:36: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 546BA7D7;
Sun, 26 Oct 2014 07:36:13 +0000 (UTC)
Received: from [93.104.7.207] (helo=unixarea.DDR.dd)
by ms-10.1blu.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
(Exim 4.76) (envelope-from <guru@unixarea.de>)
id 1XiIN0-0006sr-9B; Sun, 26 Oct 2014 08:36:10 +0100
Received: from unixarea.DDR.dd (localhost [127.0.0.1])
by unixarea.DDR.dd (8.14.9/8.14.3) with ESMTP id s9Q7a7DF001882;
Sun, 26 Oct 2014 08:36:08 +0100 (CET)
(envelope-from guru@unixarea.de)
Received: (from guru@localhost)
by unixarea.DDR.dd (8.14.9/8.14.3/Submit) id s9Q7a6iX001881;
Sun, 26 Oct 2014 08:36:06 +0100 (CET)
(envelope-from guru@unixarea.de)
X-Authentication-Warning: unixarea.DDR.dd: guru set sender to guru@unixarea.de
using -f
Date: Sun, 26 Oct 2014 08:36:05 +0100
From: Matthias Apitz <guru@unixarea.de>
To: Adrian Chadd <adrian@freebsd.org>, freebsd-wireless@freebsd.org
Subject: Re: Issues with urtwn
Message-ID: <20141026073605.GA1819@unixarea.DDR.dd>
Reply-To: Matthias Apitz <guru@unixarea.de>
References: <540C751F.6050202@freebsd.org>
<CAJ-VmokyPcS077wHiP4Mdetms=meqk47v29fKA1edidhorVQpg@mail.gmail.com>
<540C92D6.4030106@freebsd.org>
<CAJ-VmomMwJOSz7hyAfeEgPE=qBfYm7fTOo5km8JJk4g62JxTkg@mail.gmail.com>
<540CC53A.90600@freebsd.org>
<CAJ-Vmokt_kgxW3aPEDcNwg_ZVrCotqF_tOP1YjZCtO=nCZ8z5Q@mail.gmail.com>
<540E2A2D.4090301@freebsd.org>
<CAJ-VmongioOZQS561Qq5S1T0UVnBifxrQf8P0rr8jEWzk=dumQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAJ-VmongioOZQS561Qq5S1T0UVnBifxrQf8P0rr8jEWzk=dumQ@mail.gmail.com>
X-Operating-System: FreeBSD 11.0-CURRENT r269739 (i386)
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Con-Id: 51246
X-Con-U: 0-guru
X-Originating-IP: 93.104.7.207
Cc: Nathan Whitehorn <nwhitehorn@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." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Oct 2014 07:36:14 -0000
El dÃa Monday, September 08, 2014 a las 03:17:08PM -0700, Adrian Chadd escribió:
> Please compile your kernel with IEEE80211_DEBUG, then enable debugging
> - wlandebug +state +power
>
> You can disable powersave with 'ifconfig wlan0 -powersave', but it
> shouldn't be enabled by default.
Hi,
I was to fast when saying in September that I do not have any issue with
this NIC: under havy SCP traffic (let's say some GByte) the connection
locks and I have to run 'netif restart' to wake it up;
it seems that powersave is off:
# ifconfig wlan0 list sta
ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG
00:13:f7:0d:08:48 2 7 54M 35.5 0 1219 64016 EPS AE RSN
the kernel is 11-CURRENT (r269739) and I have IEEE80211_DEBUG enabled:
# fgrep IEEE80211_DEBUG sys/i386/conf/GENERIC
options IEEE80211_DEBUG # enable debug msgs
# wlandebug -i wlan0 +state +power
net.wlan.0.debug: 0x0 => 0xc0000<state,power>
In /var/log/messages I see now lines like this:
# fgrep kernel /var/log/messages
Oct 26 08:22:44 unixarea kernel: wlan0: [00:13:f7:0d:08:48] sta power save mode on
Oct 26 08:22:46 unixarea kernel: wlan0: [00:13:f7:0d:08:48] sta power save mode off
Oct 26 08:27:46 unixarea kernel: wlan0: [00:13:f7:0d:08:48] sta power save mode on
Oct 26 08:27:48 unixarea kernel: wlan0: [00:13:f7:0d:08:48] sta power save mode off
Oct 26 08:32:48 unixarea kernel: wlan0: [00:13:f7:0d:08:48] sta power save mode on
Oct 26 08:32:50 unixarea kernel: wlan0: [00:13:f7:0d:08:48] sta power save mode off
every 5 minutes...
Who is switching this on/off?
thx
matthias
--
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 Sun Oct 26 21:00:28 2014
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 3688B2C9
for <freebsd-wireless@FreeBSD.org>; Sun, 26 Oct 2014 21:00:28 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
[IPv6:2001:1900:2254:206a::16:76])
(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 25FCA7EB
for <freebsd-wireless@FreeBSD.org>; Sun, 26 Oct 2014 21:00:28 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s9QL0SIC085782
for <freebsd-wireless@FreeBSD.org>; Sun, 26 Oct 2014 21:00:28 GMT
(envelope-from bugzilla-noreply@FreeBSD.org)
Message-Id: <201410262100.s9QL0SIC085782@kenobi.freebsd.org>
From: bugzilla-noreply@FreeBSD.org
To: freebsd-wireless@FreeBSD.org
Subject: Problem reports for freebsd-wireless@FreeBSD.org that need special
attention
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
Date: Sun, 26 Oct 2014 21:00:28 +0000
Content-Type: text/plain; charset="UTF-8"
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." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Oct 2014 21:00:28 -0000
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.
Status | Bug Id | Description
----------------+-----------+-------------------------------------------------
Needs MFC | 154598 | [ath] Atheros 5424/2424 can't connect to WPA ne
Needs MFC | 163312 | [panic] [ath] kernel panic: page fault with ath
Needs MFC | 166190 | [ath] TX hangs and frames stuck in TX queue
Needs MFC | 166357 | [ath] 802.11n TX stall when the first frame in
Needs MFC | 166642 | [ieee80211] [patch] in 802.11n mode for FreeBSD
Needs MFC | 169362 | [ath] AR5416: radar pulse PHY errors sometimes
6 problems total for which you should take action.
From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 27 02:02:42 2014
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 2B7E96C3
for <freebsd-wireless@FreeBSD.org>; Mon, 27 Oct 2014 02:02:42 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
[IPv6:2001:1900:2254:206a::16:76])
(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 12B085F1
for <freebsd-wireless@FreeBSD.org>; Mon, 27 Oct 2014 02:02:42 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s9R22fYH030174
for <freebsd-wireless@FreeBSD.org>; Mon, 27 Oct 2014 02:02:41 GMT
(envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-wireless@FreeBSD.org
Subject: [Bug 194620] New: [ath] [net80211] take ampdu length and error rate
into account when select ampdu length
Date: Mon, 27 Oct 2014 02:02:42 +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: <bug-194620-21060@https.bugs.freebsd.org/bugzilla/>
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-1
Precedence: list
List-Id: "Discussions of 802.11 stack,
tools device driver development." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Oct 2014 02:02:42 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194620
Bug ID: 194620
Summary: [ath] [net80211] take ampdu length and error rate into
account when select ampdu length
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
Right now the A-MPDU error logic in ath_rate_sample only looks at the error
rate, not at where the errors are.
eg:
http://www.mwnl.snu.ac.kr/~schoi/publication/Conferences/14-CONEXT-BYEON.pdf
so for longer frames, things like changing channel conditions, clock
drift/phase drift and such will cause the BER for the later subframes to be
greater than the earlier frames.
The atheros NICs do channel estimate at the beginning of each frame.
So, let's add a bit of logic to check the RX AMPDU BER pattern and if we see
the later sub-frames with a higher BER than the earlier subframes, start
shortening the AMPDU.
--
You are receiving this mail because:
You are the assignee for the bug.
From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 27 08:00:21 2014
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id DFF051F2
for <freebsd-wireless@FreeBSD.org>; Mon, 27 Oct 2014 08:00:20 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
[IPv6:2001:1900:2254:206a::16:76])
(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 CD2CEA85
for <freebsd-wireless@FreeBSD.org>; Mon, 27 Oct 2014 08:00:20 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s9R80K1X073263
for <freebsd-wireless@FreeBSD.org>; Mon, 27 Oct 2014 08:00:20 GMT
(envelope-from bugzilla-noreply@freebsd.org)
Message-Id: <201410270800.s9R80K1X073263@kenobi.freebsd.org>
From: bugzilla-noreply@freebsd.org
To: freebsd-wireless@FreeBSD.org
Subject: [FreeBSD 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, 27 Oct 2014 08:00:20 +0000
Content-Type: text/plain
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." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Oct 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.
(6 bugs)
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 Wed Oct 29 08:47:30 2014
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id B0FC6CA0
for <freebsd-wireless@freebsd.org>; Wed, 29 Oct 2014 08:47:30 +0000 (UTC)
Received: from edge10.ethz.ch (edge10.ethz.ch [82.130.75.186])
(using TLSv1 with cipher AES128-SHA (128/128 bits))
(Client CN "edge10", Issuer "edge10" (not verified))
by mx1.freebsd.org (Postfix) with ESMTPS id 4E0516E9
for <freebsd-wireless@freebsd.org>; Wed, 29 Oct 2014 08:47:30 +0000 (UTC)
Received: from CAS12.d.ethz.ch (172.31.38.212) by edge10.ethz.ch
(82.130.75.186) with Microsoft SMTP Server (TLS) id 14.3.195.1; Wed, 29 Oct
2014 09:44:06 +0100
Received: from MBX12.d.ethz.ch ([fe80::fcbd:f3f9:2031:cf24]) by
CAS12.d.ethz.ch ([fe80::7861:4ecb:7c42:cad4%10]) with mapi id 14.03.0195.001;
Wed, 29 Oct 2014 09:44:16 +0100
From: "Graf Monika" <grafmon@student.ethz.ch>
To: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org>
Subject: Time-of-flight positioning - Atheros
Thread-Topic: Time-of-flight positioning - Atheros
Thread-Index: Ac/zVIXE+2jNKf85S8qUgq/JjldDPQ==
Date: Wed, 29 Oct 2014 08:44:16 +0000
Message-ID: <1E0B1592-5212-4D65-8F08-344EC215EA47@student.ethz.ch>
Accept-Language: de-CH, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1DB4B22B4734A542A86E25C7C9E4893A@intern.ethz.ch>
Content-Transfer-Encoding: quoted-printable
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." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Oct 2014 08:47:30 -0000
Hello Everyone
I am currently at a project where I am using Atheros Chipsets AR9590 with t=
he ath9k driver.
I am wondering how the time-of-flight information can be retrieved per pack=
et in most recent Atheros chipsets. Is it required a proprietary HAL versio=
n ?
Thanks for your help!
Monika=
From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 29 09:33:37 2014
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 768F2B38
for <freebsd-wireless@freebsd.org>; Wed, 29 Oct 2014 09:33:37 +0000 (UTC)
Received: from mail-yh0-x229.google.com (mail-yh0-x229.google.com
[IPv6:2607:f8b0:4002:c01::229])
(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 33CF5C20
for <freebsd-wireless@freebsd.org>; Wed, 29 Oct 2014 09:33:37 +0000 (UTC)
Received: by mail-yh0-f41.google.com with SMTP id b6so368136yha.28
for <freebsd-wireless@freebsd.org>; Wed, 29 Oct 2014 02:33:36 -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=rfJup4ehF93mmO7F5Z99A6hDTE3Y+JL2aqaGnzq1wkY=;
b=lblPI2xhSMaxoU9sNtkD5WdB3tf9uDS2HzWSVUpyKF1iwWdGWCJF+sbzluY/UzR1Or
7Yjp/Vp9JasATN0wilwWmf+c/H+WRyf30TIjZ8BWVx9wwQ6YNi4fxMVZkoiq28tE2COn
u+KhGRUOIEwlvAzt0eNPYjqxN2WGgVsOrq7yQ63UcTWS38GNts+w5BbF7aap64mP2Fe6
ENYBP2u27fOyGQ3CQSYkBOSVxCIXVM6gBWalcSs6PADf0S5u4DzZC8M/qhsTPLd/UlVY
V33IO0CWy+FdQicdOcTmGQAvPUtOKBQ8gKRYsUhIMoBCji7DRpDgRKmF+Jy0q2ATNWrO
d38w==
X-Received: by 10.236.62.136 with SMTP id y8mr835997yhc.124.1414575216459;
Wed, 29 Oct 2014 02:33:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.170.153.196 with HTTP; Wed, 29 Oct 2014 02:33:16 -0700 (PDT)
In-Reply-To: <1E0B1592-5212-4D65-8F08-344EC215EA47@student.ethz.ch>
References: <1E0B1592-5212-4D65-8F08-344EC215EA47@student.ethz.ch>
From: Sergey Ryazanov <ryazanov.s.a@gmail.com>
Date: Wed, 29 Oct 2014 13:33:16 +0400
Message-ID: <CAHNKnsTo5Pt4tvxnL4MJKsUsjGc-fYQMXdi3+DzBvvJZNxwYrg@mail.gmail.com>
Subject: Re: Time-of-flight positioning - Atheros
To: Graf Monika <grafmon@student.ethz.ch>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "freebsd-wireless@freebsd.org" <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." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Oct 2014 09:33:37 -0000
Hi Monika,
2014-10-29 11:44 GMT+03:00 Graf Monika <grafmon@student.ethz.ch>:
> Hello Everyone
>
> I am currently at a project where I am using Atheros Chipsets AR9590 with the ath9k driver.
>
It's a bit strange to ask questions about linux driver in
freebsd-wireless mailing list. Just in case, there are two mailing
lists for ath9k: ath9k-devel and linux-wireless.
> I am wondering how the time-of-flight information can be retrieved per packet in most recent Atheros chipsets. Is it required a proprietary HAL version ?
>
If you need a round-trip-time: take a tx timestamp from tx-complete
descriptor of data frame, then take a timestamp from received ACK
frame and then compute the time. To get received ACK frames from NIC
you should enable control frames receiving in Rx filter. If you need
more details about descriptor format or time of timestamp capture,
then may be Adrian could help.
BTW, a month ago or so, Lorenzo Bianconi added a dynamic ACK timeout
estimation to the ath9k, based exactly on round-trip-time computation.
--
BR,
Sergey
From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 29 18:34:21 2014
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 0804A59B
for <freebsd-wireless@freebsd.org>; Wed, 29 Oct 2014 18:34:21 +0000 (UTC)
Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com
[IPv6:2a00:1450:400c:c00::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 96296276
for <freebsd-wireless@freebsd.org>; Wed, 29 Oct 2014 18:34:20 +0000 (UTC)
Received: by mail-wg0-f54.google.com with SMTP id m15so2539290wgh.41
for <freebsd-wireless@freebsd.org>; Wed, 29 Oct 2014 11:34:18 -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=s1JJtrAWo/7AlAh6fsF4KJf++AFONULPbY6ZIk00JZs=;
b=OnIMjmi3gVdvsMAxP5MB4Kk5U3qJgH99cnbPf91NG6hC4rQdpio1uoWl+vtHARiWFA
xP7WacV3tsh4tFOmRfSa+6aOH/7zs9xDwqdyM14y/ueb+Hdjt4SR7MvfWbHxCgiASJ/n
W7VOmb3FHS18yCJ76wjneXPN35VJmvFe/TqS5vq7NQqXwszOqx3ZzxZoSv74yuLLft1k
fLmF99IUk3Yj28679q8kqpgTG7ITQVvrLvyp27k1VnpRA7Z9kEjvHKjnvYdrLzYA69lW
NGaVteg20yElQa9g2jyD60Lo2bbQ9HwEEaPp8HZYfEpfQyvsTqtwi2MteGdVeONmSZvy
7PtQ==
MIME-Version: 1.0
X-Received: by 10.194.6.233 with SMTP id e9mr15182628wja.20.1414607658804;
Wed, 29 Oct 2014 11:34:18 -0700 (PDT)
Sender: adrian.chadd@gmail.com
Received: by 10.216.106.136 with HTTP; Wed, 29 Oct 2014 11:34:18 -0700 (PDT)
In-Reply-To: <CAHNKnsTo5Pt4tvxnL4MJKsUsjGc-fYQMXdi3+DzBvvJZNxwYrg@mail.gmail.com>
References: <1E0B1592-5212-4D65-8F08-344EC215EA47@student.ethz.ch>
<CAHNKnsTo5Pt4tvxnL4MJKsUsjGc-fYQMXdi3+DzBvvJZNxwYrg@mail.gmail.com>
Date: Wed, 29 Oct 2014 11:34:18 -0700
X-Google-Sender-Auth: ybKh6IGX-dCdaJCVLlKLD_SWVmA
Message-ID: <CAJ-Vmok1FKVetcKVRC-BA_j1hQiZ0WfP=hZ2yS4RuN2aQmbRTA@mail.gmail.com>
Subject: Re: Time-of-flight positioning - Atheros
From: Adrian Chadd <adrian@freebsd.org>
To: Sergey Ryazanov <ryazanov.s.a@gmail.com>
Content-Type: text/plain; charset=UTF-8
Cc: Graf Monika <grafmon@student.ethz.ch>,
"freebsd-wireless@freebsd.org" <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." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Oct 2014 18:34:21 -0000
Oh, I asked him to. I don't mind which list he's asking for hardware help on.
On 29 October 2014 02:33, Sergey Ryazanov <ryazanov.s.a@gmail.com> wrote:
> Hi Monika,
>
> 2014-10-29 11:44 GMT+03:00 Graf Monika <grafmon@student.ethz.ch>:
>> Hello Everyone
>>
>> I am currently at a project where I am using Atheros Chipsets AR9590 with the ath9k driver.
>>
> It's a bit strange to ask questions about linux driver in
> freebsd-wireless mailing list. Just in case, there are two mailing
> lists for ath9k: ath9k-devel and linux-wireless.
>
>> I am wondering how the time-of-flight information can be retrieved per packet in most recent Atheros chipsets. Is it required a proprietary HAL version ?
>>
> If you need a round-trip-time: take a tx timestamp from tx-complete
> descriptor of data frame, then take a timestamp from received ACK
> frame and then compute the time. To get received ACK frames from NIC
> you should enable control frames receiving in Rx filter. If you need
> more details about descriptor format or time of timestamp capture,
> then may be Adrian could help.
The RX timestamp is from the MAC, not the PHY. So it's an OK estimate,
but for metre and sub-metre accuracy you still need to get the
original PHY timestamp. IIRC the timestamps are microsecond accurate,
which limits your actual distance calculation.
Now, the AR9380 and later chips do have some stuff to pull out the PHY
timestamp and some information about the leading edge of the received
frame.
> BTW, a month ago or so, Lorenzo Bianconi added a dynamic ACK timeout
> estimation to the ath9k, based exactly on round-trip-time computation.
That was pretty cute.
-adrian
From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 30 06:57:22 2014
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 05BD021F;
Thu, 30 Oct 2014 06:57:22 +0000 (UTC)
Received: from edge20.ethz.ch (edge20.ethz.ch [82.130.99.26])
(using TLSv1 with cipher AES128-SHA (128/128 bits))
(Client CN "edge20", Issuer "edge20" (not verified))
by mx1.freebsd.org (Postfix) with ESMTPS id 93383BFB;
Thu, 30 Oct 2014 06:57:21 +0000 (UTC)
Received: from CAS11.d.ethz.ch (172.31.38.211) by edge20.ethz.ch
(82.130.99.26) with Microsoft SMTP Server (TLS) id 14.3.195.1; Thu, 30 Oct
2014 07:57:10 +0100
Received: from MBX22.d.ethz.ch ([fe80::b5f8:e932:7440:95ef]) by
CAS11.d.ethz.ch ([fe80::ecc9:4e2d:b26b:1614%10]) with mapi id 14.03.0195.001;
Thu, 30 Oct 2014 07:57:13 +0100
From: "Graf Monika" <grafmon@student.ethz.ch>
To: Adrian Chadd <adrian@freebsd.org>, Sergey Ryazanov <ryazanov.s.a@gmail.com>
Subject: AW: Time-of-flight positioning - Atheros
Thread-Topic: Time-of-flight positioning - Atheros
Thread-Index: Ac/zVIXE+2jNKf85S8qUgq/JjldDPf///OwAgACXKgCAAN+V8g==
Date: Thu, 30 Oct 2014 06:57:12 +0000
Message-ID: <2CCC302EA38F004C899D788D1F3438D51FA025CA@MBX22.d.ethz.ch>
References: <1E0B1592-5212-4D65-8F08-344EC215EA47@student.ethz.ch>
<CAHNKnsTo5Pt4tvxnL4MJKsUsjGc-fYQMXdi3+DzBvvJZNxwYrg@mail.gmail.com>,
<CAJ-Vmok1FKVetcKVRC-BA_j1hQiZ0WfP=hZ2yS4RuN2aQmbRTA@mail.gmail.com>
In-Reply-To: <CAJ-Vmok1FKVetcKVRC-BA_j1hQiZ0WfP=hZ2yS4RuN2aQmbRTA@mail.gmail.com>
Accept-Language: de-CH, en-US
Content-Language: de-CH
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [62.202.7.132]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "freebsd-wireless@freebsd.org" <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." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Oct 2014 06:57:22 -0000
thanks for your answers!:)=0A=
=0A=
Adrian, could you specify a little bit more, how that I get out the PHY tim=
estamp?=0A=
=0A=
Thank you!=0A=
=0A=
Monika=0A=
________________________________________=0A=
Von: adrian.chadd@gmail.com [adrian.chadd@gmail.com]" im Auftrag von &=
quot;Adrian Chadd [adrian@freebsd.org]=0A=
Gesendet: Mittwoch, 29. Oktober 2014 19:34=0A=
An: Sergey Ryazanov=0A=
Cc: Graf Monika; freebsd-wireless@freebsd.org=0A=
Betreff: Re: Time-of-flight positioning - Atheros=0A=
=0A=
Oh, I asked him to. I don't mind which list he's asking for hardware help o=
n.=0A=
=0A=
=0A=
On 29 October 2014 02:33, Sergey Ryazanov <ryazanov.s.a@gmail.com> wrote:=
=0A=
> Hi Monika,=0A=
>=0A=
> 2014-10-29 11:44 GMT+03:00 Graf Monika <grafmon@student.ethz.ch>:=0A=
>> Hello Everyone=0A=
>>=0A=
>> I am currently at a project where I am using Atheros Chipsets AR9590 wit=
h the ath9k driver.=0A=
>>=0A=
> It's a bit strange to ask questions about linux driver in=0A=
> freebsd-wireless mailing list. Just in case, there are two mailing=0A=
> lists for ath9k: ath9k-devel and linux-wireless.=0A=
>=0A=
>> I am wondering how the time-of-flight information can be retrieved per p=
acket in most recent Atheros chipsets. Is it required a proprietary HAL ver=
sion ?=0A=
>>=0A=
> If you need a round-trip-time: take a tx timestamp from tx-complete=0A=
> descriptor of data frame, then take a timestamp from received ACK=0A=
> frame and then compute the time. To get received ACK frames from NIC=0A=
> you should enable control frames receiving in Rx filter. If you need=0A=
> more details about descriptor format or time of timestamp capture,=0A=
> then may be Adrian could help.=0A=
=0A=
The RX timestamp is from the MAC, not the PHY. So it's an OK estimate,=0A=
but for metre and sub-metre accuracy you still need to get the=0A=
original PHY timestamp. IIRC the timestamps are microsecond accurate,=0A=
which limits your actual distance calculation.=0A=
=0A=
Now, the AR9380 and later chips do have some stuff to pull out the PHY=0A=
timestamp and some information about the leading edge of the received=0A=
frame.=0A=
=0A=
> BTW, a month ago or so, Lorenzo Bianconi added a dynamic ACK timeout=0A=
> estimation to the ath9k, based exactly on round-trip-time computation.=0A=
=0A=
That was pretty cute.=0A=
=0A=
=0A=
-adrian=0A=
From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 30 16:12:09 2014
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id F2D71CCB
for <freebsd-wireless@freebsd.org>; Thu, 30 Oct 2014 16:12:09 +0000 (UTC)
Received: from sender1.zohomail.com (sender1.zohomail.com [74.201.84.156])
(using TLSv1 with cipher RC4-SHA (128/128 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id BCB55E60
for <freebsd-wireless@freebsd.org>; Thu, 30 Oct 2014 16:12:09 +0000 (UTC)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com;
h=subject:from:to:in-reply-to:references:content-type:date:message-id:mime-version;
b=DroIAirXO3y6LfWdQq+zr9Qls2JRaBjMh4gY9K3qYaI2qpxtX0HRuF26YdcbbY+8s8bPsstqWwRj
4wVWw/oLvQ7ji/vLNMR43xLteWRQtxQpmr9t0YC2Eea96JLsxwVR
Received: from [192.168.11.5] (46.229.54.117 [46.229.54.117]) by
mx.zohomail.com with SMTPS id 1414685521042182.12625585254295;
Thu, 30 Oct 2014 09:12:01 -0700 (PDT)
Subject: Re: pcap_inject() ruins my handmade packets
From: clutton <clutton@zoho.com>
To: freebsd-wireless@freebsd.org
In-Reply-To: <CAJ-Vmonv9t5UcVgNnyvKz5wqaxgOojLO_pYhaAkXaAGxRAvTuA@mail.gmail.com>
References: <1414110110.1395.14.camel@eva02.mbsd>
<CAJ-Vmo=b7xgFHseZJbUpLYY++Fh2jt6D74dPw6BYtaKBHA=+UQ@mail.gmail.com>
<1414285536.12280.6.camel@eva02.mbsd>
<CAJ-Vmonv9t5UcVgNnyvKz5wqaxgOojLO_pYhaAkXaAGxRAvTuA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Thu, 30 Oct 2014 18:11:57 +0200
Message-ID: <1414685517.8086.15.camel@eva02.mbsd>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port
Content-Transfer-Encoding: quoted-printable
X-ZohoMail: Ss SS_10 UW UB ZCF-710TPL UW UB SF_TD_EXT SGR3_1_23094_285
X-ZohoMail-Owner: <1414685517.8086.15.camel@eva02.mbsd>+zmo_0_<clutton@zoho.com>
X-ZohoMail-Sender: 46.229.54.117
X-Zoho-Virus-Status: 2
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." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Oct 2014 16:12:10 -0000
On Sat, 2014-10-25 at 19:54 -0700, Adrian Chadd wrote:
> On 25 October 2014 18:05, clutton <clutton@zoho.com> wrote:
> > On Thu, 2014-10-23 at 17:32 -0700, Adrian Chadd wrote:
> >> Which version of FreeBSD are you using?
> >>
> >> I only recently fixed raw frame injection in monitor mode in
> >> FreeBSD-11. How are you trying to do raw frame injection?
> >>
> >>
> >> -adrian
> >>
> >
> > Any ideas? Why this doesn't work for me using pcap and works using
> > sockets?
> > https://www.kernel.org/doc/Documentation/networking/mac80211-injection.=
txt
> >
> > As I understand monitor mode can be used for injections now, is it
> > right?
> >
> > As I remember some discussion here (a long time ago) said that the
> > monitor mode is for monitoring :) and people should use other modes for
> > injections. But since new pcap API was introduced, we can see that the
> > monitor mode is not only for monitoring.
>=20
> It should be working. I haven't coded anything up recently to use
> monitor mode and inject, but I do know it now works.
>=20
>=20
>=20
> -adrian
I finally made the =C2=ABreaver=C2=BB work, I even got banned by my AP. The
problem is the pcap library, not the source of the program.
Before sending any patches I think I need familiarize myself with
libpcap more. Because it's pretty scary to patch program which has
comments like this:
* Back in 2002, Donald Lee at Cray wanted a DLT_ for
* IP-over-FC:
[skip]
* 11 years later, Christian Svensson wanted to map
* various ARPHRD_ values to DLT_FC_2 and
* DLT_FC_2_WITH_FRAME_DELIMS for raw Fibre Channel
* frames:
One more question: no radiotap headers currently can be injected. Right?
The underlie levels just ignore DLT_IEEE802_11_RADIO dlt.
From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 30 16:13:12 2014
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id D498ACF1
for <freebsd-wireless@freebsd.org>; Thu, 30 Oct 2014 16:13:12 +0000 (UTC)
Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com
[IPv6:2a00:1450:400c: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 6BB40E68
for <freebsd-wireless@freebsd.org>; Thu, 30 Oct 2014 16:13:12 +0000 (UTC)
Received: by mail-wg0-f47.google.com with SMTP id a1so5999330wgh.6
for <freebsd-wireless@freebsd.org>; Thu, 30 Oct 2014 09:13:10 -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:content-transfer-encoding;
bh=4dFO1cU35Cpcyl3962tWU2Xj0g9V4oCeI4oRNHemxHI=;
b=lOZXb69fzEhK1WjZBI+jFsWpGQ5TNi3A07Z2YFNBL0toJnlSQDfCE4AO/XeCfx4Et/
xMJhLy02XY6jVQi1BsITGajFGzGY3b3i9Cqn08fxpXz+C3Ee2XaORtSWHnOUnoZgi9j8
I3h8RmR8PJL+xJwW2tloSwdxX0RpdXFkUKviE9xv05FE8dMFwgimCXRq4uTTShhrwMq2
6FyZMfoD+e7xwzRkFQn1QASx8si3eiksmTcx5VVhWGbEFHZLvzqutknQXU4PFS9XOT9J
tGB3tL1TdnjbZ/2uxoQF6y+OdI/a00vePf4uuVu4cSIPJNVQ1Jc6/qyuZWSr1wL5yTCp
mqWQ==
MIME-Version: 1.0
X-Received: by 10.194.80.100 with SMTP id q4mr21707651wjx.15.1414685590704;
Thu, 30 Oct 2014 09:13:10 -0700 (PDT)
Sender: adrian.chadd@gmail.com
Received: by 10.216.106.136 with HTTP; Thu, 30 Oct 2014 09:13:10 -0700 (PDT)
In-Reply-To: <1414685517.8086.15.camel@eva02.mbsd>
References: <1414110110.1395.14.camel@eva02.mbsd>
<CAJ-Vmo=b7xgFHseZJbUpLYY++Fh2jt6D74dPw6BYtaKBHA=+UQ@mail.gmail.com>
<1414285536.12280.6.camel@eva02.mbsd>
<CAJ-Vmonv9t5UcVgNnyvKz5wqaxgOojLO_pYhaAkXaAGxRAvTuA@mail.gmail.com>
<1414685517.8086.15.camel@eva02.mbsd>
Date: Thu, 30 Oct 2014 09:13:10 -0700
X-Google-Sender-Auth: XaSFQLBQca7-E6xtO5HRAjacmf4
Message-ID: <CAJ-Vmon+58vPtAkfKQB-KzeYBTuzNvMA-zwmt5kyzAcTw_L9NQ@mail.gmail.com>
Subject: Re: pcap_inject() ruins my handmade packets
From: Adrian Chadd <adrian@freebsd.org>
To: clutton <clutton@zoho.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "freebsd-wireless@freebsd.org" <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." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Oct 2014 16:13:13 -0000
Hah, what was your actual code that worked?
And hm, there are some things in the radiotap header that the raw
transmit path pays attention to.
-adrian
On 30 October 2014 09:11, clutton <clutton@zoho.com> wrote:
> On Sat, 2014-10-25 at 19:54 -0700, Adrian Chadd wrote:
>> On 25 October 2014 18:05, clutton <clutton@zoho.com> wrote:
>> > On Thu, 2014-10-23 at 17:32 -0700, Adrian Chadd wrote:
>> >> Which version of FreeBSD are you using?
>> >>
>> >> I only recently fixed raw frame injection in monitor mode in
>> >> FreeBSD-11. How are you trying to do raw frame injection?
>> >>
>> >>
>> >> -adrian
>> >>
>> >
>> > Any ideas? Why this doesn't work for me using pcap and works using
>> > sockets?
>> > https://www.kernel.org/doc/Documentation/networking/mac80211-injection=
.txt
>> >
>> > As I understand monitor mode can be used for injections now, is it
>> > right?
>> >
>> > As I remember some discussion here (a long time ago) said that the
>> > monitor mode is for monitoring :) and people should use other modes fo=
r
>> > injections. But since new pcap API was introduced, we can see that the
>> > monitor mode is not only for monitoring.
>>
>> It should be working. I haven't coded anything up recently to use
>> monitor mode and inject, but I do know it now works.
>>
>>
>>
>> -adrian
>
> I finally made the =C2=ABreaver=C2=BB work, I even got banned by my AP. T=
he
> problem is the pcap library, not the source of the program.
>
> Before sending any patches I think I need familiarize myself with
> libpcap more. Because it's pretty scary to patch program which has
> comments like this:
>
> * Back in 2002, Donald Lee at Cray wanted a DLT_ for
> * IP-over-FC:
> [skip]
> * 11 years later, Christian Svensson wanted to map
> * various ARPHRD_ values to DLT_FC_2 and
> * DLT_FC_2_WITH_FRAME_DELIMS for raw Fibre Channel
> * frames:
>
> One more question: no radiotap headers currently can be injected. Right?
> The underlie levels just ignore DLT_IEEE802_11_RADIO dlt.
>
>
> _______________________________________________
> freebsd-wireless@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.or=
g"
From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 30 16:21:26 2014
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 657E0F86;
Thu, 30 Oct 2014 16:21:26 +0000 (UTC)
Received: from sender1.zohomail.com (sender1.zohomail.com [74.201.84.156])
(using TLSv1 with cipher RC4-SHA (128/128 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id 44079ECA;
Thu, 30 Oct 2014 16:21:25 +0000 (UTC)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com;
h=subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version;
b=JDtsWrRyS5PcteXXJUYRz7U32Vphh4f7wZF8++VsgO68QQWGEurGc7k9eV41vvov2FEUVgEnn+2u
CApGkU5tKI+td7dG+h6fWlzYLi7q7QytTV3bHMUsizYIBDccbVNU
Received: from [192.168.11.5] (46.229.54.117 [46.229.54.117]) by
mx.zohomail.com with SMTPS id 1414686082083646.950874524199;
Thu, 30 Oct 2014 09:21:22 -0700 (PDT)
Subject: Re: pcap_inject() ruins my handmade packets
From: clutton <clutton@zoho.com>
To: freebsd-wireless@freebsd.org
In-Reply-To: <CAJ-Vmon+58vPtAkfKQB-KzeYBTuzNvMA-zwmt5kyzAcTw_L9NQ@mail.gmail.com>
References: <1414110110.1395.14.camel@eva02.mbsd>
<CAJ-Vmo=b7xgFHseZJbUpLYY++Fh2jt6D74dPw6BYtaKBHA=+UQ@mail.gmail.com>
<1414285536.12280.6.camel@eva02.mbsd>
<CAJ-Vmonv9t5UcVgNnyvKz5wqaxgOojLO_pYhaAkXaAGxRAvTuA@mail.gmail.com>
<1414685517.8086.15.camel@eva02.mbsd>
<CAJ-Vmon+58vPtAkfKQB-KzeYBTuzNvMA-zwmt5kyzAcTw_L9NQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Thu, 30 Oct 2014 18:21:18 +0200
Message-ID: <1414686078.8086.21.camel@eva02.mbsd>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port
Content-Transfer-Encoding: quoted-printable
X-ZohoMail: Ss SS_10 UW UB ZCF-710TPL UW UB SF_TD_EXT SGR3_1_23094_82
X-ZohoMail-Owner: <1414686078.8086.21.camel@eva02.mbsd>+zmo_0_<clutton@zoho.com>
X-ZohoMail-Sender: 46.229.54.117
X-Zoho-Virus-Status: 2
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." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Oct 2014 16:21:26 -0000
On Thu, 2014-10-30 at 09:13 -0700, Adrian Chadd wrote:
> Hah, what was your actual code that worked?
>=20
> And hm, there are some things in the radiotap header that the raw
> transmit path pays attention to.
>=20
>=20
>=20
> -adrian
>=20
>=20
> On 30 October 2014 09:11, clutton <clutton@zoho.com> wrote:
> > On Sat, 2014-10-25 at 19:54 -0700, Adrian Chadd wrote:
> >> On 25 October 2014 18:05, clutton <clutton@zoho.com> wrote:
> >> > On Thu, 2014-10-23 at 17:32 -0700, Adrian Chadd wrote:
> >> >> Which version of FreeBSD are you using?
> >> >>
> >> >> I only recently fixed raw frame injection in monitor mode in
> >> >> FreeBSD-11. How are you trying to do raw frame injection?
> >> >>
> >> >>
> >> >> -adrian
> >> >>
> >> >
> >> > Any ideas? Why this doesn't work for me using pcap and works using
> >> > sockets?
> >> > https://www.kernel.org/doc/Documentation/networking/mac80211-injecti=
on.txt
> >> >
> >> > As I understand monitor mode can be used for injections now, is it
> >> > right?
> >> >
> >> > As I remember some discussion here (a long time ago) said that the
> >> > monitor mode is for monitoring :) and people should use other modes =
for
> >> > injections. But since new pcap API was introduced, we can see that t=
he
> >> > monitor mode is not only for monitoring.
> >>
> >> It should be working. I haven't coded anything up recently to use
> >> monitor mode and inject, but I do know it now works.
> >>
> >>
> >>
> >> -adrian
> >
> > I finally made the =C2=ABreaver=C2=BB work, I even got banned by my AP.=
The
> > problem is the pcap library, not the source of the program.
> >
> > Before sending any patches I think I need familiarize myself with
> > libpcap more. Because it's pretty scary to patch program which has
> > comments like this:
> >
> > * Back in 2002, Donald Lee at Cray wanted a DLT_ for
> > * IP-over-FC:
> > [skip]
> > * 11 years later, Christian Svensson wanted to map
> > * various ARPHRD_ values to DLT_FC_2 and
> > * DLT_FC_2_WITH_FRAME_DELIMS for raw Fibre Channel
> > * frames:
> >
> > One more question: no radiotap headers currently can be injected. Right=
?
> > The underlie levels just ignore DLT_IEEE802_11_RADIO dlt.
The program I work with is [rever] https://code.google.com/p/reaver-wps
I looked at aircrack-ng sources, and tools/net80211 and none of them
includes radiotap headers for injection, when I do I have corrupted
packets.
From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 30 17:22:36 2014
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 579AD280
for <freebsd-wireless@freebsd.org>; Thu, 30 Oct 2014 17:22:36 +0000 (UTC)
Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com
[IPv6:2a00:1450:400c:c00::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 E30CD8F2
for <freebsd-wireless@freebsd.org>; Thu, 30 Oct 2014 17:22:35 +0000 (UTC)
Received: by mail-wg0-f54.google.com with SMTP id m15so4766290wgh.41
for <freebsd-wireless@freebsd.org>; Thu, 30 Oct 2014 10:22:34 -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=tUhCbA++s9UEUa9KuZfuxQWFcnH3/Zr5ZvH8SURv5Bs=;
b=UcnwxQMpEVowX//7EvbOXM+pHq4owysaD2GA0Vnu6WTFwAepQhMWPgFQ4rIsfH6faA
A29NX/8vQqPNPZOvZI/oGUvHEJCJ+EKEwQ70reFtG8guc9pYu+Jw2jLVpf2DSjmyGDzn
Bg/i5UTdRlAN1fG9M+dO3qwyH6xDDW9E0AlHLAnXnevCVgUBQoXVmrysRrS49eZ++lBi
J69QaJW5B9vK2hhRePCHy7MSD+I2q3+/b9b/zlOG92zG0lS2MSDQvHEzRYv0A/ntHOVT
N2bqojNB3axv37+E83tEx4dtgcy4Dpn8IlbXQj9A8+LhxR62WJy+sGyDkUzB1vmb7mVr
Mp7g==
MIME-Version: 1.0
X-Received: by 10.180.87.33 with SMTP id u1mr20344085wiz.20.1414689754115;
Thu, 30 Oct 2014 10:22:34 -0700 (PDT)
Sender: adrian.chadd@gmail.com
Received: by 10.216.106.136 with HTTP; Thu, 30 Oct 2014 10:22:34 -0700 (PDT)
In-Reply-To: <1414686078.8086.21.camel@eva02.mbsd>
References: <1414110110.1395.14.camel@eva02.mbsd>
<CAJ-Vmo=b7xgFHseZJbUpLYY++Fh2jt6D74dPw6BYtaKBHA=+UQ@mail.gmail.com>
<1414285536.12280.6.camel@eva02.mbsd>
<CAJ-Vmonv9t5UcVgNnyvKz5wqaxgOojLO_pYhaAkXaAGxRAvTuA@mail.gmail.com>
<1414685517.8086.15.camel@eva02.mbsd>
<CAJ-Vmon+58vPtAkfKQB-KzeYBTuzNvMA-zwmt5kyzAcTw_L9NQ@mail.gmail.com>
<1414686078.8086.21.camel@eva02.mbsd>
Date: Thu, 30 Oct 2014 10:22:34 -0700
X-Google-Sender-Auth: 1T_tJYbzO_deN0cNgY9GSG2j3aE
Message-ID: <CAJ-VmokG-OdM1d=1boO5mT7Zm=E72EEkWM6TL7gT8zCdbyCgaA@mail.gmail.com>
Subject: Re: pcap_inject() ruins my handmade packets
From: Adrian Chadd <adrian@freebsd.org>
To: clutton <clutton@zoho.com>
Content-Type: text/plain; charset=UTF-8
Cc: "freebsd-wireless@freebsd.org" <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." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Oct 2014 17:22:36 -0000
On 30 October 2014 09:21, clutton <clutton@zoho.com> wrote:
>> > One more question: no radiotap headers currently can be injected. Right?
>> > The underlie levels just ignore DLT_IEEE802_11_RADIO dlt.
>
> The program I work with is [rever] https://code.google.com/p/reaver-wps
>
> I looked at aircrack-ng sources, and tools/net80211 and none of them
> includes radiotap headers for injection, when I do I have corrupted
> packets.
Ok. Maybe /that/ path is broken. The raw xmit path should handle
having radiotap headers.
Can you post some sample code that triggers / doesn't trigger the problem?
-adrian
From owner-freebsd-wireless@FreeBSD.ORG Fri Oct 31 09:40:10 2014
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 1C0EDA2
for <freebsd-wireless@FreeBSD.org>; Fri, 31 Oct 2014 09:40:10 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
[IPv6:2001:1900:2254:206a::16:76])
(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 035AD366
for <freebsd-wireless@FreeBSD.org>; Fri, 31 Oct 2014 09:40:10 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s9V9e99W072113
for <freebsd-wireless@FreeBSD.org>; Fri, 31 Oct 2014 09:40:09 GMT
(envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-wireless@FreeBSD.org
Subject: [Bug 193588] [PATCH] Staged malo(4) firmware module
Date: Fri, 31 Oct 2014 09:40:08 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports Tree
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords:
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: marino@FreeBSD.org
X-Bugzilla-Status: Needs Triage
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-193588-21060-MehzZdIqxc@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-193588-21060@https.bugs.freebsd.org/bugzilla/>
References: <bug-193588-21060@https.bugs.freebsd.org/bugzilla/>
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-1
Precedence: list
List-Id: "Discussions of 802.11 stack,
tools device driver development." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Oct 2014 09:40:10 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193588
John Marino <marino@FreeBSD.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marino@FreeBSD.org
--- Comment #8 from John Marino <marino@FreeBSD.org> ---
I can't follow what's going on with this PR. Should it be closed? If not,
what needs to be done?
--
You are receiving this mail because:
You are on the CC list for the bug.
From owner-freebsd-wireless@FreeBSD.ORG Fri Oct 31 10:13:10 2014
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id F1A3058A
for <freebsd-wireless@FreeBSD.org>; Fri, 31 Oct 2014 10:13:10 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
[IPv6:2001:1900:2254:206a::16:76])
(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 D8D95A46
for <freebsd-wireless@FreeBSD.org>; Fri, 31 Oct 2014 10:13:10 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s9VADAMs005433
for <freebsd-wireless@FreeBSD.org>; Fri, 31 Oct 2014 10:13:10 GMT
(envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-wireless@FreeBSD.org
Subject: [Bug 193588] [PATCH] Staged malo(4) firmware module
Date: Fri, 31 Oct 2014 10:13:10 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports Tree
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords:
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: info@juanmolina.eu
X-Bugzilla-Status: Needs Triage
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-193588-21060-gGMHqxnqrR@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-193588-21060@https.bugs.freebsd.org/bugzilla/>
References: <bug-193588-21060@https.bugs.freebsd.org/bugzilla/>
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." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Oct 2014 10:13:11 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D193588
--- Comment #9 from Juan Ram=C3=B3n Molina Menor <info@juanmolina.eu> ---
malo(4) is the Marvell Libertas IEEE 802.11b/g wireless network driver. It =
is
included in GENERIC kernel. It requires a firmware kernel module that must =
be
installed through a port that it=E2=80=99s not present in the current ports=
tree and
have to be downloaded from:
http://weongyo.org/project/malo/malo-firmware-1.4.tar.gz
As this port has not been updated to conform to the new staging infrastruct=
ure,
these family of NICs cannot work in recent versions of FreeBSD.
I guess the solution should be to contact weongyo@FreeBSD.org for replacing=
the
above mentioned file with the patched (staged) one provided by Carlos. Or m=
ove
the port to the official ports tree and change the malo(4) man page. This is
maybe not possible, as hinted in the pkg-descr file:
Marvell Libertas 88W8335 firmware files are not free because Marvell
refuses to grant distribution rights. As a result, we need to build the
firmware using ports.
This firmware files are comed from OpenBSD malo driver.
http://www.nazgul.ch/malo/malo-firmware-1.4.tgz
Hope I understood it well and it helps,
Juan
--=20
You are receiving this mail because:
You are on the CC list for the bug.=
From owner-freebsd-wireless@FreeBSD.ORG Fri Oct 31 14:21:33 2014
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id BE0362F7
for <freebsd-wireless@FreeBSD.org>; Fri, 31 Oct 2014 14:21:33 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
[IPv6:2001:1900:2254:206a::16:76])
(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 A5A118E7
for <freebsd-wireless@FreeBSD.org>; Fri, 31 Oct 2014 14:21:33 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s9VELXIY015527
for <freebsd-wireless@FreeBSD.org>; Fri, 31 Oct 2014 14:21:33 GMT
(envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-wireless@FreeBSD.org
Subject: [Bug 193588] [PATCH] Staged malo(4) firmware module
Date: Fri, 31 Oct 2014 14:21:32 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports Tree
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords:
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: marino@FreeBSD.org
X-Bugzilla-Status: Needs Triage
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-193588-21060-MKslWoXkBZ@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-193588-21060@https.bugs.freebsd.org/bugzilla/>
References: <bug-193588-21060@https.bugs.freebsd.org/bugzilla/>
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-1
Precedence: list
List-Id: "Discussions of 802.11 stack,
tools device driver development." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Oct 2014 14:21:33 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193588
--- Comment #10 from John Marino <marino@FreeBSD.org> ---
yes, it helps.
If I understand this correctly, the original port is in the link mentioned in
in the description, and the attachments are patches to that link.
Needless to that, that is less than optimal (read unacceptable).
A new port needs to be introduced with a shar file:
https://www.freebsd.org/doc/en/books/porters-handbook/porting-submitting.html
Before this port can advance, I'd like to see a completely up-to-date shar file
submitted and all the other patches made obsolete. We also need poudriere
logs with stage-qa checks (testport, bulk -t) as a second attachment, at the
very least.
--
You are receiving this mail because:
You are on the CC list for the bug.
From owner-freebsd-wireless@FreeBSD.ORG Sat Nov 1 14:29:02 2014
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 2107E28C;
Sat, 1 Nov 2014 14:29:02 +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 CF928CB3;
Sat, 1 Nov 2014 14:29:01 +0000 (UTC)
Received: from [93.104.4.174] (helo=unixarea.DDR.dd)
by ms-10.1blu.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
(Exim 4.76) (envelope-from <guru@unixarea.de>)
id 1XkZfg-0007M3-Pz; Sat, 01 Nov 2014 15:28:53 +0100
Received: from unixarea.DDR.dd (localhost [127.0.0.1])
by unixarea.DDR.dd (8.14.9/8.14.3) with ESMTP id sA1ESpF1002237;
Sat, 1 Nov 2014 15:28:51 +0100 (CET) (envelope-from guru@unixarea.de)
Received: (from guru@localhost)
by unixarea.DDR.dd (8.14.9/8.14.3/Submit) id sA18HabB002873;
Sat, 1 Nov 2014 09:17:36 +0100 (CET) (envelope-from guru@unixarea.de)
X-Authentication-Warning: unixarea.DDR.dd: guru set sender to guru@unixarea.de
using -f
Date: Sat, 1 Nov 2014 09:17:36 +0100
From: Matthias Apitz <guru@unixarea.de>
To: Adrian Chadd <adrian@freebsd.org>, freebsd-wireless@freebsd.org,
Nathan Whitehorn <nwhitehorn@freebsd.org>
Subject: Re: Issues with urtwn
Message-ID: <20141101081736.GA2857@unixarea.DDR.dd>
Reply-To: Matthias Apitz <guru@unixarea.de>
References: <540C751F.6050202@freebsd.org>
<CAJ-VmokyPcS077wHiP4Mdetms=meqk47v29fKA1edidhorVQpg@mail.gmail.com>
<540C92D6.4030106@freebsd.org>
<CAJ-VmomMwJOSz7hyAfeEgPE=qBfYm7fTOo5km8JJk4g62JxTkg@mail.gmail.com>
<540CC53A.90600@freebsd.org>
<CAJ-Vmokt_kgxW3aPEDcNwg_ZVrCotqF_tOP1YjZCtO=nCZ8z5Q@mail.gmail.com>
<540E2A2D.4090301@freebsd.org>
<CAJ-VmongioOZQS561Qq5S1T0UVnBifxrQf8P0rr8jEWzk=dumQ@mail.gmail.com>
<20141026073605.GA1819@unixarea.DDR.dd>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20141026073605.GA1819@unixarea.DDR.dd>
X-Operating-System: FreeBSD 11.0-CURRENT r269739 (i386)
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Con-Id: 51246
X-Con-U: 0-guru
X-Originating-IP: 93.104.4.174
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." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>,
<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Nov 2014 14:29:02 -0000
El dÃa Sunday, October 26, 2014 a las 08:36:05AM +0100, Matthias Apitz escribió:
> # ifconfig wlan0 list sta
> ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG
> 00:13:f7:0d:08:48 2 7 54M 35.5 0 1219 64016 EPS AE RSN
>
> the kernel is 11-CURRENT (r269739) and I have IEEE80211_DEBUG enabled:
>
> # fgrep IEEE80211_DEBUG sys/i386/conf/GENERIC
> options IEEE80211_DEBUG # enable debug msgs
>
> # wlandebug -i wlan0 +state +power
> net.wlan.0.debug: 0x0 => 0xc0000<state,power>
>
I have had another look up with these messages in /var/log/messages:
Nov 1 08:44:39 unixarea kernel: wlan0: Ethernet address: 80:1f:02:ee:16:37
Nov 1 08:44:44 unixarea kernel: wlan0: link state changed to UP
Nov 1 08:49:44 unixarea kernel: wlan0: [00:13:f7:0d:08:48] sta power save mode on
Nov 1 08:49:46 unixarea kernel: wlan0: [00:13:f7:0d:08:48] sta power save mode off
Nov 1 08:54:46 unixarea kernel: wlan0: [00:13:f7:0d:08:48] sta power save mode on
Nov 1 08:54:46 unixarea kernel: wlan0: [00:13:f7:0d:08:48] save frame with age 40, 1 now queued
Nov 1 08:54:46 unixarea kernel: wlan0: [00:13:f7:0d:08:48] sta power save mode off
Nov 1 08:54:46 unixarea kernel: wlan0: [00:13:f7:0d:08:48] flush ps queue, 1 packets queued
Nov 1 08:54:47 unixarea kernel: wlan0: [00:13:f7:0d:08:48] sta power save mode on
Nov 1 08:54:48 unixarea kernel: wlan0: [00:13:f7:0d:08:48] sta power save mode off
Nov 1 08:59:48 unixarea kernel: wlan0: [00:13:f7:0d:08:48] sta power save mode on
Nov 1 08:59:48 unixarea kernel: wlan0: [00:13:f7:0d:08:48] save frame with age 40, 1 now queued
Nov 1 08:59:50 unixarea kernel: wlan0: [00:13:f7:0d:08:48] sta power save mode off
Nov 1 08:59:50 unixarea kernel: wlan0: [00:13:f7:0d:08:48] flush ps queue, 1 packets queued
Nov 1 09:03:40 unixarea kernel: wlan0: beacon miss, mode STA state RUN
Nov 1 09:03:41 unixarea kernel: wlan0: beacon miss, mode STA state RUN
Nov 1 09:03:41 unixarea kernel: wlan0: ieee80211_new_state_locked: RUN -> SCAN (nrunning 0 nscanning 0)
Nov 1 09:03:41 unixarea kernel: wlan0: ieee80211_newstate_cb: RUN -> SCAN arg 0
Nov 1 09:03:41 unixarea kernel: wlan0: sta_newstate: RUN -> SCAN (0)
Nov 1 09:03:41 unixarea kernel: wlan0: link state changed to DOWN
Nov 1 09:03:44 unixarea kernel: wlan0: [00:13:f7:0d:08:48] station assoc via MLME
Nov 1 09:03:44 unixarea kernel: wlan0: ieee80211_new_state_locked: SCAN -> AUTH (nrunning 0 nscanning 0)
Nov 1 09:03:44 unixarea kernel: wlan0: ieee80211_newstate_cb: SCAN -> AUTH arg 192
Nov 1 09:03:44 unixarea kernel: wlan0: sta_newstate: SCAN -> AUTH (192)
Nov 1 09:03:46 unixarea kernel: wlan0: ieee80211_new_state_locked: AUTH -> SCAN (nrunning 0 nscanning 0)
Nov 1 09:03:46 unixarea kernel: wlan0: ieee80211_newstate_cb: AUTH -> SCAN arg 1
Nov 1 09:03:46 unixarea kernel: wlan0: sta_newstate: AUTH -> SCAN (1)
Nov 1 09:03:54 unixarea kernel: wlan0: [00:13:f7:0d:08:48] station deauth via MLME (reason 3)
Nov 1 09:03:54 unixarea kernel: wlan0: ieee80211_new_state_locked: SCAN -> INIT (nrunning 0 nscanning 0)
Nov 1 09:03:54 unixarea kernel: wlan0: ieee80211_newstate_cb: SCAN -> INIT arg 3
Nov 1 09:03:54 unixarea kernel: wlan0: sta_newstate: SCAN -> INIT (3)
Nov 1 09:03:55 unixarea kernel: wlan0: ieee80211_new_state_locked: INIT -> SCAN (nrunning 0 nscanning 0)
Nov 1 09:03:55 unixarea kernel: wlan0: ieee80211_newstate_cb: INIT -> SCAN arg 0
Nov 1 09:03:55 unixarea kernel: wlan0: sta_newstate: INIT -> SCAN (0)
--
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