Date: Mon, 28 Apr 2008 01:22:09 +0200 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-net@freebsd.org Subject: Re: Connecting P1i to FreeBSD Message-ID: <fv31r2$est$1@ger.gmane.org> In-Reply-To: <ea7b9c170804262052s1877a325rfffa364fca47f92b@mail.gmail.com> References: <fur5qu$u5i$1@ger.gmane.org> <ea7b9c170804242354g56983458i5a1461ca9d18a015@mail.gmail.com> <fv0dmo$squ$1@ger.gmane.org> <fv0f8c$f3$1@ger.gmane.org> <ea7b9c170804262051q4768244blbb4e93381c9a903d@mail.gmail.com> <ea7b9c170804262052s1877a325rfffa364fca47f92b@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig3A0D1FB44691DBF17F50A0D9 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Sepherosa Ziehau wrote: >> 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? Do you still need these tests since you did your own with the rum=20 device? Apparently my iwi device causes kernel panic when switching=20 modes or some related activity, so it's difficult to work with. >> I tested my rum: the beacon template set in the hardware is trashed i= n >> a strange a pattern > BTW, the pattern is anything beyond 64bytes will be wrapped. See the > dump and the beacon content. Yes, I see what you mean... >> 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= I tried, and I can't run rum in IBSS in 11b (at least the device in=20 question ignores it as always). Can you? >> result. If it is not a hardware design flaw then we will need data >> sheet to make it correct. I don't think it's a hardware fault since it "just works" in Windows=20 without any special configuration. Btw. what hardware revision is your rum device? Mine is C1 (found on the = label before the firmware version). I don't know about data sheets, but the Linux driver (rum-equivalent) is = available from the chips' vendor:=20 http://www.ralinktech.com/ralink/Home/Support/Linux.html It should be the one for RT2500USB. --------------enig3A0D1FB44691DBF17F50A0D9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIFQqhldnAQVacBcgRAqk/AKCGVoeJyqT/ABJ1VaUCiOKQs7hX/ACfXqvT WCk/6QUyq7adV2kR4LVA0Qc= =plcI -----END PGP SIGNATURE----- --------------enig3A0D1FB44691DBF17F50A0D9--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fv31r2$est$1>