From owner-freebsd-net@FreeBSD.ORG Sun Oct 18 14:27:45 2009 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 18A0E106566B; Sun, 18 Oct 2009 14:27:45 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mx01.netsrc.de (mx01.netsrc.de [89.107.71.100]) by mx1.freebsd.org (Postfix) with ESMTP id CC4FE8FC24; Sun, 18 Oct 2009 14:27:44 +0000 (UTC) Received: from jessie.localnet (dslb-088-065-057-061.pools.arcor-ip.net [88.65.57.61]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.netsrc.de (Postfix) with ESMTP id A38F6192FD9; Sun, 18 Oct 2009 16:27:42 +0200 (CEST) From: Bernhard Schmidt To: freebsd-net@freebsd.org Date: Sun, 18 Oct 2009 16:27:37 +0200 User-Agent: KMail/1.12.1 (Linux/2.6.30-2-686; KDE/4.3.1; i686; ; ) References: <20091009170839.142800@gmx.net> <179b97fb0910142019u455995a4s2cdcf8ba744d98bf@mail.gmail.com> <200910150815.58174.bschmidt@techwires.net> In-Reply-To: <200910150815.58174.bschmidt@techwires.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200910181627.38060.bschmidt@techwires.net> Cc: Brandon Gooch , Lawrence Stewart , Lutz Bichler , Vassilis Laganakos Subject: Re: Intel WiFi 5100/5300 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, 18 Oct 2009 14:27:45 -0000 On Thursday 15 October 2009 08:15:57 Bernhard Schmidt wrote: > .. anyways, I'll post updates on sunday. Here we go. http://techwires.net/~bschmidt/patches/freebsd/iwn/ Testers/feedback welcome! Code is pretty stable although there are still a few open issues. Nothing major I should be able to figure them out. * I did only tests with a 5100 card, other might not yet work.. I will do tests wie 5300 and 4965 cards later this week. * 11N has not been tested at all. * Deauth/disconnect frames are not handled correctly, those yield firmware errors. The remote side might therefore not be able to clean up correctly, whichs lead to no answers to probe requests on new scans. * Encryption of any kind does not yet work. * Monitor mode/radiotap does not yet work. * IBSS mode has not been tested. * iwnfw module is locked somehow on kldunload. * RF kill switch might not work correctly. * Manpage needs an update. :) * Suspend/resume is broken. -- Bernhard