From owner-freebsd-questions@FreeBSD.ORG Thu Nov 6 13:06:39 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7BF871065689 for ; Thu, 6 Nov 2008 13:06:39 +0000 (UTC) (envelope-from me@janh.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mx1.freebsd.org (Postfix) with ESMTP id 116A28FC30 for ; Thu, 6 Nov 2008 13:06:38 +0000 (UTC) (envelope-from me@janh.de) Received: from janh.freebsd (f054097186.adsl.alicedsl.de [78.54.97.186]) by mrelayeu.kundenserver.de (node=mrelayeu8) with ESMTP (Nemesis) id 0ML31I-1Ky4ZC1ZE5-0003Gx; Thu, 06 Nov 2008 14:06:30 +0100 Message-ID: <4912EBD6.8070805@janh.de> Date: Thu, 06 Nov 2008 14:06:30 +0100 From: Jan Henrik Sylvester User-Agent: Thunderbird 2.0.0.17 (X11/20080927) MIME-Version: 1.0 To: Ludovit Koren References: 20081106.114846.107247756.koren@tempest.sk Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX19XHQBprSAQrSlqgCL5pMyd6XoGjPuRn4zu44Q 73994BK5Rza1T9/ZEBaJRDiHsURbZYaLj/6vu8G64OVR7YkU1g YTGzs7PBgDI2finOza9wg== Cc: questions-list freebsd Subject: Re: Kismet on FreeBSD 7.0-STABLE X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Nov 2008 13:06:39 -0000 Ludovit wrote: > iwi0: mem 0xfafef000-0xfafeffff irq 9 > at device 3.0 on pci2 Monitor is broken on iwi on FreeBSD 7. I did report it during the 7.0-BETA, but there was at least one more report in the meantime. With exactly the same setup, I can use kismet with ural (ok), zyd (many broken packages), ral (ok), and ath (good, but see below). I do not receive a single package with iwi. I did replace my iwi miniPCI device by an ath one, which is more reliable anyhow. (iwi, as all Intel cards, occasionally dies and cannot reload firmware because of too little dma memory. That was reported a few times, too.) ath can monitor, even for longer periods of time, but if I do channel hopping in kismet, it often eventually stops receiving packages after a few minutes. Restarting kismet always fixes that. (I have had that with different ath cards.) iwi monitoring did work on 6.2, but often the card would not do regular networking after that until reboot and the problem with the firmware mentioned above was already present, although it was much better than on 6.1. For monitoring, you should either get a different card or try 6.X, 6-STABLE, or maybe 8-CURRENT. (I have no experience with the latter.) Cheers, Jan Henrik