From owner-freebsd-hardware@FreeBSD.ORG Sat Oct 31 16:46:47 2009 Return-Path: Delivered-To: hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C9211065670; Sat, 31 Oct 2009 16:46:47 +0000 (UTC) (envelope-from onemda@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 6B22B8FC0A; Sat, 31 Oct 2009 16:46:46 +0000 (UTC) Received: by bwz5 with SMTP id 5so4762639bwz.3 for ; Sat, 31 Oct 2009 09:46:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=5TrI9ExvasXNhckC/rMrPeRWGd7dwSviLFEphesdNsI=; b=hHIb65kzGQVM8NsbZEZdu3PDEFldKZDSlVS7J5+DOL2tglnHqYSDN3t42KMYj9VVg/ YXsWgrKh19dfUU+bff5ks4qLrxbgxk++lfzWLXd4jPX69v6DI1cw4uNAF9RNdety2/X5 Pg4GHNS/NaohIiO2VQ1TQtKygR+so5VPAE0Pc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=YJP4TssJUW94kYqMyYlDZzNRhBjoKj/FnVp92xKN4W2ujaOyNNDoq3atwyFQDL1141 A0RF4BINREb5/IfSIOdiKI61NZf5wOeiMZc8xTelK4J6QND7crqBvt3aCCwkJZpieXK/ jOpie3a27YDpTKcII3W6fu+9Qe9xG/xEJUzcs= MIME-Version: 1.0 Received: by 10.103.81.21 with SMTP id i21mr1212519mul.57.1257005816637; Sat, 31 Oct 2009 09:16:56 -0700 (PDT) In-Reply-To: <9bbcef730910310830s43237918g1489beb1fe9fae9a@mail.gmail.com> References: <9bbcef730910310830s43237918g1489beb1fe9fae9a@mail.gmail.com> Date: Sat, 31 Oct 2009 17:16:56 +0100 Message-ID: <3a142e750910310916labe85e5ke804386a834c49c8@mail.gmail.com> From: Paul B Mahol To: Ivan Voras Content-Type: text/plain; charset=ISO-8859-1 Cc: stable@freebsd.org, hardware@freebsd.org Subject: Re: hostapd "deauthenticated due to local deauth request" X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Oct 2009 16:46:47 -0000 On 10/31/09, Ivan Voras wrote: > I'm trying to setup an AP with a run0 interface on latest 8-STABLE but > apparently 802.11 association fails: > > Oct 31 16:21:30 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE > 802.11: associated > Oct 31 16:21:33 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE > 802.11: deauthenticated due to local deauth request > Oct 31 16:21:33 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE > 802.11: deassociated > Oct 31 16:21:35 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE > 802.11: associated > Oct 31 16:21:38 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE > 802.11: deauthenticated due to local deauth request > Oct 31 16:21:38 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE > 802.11: deassociated > > etc. Apparently the client never comes to the phase to receive DHCP address. > > The client in this case is WinXP and the setup did work with 7-STABLE, > though with a bug in the rum driver which caused regular kernel panics > on the AP. > I tried same one with rum(4) as AP and ndis(4) as client on same machine(some version of 8.0 - CURRENT). ndis client (configured via wpa_supplicant) would keep auth and deauth all the time. I came to conclusion that rum is broken. But I think I remmember that bwi(4) (as a client) did not have such problem ... (I will test again to see)