From owner-freebsd-questions@FreeBSD.ORG Wed Nov 2 13:22:40 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF4EE16A41F for ; Wed, 2 Nov 2005 13:22:40 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from aiolos.otenet.gr (aiolos.otenet.gr [195.170.0.93]) by mx1.FreeBSD.org (Postfix) with ESMTP id F202243D53 for ; Wed, 2 Nov 2005 13:22:39 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226]) by aiolos.otenet.gr (8.13.4/8.13.4/Debian-1) with SMTP id jA2DKTUE007943; Wed, 2 Nov 2005 15:20:30 +0200 Received: from flame.pc (flame [127.0.0.1]) by flame.pc (8.13.4/8.13.4) with ESMTP id jA2DKNet001678; Wed, 2 Nov 2005 15:20:23 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by flame.pc (8.13.4/8.13.4/Submit) id jA2DKMhZ001677; Wed, 2 Nov 2005 15:20:22 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Date: Wed, 2 Nov 2005 15:20:22 +0200 From: Giorgos Keramidas To: Stijn Hoop , freebsd-questions@freebsd.org Message-ID: <20051102132022.GA1463@flame.pc> References: <20051031182539.GA52720@pcwin002.win.tue.nl> <20051031182851.GB1428@flame.pc> <20051031184058.GB52720@pcwin002.win.tue.nl> <20051031184449.GA1690@flame.pc> <20051102074102.GC52720@pcwin002.win.tue.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051102074102.GC52720@pcwin002.win.tue.nl> Cc: Subject: Re: cannot get IP working between associated ath0 & AP, what to do? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 13:22:40 -0000 On 2005-11-02 08:41, Stijn Hoop wrote: > On Mon, Oct 31, 2005 at 08:44:49PM +0200, Giorgos Keramidas wrote: > > Make sure you're not running a BSD firewall too, like the one I had a > > few days ago and kept failing to obtain an address from my wireless AP > > at home because of the paranoid ruleset I was using :) > > First I confirmed that it really wasn't a firewall issue. Then > of course I found out it was a PEBKAC; I used this command to > configure ath0: > > # ifconfig ath0 ssid FOO wepmode on wepkey 0xBAR > > which showed an association but did not allow packets to be > sent. The correct incantation is > > # ifconfig ath0 ssid FOO wepmode on wepkey 0xBAR weptxkey 1 > > which, I presume, also sets the wepkey to be used for > transmitting packets after destination. I must say that I don't > really see the value of specifying the WEP key and then not > using it, but then again this is not my OS :-) Ah! Hehe. That's a nice catch there. I didn't hit this because I explicitly specified more than the absolutely necessary stuff in my /root/netstart.home shell script, which I use to connect to my home's network. The important bit for the wepkey setup is the ifconfig_ath0 line, which contains: % # Use a format similar to rc.conf(5) to allow /etc/rc.d/netif to % # find and use these settings automagically. % export ifconfig_ath0="DHCP ssid "FOO" \ % wepmode on weptxkey 1 wepkey '1:0xXXXXXXXXXXXXXXXXXXXXXXXXXX'" I'm explicitly specifying that weptxkey is going to be key 1 and then prepending the number of the key, so this didn't happen here. Thanks for the followup, since now I know what to look for when things don't Just Work(TM) in the future :)))