From owner-freebsd-current@FreeBSD.ORG Tue Mar 24 19:59:12 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 9DAF610656C2 for ; Tue, 24 Mar 2009 19:59:12 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from megatron.madpilot.net (megatron.madpilot.net [88.149.173.206]) by mx1.freebsd.org (Postfix) with ESMTP id 4654A8FC22 for ; Tue, 24 Mar 2009 19:59:12 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from localhost (localhost [127.0.0.1]) by megatron.madpilot.net (Postfix) with ESMTP id 7D152130C3C; Tue, 24 Mar 2009 20:59:11 +0100 (CET) X-Virus-Scanned: amavisd-new at madpilot.net Received: from megatron.madpilot.net ([127.0.0.1]) by localhost (megatron.madpilot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N2GMt2hLidP6; Tue, 24 Mar 2009 20:59:05 +0100 (CET) Received: from wedge.madpilot.net (localhost [127.0.0.1]) by megatron.madpilot.net (Postfix) with ESMTP; Tue, 24 Mar 2009 20:59:05 +0100 (CET) Message-ID: <49C93B89.1090201@madpilot.net> Date: Tue, 24 Mar 2009 20:59:05 +0100 From: Guido Falsi User-Agent: Thunderbird 2.0.0.21 (X11/20090323) MIME-Version: 1.0 To: Sam Leffler References: <49C92C9F.4050000@madpilot.net> <49C9357A.8000609@freebsd.org> In-Reply-To: <49C9357A.8000609@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: wpa_supplicant can't associate with WPA2 AP 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: Tue, 24 Mar 2009 19:59:13 -0000 Sam Leffler wrote: > Guido Falsi wrote: >> and excerpt from rc.conf: >> >> wlans_ipw0="wlan0" >> create_args_wlan0="wlanmode sta country IT" >> ifconfig_wlan0="WPA DHCP" > Thanks for the fast feedback! > Unfortunately the vap conversion of the ipw driver never was completed > (it's the only driver in the tree that is known to be totally broken). > It's on my todo list for 8.0 but would happily defer to someone else > :). I'm actually surprised you got this far. I'm an obstinate person :) Unluckily I don't even know from where to start to hack it. If I could anyway help you in some way, just ask. -- Guido Falsi