From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 02:54:55 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8BD6E1065677 for ; Fri, 4 Jul 2008 02:54:55 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.238]) by mx1.freebsd.org (Postfix) with ESMTP id 592E08FC18 for ; Fri, 4 Jul 2008 02:54:55 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1455147rvf.43 for ; Thu, 03 Jul 2008 19:54:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:date:to:subject :message-id:mail-followup-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent:organization :x-operation-sytem:from; bh=03QaGi1knQrwDDrbM6M7qhh76Stn8cI5I4x+zpgwEDk=; b=EAJK4SG2/wM4vCw1uovRn+NfVhaK4R5yE5+TePIyWZFT7Kdlv3kUPI6DHKffFg8fqU iIGXx9a9kdFeFmTY/4tNMi++eYgo9SBi8vTyVQ1AaZG+/krYptKZzisg1D7mfbrhikVK JPmWROW2Gq4o2o2V97X2JVk4S35kE+xw7lV5w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:to:subject:message-id:mail-followup-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent :organization:x-operation-sytem:from; b=KjQiiDRda1XquFOqhd4XQDWYjIHDXbMpg+ygXEdwHFqjlpH2PEcJxvqqaFKvhVaUOH 7tUG/iT1wUXk1FOdvavTWe0yxaXRPvVH0HDXEjuskqW6DxvzqmtIN3uMCx1IXUwd/Np+ 7Wqa+e8TGV2+m0DAaegZORwNyYAYMWsoK4KDc= Received: by 10.115.78.1 with SMTP id f1mr2337597wal.150.1215140094951; Thu, 03 Jul 2008 19:54:54 -0700 (PDT) Received: from freebsd.weongyo.org ( [211.53.35.67]) by mx.google.com with ESMTPS id k35sm1140481waf.15.2008.07.03.19.54.23 (version=SSLv3 cipher=RC4-MD5); Thu, 03 Jul 2008 19:54:54 -0700 (PDT) Received: by freebsd.weongyo.org (sSMTP sendmail emulation); Fri, 4 Jul 2008 11:54:01 +0900 Date: Fri, 4 Jul 2008 11:54:01 +0900 To: current@freebsd.org Message-ID: <20080704025401.GF57570@freebsd.weongyo.org> Mail-Followup-To: current@freebsd.org References: <20080703114158.GE57570@freebsd.weongyo.org> <486CEAF7.6040709@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <486CEAF7.6040709@freebsd.org> User-Agent: Mutt/1.4.2.3i Organization: CDNetworks. X-Operation-Sytem: FreeBSD From: Weongyo Jeong Cc: Subject: Re: Q: 802.11 vap monitor mode X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 02:54:55 -0000 On Thu, Jul 03, 2008 at 08:06:31AM -0700, Sam Leffler wrote: > Weongyo Jeong wrote: > >During testing a new driver, I got a problem to test a monitor mode at > >802.11 vap I'm using. > > > ># uname -a > >FreeBSD kkk 8.0-CURRENT FreeBSD 8.0-CURRENT #6: Wed May 14 11:27:37 KST > >2008 root@kkk:/usr/obj/usr/src/sys/GENERIC i386 > ># ifconfig wlan0 create wlandev upgt0 wlanmode monitor > ># ifconfig wlan0 up > ># ifconfig > >[...] > >upgt0: > >flags=108943 > >metric 0 mtu 2290 > > ether 00:0f:b5:dd:6f:36 > > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > > > > status: running > >wlan0: > >flags=28943 > >metric 0 mtu 1500 > > ether 00:0f:b5:dd:6f:36 > > inet6 fe80::20f:b5ff:fedd:6f36%wlan0 prefixlen 64 scopeid 0xd > > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > > > > status: running > > ssid "" channel 1 (2412 Mhz 11g) bssid 00:0f:b5:dd:6f:36 > > country US authmode OPEN privacy OFF txpower 0 scanvalid 60 > > protmode CTS > > > >As seeing, it looks work but the problem is happend when I ran stumbler > >(src/tools/tools/net80211/stumbler) program. > > > >The error message is "ioctl(BIOCSDLT): Invalid argument" that it's > >emitted to screen when I execute the following command: > ># ./stumbler wlan0 > > > >Are there something I missed? > > > What DLT is stumbler using? If it's requesting IEEE802_11_RADIO then DLT was DLT_IEEE802_11_RADIO so it looks the stumbler code is broken as Paul B. Mahol mentioned. > this will fail as that is not available for the vap, only for the > underlying device. This is an open issue that I'm looking for help > with--previously an 802.11 device supported 3 DLT's: 802.3, 802.11, and > radiotap but now it only supports the first 2. The net80211 layer does > not have all the data required to dispatch radiotap headers (only the > driver does) so we need to push the information up to net80211 for each > rx'd packet (possibly expensive) or provide some net80211-level support > for dispatching radiotap data through vap's. regards, Weongyo Jeong