From owner-freebsd-net@FreeBSD.ORG Mon Mar 23 21:50:05 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 475E0106568B for ; Mon, 23 Mar 2009 21:50:05 +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 36A068FC1A for ; Mon, 23 Mar 2009 21:50:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n2NLo5du086145 for ; Mon, 23 Mar 2009 21:50:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n2NLo5Q9086144; Mon, 23 Mar 2009 21:50:05 GMT (envelope-from gnats) Date: Mon, 23 Mar 2009 21:50:05 GMT Message-Id: <200903232150.n2NLo5Q9086144@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Matthias Apitz Cc: Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Mar 2009 21:50:05 -0000 The following reply was made to PR kern/132722; it has been noted by GNATS. From: Matthias Apitz To: Sam Leffler Cc: bug-followup@freebsd.org, freebsd-net@freebsd.org Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work Date: Mon, 23 Mar 2009 22:42:07 +0100 El día Monday, March 23, 2009 a las 12:12:04PM -0700, Sam Leffler escribió: > If you have the raw pcap capture please provide a url to it. I have to capture it and will provide it; > > From the log it appears you're sending+receiving wep-encrypted frames. > They keyid is the same and since you're receiving frames I have to > assume the key matter is correct as otherwise the h/w would drop the > frame. You can verify this by feeding the key into wireshark to check > if the frame contents make sense. > > I'm out of ideas. About the only thing I can suggest is you setup a > different ap w/ the same wep key and see if things work. If so then you > know it's something this ap is doing. I can't recall when I last tested > wep on HEAD but I'm pretty sure it works. I will re-test that when I > get a chance. > > Sam WEP in general works; my AP at home is configured as WEP and the entries in wpa_supplicant.conf are nearly the same, only the key differs: # my home # network={ ssid="tarara" scan_ssid=0 key_mgmt=NONE wep_tx_keyidx=0 wep_key0=xxxxxxxxxx } # Restaurante Odyssee (2007-11-18) # network={ ssid="ConnectionPoint" scan_ssid=0 key_mgmt=NONE wep_tx_keyidx=0 wep_key0=xxxxxxxxxxxxxxxxxxxx } but I will configure another AP to also use the same wep_key0, if you think that the problem could depend on the key itself; and I will check if I could get somewhere this model of AP for a test; matthias