From owner-freebsd-net@FreeBSD.ORG Sun Apr 27 03:51:21 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B291A1065675 for ; Sun, 27 Apr 2008 03:51:21 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.251]) by mx1.freebsd.org (Postfix) with ESMTP id 6A3D18FC14 for ; Sun, 27 Apr 2008 03:51:21 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: by an-out-0708.google.com with SMTP id c14so1187226anc.13 for ; Sat, 26 Apr 2008 20:51:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=MXILP9kRPhgkQYE087AhFSMVgRwrl1N5bV3RvSv37sY=; b=Rif8W00PUov6yhYz9AyENH+gdmvlLPPpk3rh3Ph3Pmabh1nsIvCorQeb7lO5Gx3c+mA4sA4hGBDUP5NI9HUzyhDisGXZT/TVLlNhfdaA7GNY4jg1E2WGJQhkLefLqetijFL4ZT0LQD+f5Tzu5sdPwyVzm0P+cq9yArcoaHgnDJY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=CO07C5tbxCv61OiJomQ6d1tMN05+uIcAdRN95jZlTsGuRSHDzrRugu5NmrkoK0tZs5SrA7Tpt3EzjZTqpiZYbqorp5E3d0rUzoMgSoyve1xEsBOMkME2zcBZjWa5pecexoG9PbAUu/pQmb4nuSdOW9JQu1NhGsCb8RNt/+XPhLQ= Received: by 10.100.214.19 with SMTP id m19mr10016766ang.50.1209268280622; Sat, 26 Apr 2008 20:51:20 -0700 (PDT) Received: by 10.100.48.5 with HTTP; Sat, 26 Apr 2008 20:51:20 -0700 (PDT) Message-ID: Date: Sun, 27 Apr 2008 11:51:20 +0800 From: "Sepherosa Ziehau" To: freebsd-net In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: Kevin Lo Subject: Re: Connecting P1i to FreeBSD X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Apr 2008 03:51:21 -0000 On Sun, Apr 27, 2008 at 7:52 AM, Ivan Voras wrote: > Ivan Voras wrote: > > > Sepherosa Ziehau wrote: > > > > > > > Are you sure that your device works under IBSS mode? > > > > > > > Yes, since Windows doesn't support creating an AP from the card, and it > connects to Windows. Unless there are other modes that can do the same > thing... > > > > Actually there is a difference; here's a dump from laptop where the device > connects to the Windows machine: > > 23:49:18.013539 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:18.045340 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY > 23:49:18.148408 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:18.374477 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:18.377198 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:18.379066 Probe Response (SpeedTouch425488) [1.0* 2.0* 5.5* 11.0* > 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY > 23:49:18.659907 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY > 23:49:18.734842 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:18.762218 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY > 23:49:19.005423 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:19.008301 Probe Response (SpeedTouch425488) [1.0* 2.0* 5.5* 11.0* > 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY > 23:49:19.026747 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:19.366882 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:19.376645 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY > 23:49:19.411652 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:19.636460 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:19.637575 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:19.888667 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY > 23:49:19.990770 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY > 23:49:19.997530 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:20.268038 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:20.269293 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:20.271670 Probe Response (SpeedTouch425488) [1.0* 2.0* 5.5* 11.0* > 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY > 23:49:20.274467 Beacon (SpeedTouch425488) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 > 36.0 54.0 Mbit] ESS CH: 6, PRIVACY > 23:49:20.297986 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY > 23:49:20.492967 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:20.502751 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY > 23:49:20.629491 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:20.707738 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY > 23:49:20.899123 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:20.901458 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:20.989459 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:21.124700 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:21.219413 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY > 23:49:21.259747 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:21.321793 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY > 23:49:21.530624 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:21.531691 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:21.533326 Probe Response (SpeedTouch425488) [1.0* 2.0* 5.5* 11.0* > 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY > 23:49:21.833759 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY > > I didn't get the "Beacon" entries before. I expected to see actual data > packets in tcpdump, but I assume they are not in the dump because we're only > looking at the 802.11 events with -y ieee802_11? > I think you are using iwi to do the tap, could you put iwi into monitor mode, since iwi is "smart" device which may filter certain type of frames in non-monitor mode? I tested my rum: the beacon template set in the hardware is trashed in a strange a pattern What I got in the air; fc duration and certain part of mac address is trashed: 11:04:57.256700 Assoc Request (sephe-adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] 0x0000: 0000 2a01 0032 0430 4860 6c18 f32f 077a 0x0010: 4e9c 3b6a eb9f b01d afbe e402 0000 0000 0x0020: 6400 2200 000b 7365 7068 652d 6164 686f 0x0030: 6301 0882 848b 960c 1218 2403 0101 0602 0x0040: 9056 e96b 88d0 f6ef 5cc9 1d The actual beacon mbuf content: 80 00 00 00 ff ff ff ff ff ff 00 18 f3 2f 07 7a 4e 9c 3b 6a eb 9f 00 00 00 00 00 00 00 00 00 00 64 00 22 00 00 0b 73 65 70 68 65 2d 61 64 68 6f 63 01 08 82 84 8b 96 0c 12 18 24 03 01 01 06 02 00 00 2a 01 00 32 04 30 48 60 6c After several small code change, I found that beacon template size can't exceeds 64bytes. Small template space means you could only use rum IBSS in 11b mode. I have tried to setup BEACON_BASE1 but without result. If it is not a hardware design flaw then we will need data sheet to make it correct. Best Regards, sephe -- Live Free or Die