Re: Wireless capture - ReadList.com

3 msg	Which GigE NIC for reliable use?
3 msg	Intel PowerTop tool on FreeBSD?

Wireless capture
\ Eric L. Chen (21 Jun 2007)
. \ Sam Leffler (21 Jun 2007)
. . \ Stefan Ehmann (21 Jun 2007)
. . . \ Henrik Brix Andersen (21 Jun 2007)
. . . . \ Niki Denev (21 Jun 2007)
. . . . . \ Stefan Ehmann (21 Jun 2007)
. . . . . . \ Sam Leffler (21 Jun 2007)

7 msg	Promise SATA300 TX4 card issues
2 msg	ZFS scrub gone wrong
12 msg	Kernel Panic in latest -CURRENT
5 msg	AGPGART not found ... ( on Q965)
10 msg	ZFS and deadlock with {nullfs,NFS}
17 msg	ZFS status now in June? / stable enough for a f...
1 msg	Camellia block cipher for geli (GEOM ELI).
3 msg	truss(1) gets confused after execve
2 msg	Panic in callout_reset()
1 msg	Acer Aspire 5100 problems in current
2 msg	Re: i386 with PAE or AMD64 on PowerEdge with 4G...
19 msg	[head tinderbox] failure on sparc64/sparc64
11 msg	Current does not boot - BIOS problem?
3 msg	ukbd broken as module
1 msg	zfs and backup
2 msg	pkg_add : works fine when compiled normally ;se...
17 msg	wireless

Subject:	Re: Wireless capture
Group:	Freebsd-current
From:	Sam Leffler
Date:	21 Jun 2007

Stefan Ehmann wrote:
> On Thursday 21 June 2007 22:33:58 Niki Denev wrote:
>> Henrik Brix Andersen wrote:
>>> On Thu, Jun 21, 2007 at 06:56:15PM +0200, Stefan Ehmann wrote:
>>>> kismet doesn't detect any APs after the 802.11 changes. I thought I had
>>>> to wait until someone commits the wlan_scan_monitor module. But it seems
>>>> like this won't help.
>>>>
>>>> Any idea why kismet stopped working? Except for the missing module, I
>>>> haven't seen any suspicous message.
>>> For what it's worth, kismet still works as expected on my -CURRENT box
>>> using the ath(4) driver.
>>>
>>> Regards,
>>> Brix
>> I have just checked and it works here too, with ral(4) pccard.
>
> Thanks for your reports.
>
> So it's either a bug in iwi or something wrong on my side. It has worked
> before and I haven't changed the config though.

iwi has never been a reliable packet sniffer but it sounds like a
regression. FWIW iwi sniffs by "scanning a channel" but since it wasn't
possible to reliably abort a scan the scan requests were made for very
short periods of time and then resubmitted on timeout. This means you
can easily miss frames between resubmitted scan requests.

Sam
_______________________________________________
freebsd-current mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe"