From nobody@FreeBSD.org  Wed Mar 19 20:37:28 2008
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id F17FF106564A
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 19 Mar 2008 20:37:28 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21])
	by mx1.freebsd.org (Postfix) with ESMTP id DBD938FC1D
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 19 Mar 2008 20:37:28 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.14.2/8.14.2) with ESMTP id m2JKbPAN098497
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 19 Mar 2008 20:37:25 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.14.2/8.14.1/Submit) id m2JKbPZP098496;
	Wed, 19 Mar 2008 20:37:25 GMT
	(envelope-from nobody)
Message-Id: <200803192037.m2JKbPZP098496@www.freebsd.org>
Date: Wed, 19 Mar 2008 20:37:25 GMT
From: bob frazier <bobf@mrp3.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: ath driver in 7.0 no longer honors 'monitor' mode
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         121880
>Category:       kern
>Synopsis:       [ath] ath driver in 7.0 no longer honors 'monitor' mode (regression)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    sam
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Mar 19 20:40:03 UTC 2008
>Closed-Date:    Tue Mar 25 17:14:04 UTC 2008
>Last-Modified:  Tue Mar 25 17:14:04 UTC 2008
>Originator:     bob frazier
>Release:        7.0-STABLE (as of 3/2/2008)
>Organization:
>Environment:
FreeBSD BSDLaptop 7.0-STABLE FreeBSD 7.0-STABLE #0: Sun Mar  2 15:33:08 PST 2008

>Description:
In 6.x the ath driver properly honored 'monitor' mode, shutting down
transmit so that you could safely use tools like 'wireshark' without
attempting to roam, associate with an access point, or transmit probe
requests.

Using wireshark I verified that 'monitor mode' no longer works with the
'ath' driver.  This basically makes passive scans IMPOSSIBLE, including
scanning for access points in the area without actually attempting to
associate.

Again, the 'monitor' functionality worked properly in the previous
release.  It no longer works in 7.0


>How-To-Repeat:
a) issue the following command for hardware supported by the 'ath' driver
   ifconfig ath0 up ssid - monitor channel 1
   (alternately choose another channel on which an access point is known to be)

b) with an access point known to be on the monitored channel, run wireshark
   and capture radiotap headers in addition to normal traffic with
   'promiscuous mode' chosen.

c) observe beacons AND response packets going to/from the atheros adaptor
   that is supposed to be in 'monitor' mode.

>Fix:


>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->sam 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Wed Mar 19 21:00:24 UTC 2008 
Responsible-Changed-Why:  
Sam, can you comment on this one? 

http://www.freebsd.org/cgi/query-pr.cgi?pr=121880 

From: Sam Leffler <sam@errno.com>
To: bug-followup@FreeBSD.org, bobf@mrp3.com
Cc:  
Subject: Re: kern/121880: [ath] ath driver in 7.0 no longer honors 'monitor'
 mode (regression)
Date: Wed, 19 Mar 2008 21:07:13 -0700

 ifconfig monitor is not "monitor mode"; it just causes the 802.3 code to 
 discard frames in the tx/rx paths.  In fact it is a total hack and never 
 intended for wireless nics.  The right way to use wireshark is (and has 
 always been) to do:
 
 ifconfig ath0 mediaopt monitor channel X up
 
 and then run wireshark, tcpdump, whatever.  This is especially required 
 for adapters that must program the device specially for monitor mode 
 operation.

From: Bob Frazier <bobf@mrp3.com>
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: kern/121880: [ath] ath driver in 7.0 no longer honors 'monitor'
 mode (regression)
Date: Sat, 22 Mar 2008 17:18:55 -0800

 thanks - I searched the docs for this information and could not find it. 
 Can you add that information about 'mediaopt monitor' to the ifconfig 
 man page?  If there are other 'mediaopt' options that aren't 
 drive-specific, can they be added to the ifconfig page as well?  the 
 ifconfig man page only says "see driver documentation" and of course the 
 ath man page has no reference to 'mediaopt monitor' either.
 
 [I guess we can call this one 'closed']
 
 
State-Changed-From-To: open->closed 
State-Changed-By: sam 
State-Changed-When: Tue Mar 25 17:13:16 UTC 2008 
State-Changed-Why:  
the misunderstanding is resolved; we need to improve out documentation 
wrt monitor mode and/or mediaopt monitor operation 

http://www.freebsd.org/cgi/query-pr.cgi?pr=121880 
>Unformatted:
