From owner-freebsd-bugs@FreeBSD.ORG  Fri Jun 13 12:20:11 2003
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 17A5137B401
	for <freebsd-bugs@hub.freebsd.org>;
	Fri, 13 Jun 2003 12:20:11 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9365843FAF
	for <freebsd-bugs@hub.freebsd.org>;
	Fri, 13 Jun 2003 12:20:10 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h5DJKAUp095176
	for <freebsd-bugs@freefall.freebsd.org>;
	Fri, 13 Jun 2003 12:20:10 -0700 (PDT)
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h5DJK9ji095175;
	Fri, 13 Jun 2003 12:20:09 -0700 (PDT)
Date: Fri, 13 Jun 2003 12:20:09 -0700 (PDT)
Message-Id: <200306131920.h5DJK9ji095175@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
From: Bruce M Simpson <bms@spc.org>
Subject: Re: kern/53187
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Bruce M Simpson <bms@spc.org>
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jun 2003 19:20:11 -0000

The following reply was made to PR kern/53187; it has been noted by GNATS.

From: Bruce M Simpson <bms@spc.org>
To: freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: kern/53187
Date: Wed, 11 Jun 2003 09:24:29 +0100

 Here are more of my notes from working through the problem:-
 
    - firmly established that old-style monitor-mode/procframe handling is
      gone from the driver. this is what breaks bsd-airtools.
    - tcpdump is able to sniff 802.11 headers though; but it does the
      following: pcap_set_datalink(p, DLT_IEEE802_11).
    - looks like enabling monitor mode does actually go through to hw still.
     - dstumbler is heavily dependent on the old monitor-mode behaviour 
       from 5.0-RELEASE. but it could be patched to do things in a way
       which is compatible with the new api changes.
     - looks like struct wi_rx_frame {} no longer used, but still defined.
     - the wi_frame is broadly equivalent to the wi_rx_frame struct
       abused by bsd-airtools.
     - one would need to define a different link layer, IEEE802_11_PRISM2,
       dummy mbuf with procfame, and bpf_mtap() that.
     - Conditionalise it for people who are worried about this support
       bloating up their packet input path.
     - Moving wi_rx_intr() processing into taskqs is probably a far distant
       future exercise right now anyway.
 
 I could potentially write the code to do the above. I would like review
 from sam@ and imp@ first before deciding how to proceed.
 
 BMS