From owner-freebsd-current@FreeBSD.ORG Fri Nov 27 02:59:00 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A0864106568B for ; Fri, 27 Nov 2009 02:59:00 +0000 (UTC) (envelope-from behrnetworks@gmail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 36B358FC0A for ; Fri, 27 Nov 2009 02:59:00 +0000 (UTC) Received: by bwz5 with SMTP id 5so938370bwz.3 for ; Thu, 26 Nov 2009 18:58:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=vntcO3NclRIc+LzBnruZ7XkgDZEH20Sm7WDj5jB1loE=; b=MZKCMh2y7dQJ6rahjDAX9GA6TbGPbmT+RK2njMTK1GZu6egI2qDF5K3raLh61Ij1HU Za5Tnjt0b6NHM+MXCikeLvU03qvbw2UmjEAll/O/+snVaRqp9cnvR9VsRsb8i7ZS6xnd RctAb/12eqWkX/9+JaFJbeEqVREozj3OYQUVg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=kVwroXkcG4OAXFMFcQSGqQEkFqfFiblx094BSJ2dBy4shsuVNAvrIGZQss0UDXw86F q6qVd3AX0OTJU/N79vxD1lPy6ilsMki4subdqawtbUOhxhp/xeAT7+D2PMOH8eKXzvIO fbuw2BG+EcgDnnpkVcqk/UEOKcJO8UF1RKBAk= MIME-Version: 1.0 Received: by 10.204.3.211 with SMTP id 19mr468019bko.153.1259289118439; Thu, 26 Nov 2009 18:31:58 -0800 (PST) Date: Thu, 26 Nov 2009 21:31:58 -0500 Message-ID: <64aa03030911261831i1994a3dcpca545ab7ffd78dfe@mail.gmail.com> From: Chris To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: ipw driver on FreeBSD 8.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2009 02:59:00 -0000 Hello, Months ago there was some chatter about the ipw driver (For Centrino Intel 2100 wireless) being broken in 8.0 but that was when 8.0 was still under the CURRENT branch. Can anyone tell me if it has been fixed? I'm having a heck of a time trying to get it to work with the new VAP stuff. Here's the thread I'm referring to: http://old.nabble.com/wpa_supplicant-can%27t-associate-with-WPA2-AP-td22687633.html I'm seeing exactly the same problem shown in the thread when trying to associate with a regular WPA access point. Any info would be appreciated! Chris