From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1F7NNX-0001k8-G7 for garchives@archives.gentoo.org; Fri, 10 Feb 2006 01:47:19 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k1A1j9a8017564; Fri, 10 Feb 2006 01:45:09 GMT Received: from mail.netspace.net.au (thunder.netspace.net.au [203.10.110.71]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k1A1dg1g019400 for ; Fri, 10 Feb 2006 01:39:43 GMT Received: from orpheus (unknown [150.101.6.82]) by mail.netspace.net.au (Postfix) with ESMTP id 0274E4AD49 for ; Fri, 10 Feb 2006 12:39:40 +1100 (EST) Subject: Re: [gentoo-user] Connecting to a WEP Airport router From: Iain Buchanan To: gentoo-user@lists.gentoo.org In-Reply-To: <49bf44f10602091641v351a0e38jaba2b0fd2a75f0de@mail.gmail.com> References: <49bf44f10602071240j737ddae9p47d8c1246de4862@mail.gmail.com> <49bf44f10602091641v351a0e38jaba2b0fd2a75f0de@mail.gmail.com> Content-Type: text/plain Date: Fri, 10 Feb 2006 11:09:37 +0930 Message-Id: <1139535577.19833.10.camel@orpheus> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 16487fdc-0369-41da-a906-a7ab9b3dfdc3 X-Archives-Hash: 37a40458b1270bc12f14596277b3afe9 On Thu, 2006-02-09 at 16:41 -0800, Grant wrote: > I still can't get this to work. I have the essid and key defined in > '/etc/conf.d/net'. I've tried defining the key like "s:key" and > "s:key enc open" and "open s:key". I've tried other little things but > to no avail. I can connect to a non-Airport WEP router via > wpa_supplicant just fine, and an unencrypted non-Airport router via > iwconfig just fine as well. What else could be the problem connecting > to this WEP Airport router via iwconfig? > > I've also tried Eric's suggestion of running each command manually > with the same results. I've noticed that wireless can be sensitive to the order and timing of running iwconfig commands. Run these two lines from bash (substitute DEV=wlan0 for your device, and the key and essid): function iw { sleep 5; iwconfig 2>/dev/null | grep "Access Point"; } DEV=wlan0 iw; sudo iwconfig $DEV essid youressid; iw; sudo iwconfig $DEV key 00001111222233334444555566; iw; sudo iwconfig $DEV key open; iw then tell me if the output you see is like this: Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated or if you see something other than "Not-Associated". You could also try playing with the order of the commands, but usually I find it goes essid, key, enc. HTH, -- Iain Buchanan Nezvannyi gost'--khuzhe tatarina. [An uninvited guest is worse than the Mongol invasion] -- Russian proverb -- gentoo-user@gentoo.org mailing list