From owner-freebsd-bugs@FreeBSD.ORG Tue Feb 10 06:10:01 2009 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4764106566B for ; Tue, 10 Feb 2009 06:10:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A35458FC25 for ; Tue, 10 Feb 2009 06:10:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n1A6A1YS079049 for ; Tue, 10 Feb 2009 06:10:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n1A6A1um079048; Tue, 10 Feb 2009 06:10:01 GMT (envelope-from gnats) Resent-Date: Tue, 10 Feb 2009 06:10:01 GMT Resent-Message-Id: <200902100610.n1A6A1um079048@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Yuri Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D171D106564A for ; Tue, 10 Feb 2009 06:06:00 +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 C00868FC19 for ; Tue, 10 Feb 2009 06:06:00 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id n1A6605H030277 for ; Tue, 10 Feb 2009 06:06:00 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id n1A6600D030272; Tue, 10 Feb 2009 06:06:00 GMT (envelope-from nobody) Message-Id: <200902100606.n1A6600D030272@www.freebsd.org> Date: Tue, 10 Feb 2009 06:06:00 GMT From: Yuri To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: kern/131549: ifconfig can't clear 'monitor' mode on the wireless device X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2009 06:10:02 -0000 >Number: 131549 >Category: kern >Synopsis: ifconfig can't clear 'monitor' mode on the wireless device >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Feb 10 06:10:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Yuri >Release: 71-PRERELEASE >Organization: n/a >Environment: >Description: After I used 'airodump-ng -write ath0 ath0' ath0 interface was left in 'monitor' mode (which maybe is a bug in airodump itself). Command 'ifconfig ath0 -monitor' is supposed to clear 'monitor' mode. But it doesn't seem to make any difference. This is a very serious problem since after this interface isn't usable until reboot. It stays in 'monitor' mode (no packets go out or in). Same is true for ral0 device. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: