From owner-freebsd-usb@FreeBSD.ORG Fri May 18 06:10:04 2012 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8E681106566B for ; Fri, 18 May 2012 06:10:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 70A338FC0C for ; Fri, 18 May 2012 06:10:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q4I6A4qN086929 for ; Fri, 18 May 2012 06:10:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q4I6A4fl086927; Fri, 18 May 2012 06:10:04 GMT (envelope-from gnats) Date: Fri, 18 May 2012 06:10:04 GMT Message-Id: <201205180610.q4I6A4fl086927@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: PseudoCylon Cc: Subject: Re: usb/167847: [ural] dlink dwl-122g e crashes(?) when trying wap2 crypto X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: PseudoCylon List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 May 2012 06:10:04 -0000 The following reply was made to PR usb/167847; it has been noted by GNATS. From: PseudoCylon To: "Christopher J. Ruwe" Cc: bug-followup@freebsd.org Subject: Re: usb/167847: [ural] dlink dwl-122g e crashes(?) when trying wap2 crypto Date: Fri, 18 May 2012 00:00:42 -0600 On Thu, May 17, 2012 at 11:01 AM, Christopher J. Ruwe wrote: > The problem of not being able to connect persists. Do stations see the bsdap or nothing at all? Does % ifconfig wlan0 list ap list the ap? (Do it one of stations.) If it does, first issue # wlandebug -i wlan0 assoc+auth+crypto then have a station to connect the ap. Let me know what it says. Just in case, you have changed "UseYourOwnPwd" in hostapd.conf to the actual password you are using, haven't you? wpa_passphrase=UseYourOwnPwd AK