Date: Sat, 19 Feb 2005 21:52:43 -0800 From: Sam Leffler <sam@errno.com> To: Chris <racerx@makeworld.com> Cc: FreeBSD - Current <freebsd-current@freebsd.org> Subject: Re: MA401 worked w/5.3 - No go under CURRENT Message-ID: <421825AB.3060604@errno.com> In-Reply-To: <4217C407.8070605@makeworld.com> References: <421290FA.40108@makeworld.com> <20050216010859.GA57098@freebsd3.cimlogic.com.au> <4217C407.8070605@makeworld.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Chris wrote: > John Birrell wrote: > >> On Tue, Feb 15, 2005 at 06:16:58PM -0600, Chris wrote: >> >>> I'm just starting to follow the CURRENT branch and popped that >>> latest snapshot on my laptop. Under 5.3 my NetGear MA401 worked >>> with just adding something like this to /etc/rc.conf: >>> >>> ifconfig_wi0="inet xxx.xxx.xxx.xxx netmask 255.255.255.0 ssid XXX >>> wepmode on wepkey 0xxxxxxxxxxxxxxxxxxxxxxxxxxx" >>> >>> And everything came up just dandy. Has something changed? >> >> >> >> I hadn't tried to use my wireless stuff for months until a few days >> ago. I have >> the hostap running on current and I was trying to connect with wepmode >> on from >> a RELENG_5 laptop without success. I read the recent messages >> suggesting the >> explicit setting of the wepkey and default key, but that didn't solve >> the problem. >> >> I'll be away from the current box for 5 weeks and unable to debug >> anything, so I >> know this message is virtally useless. I just wanted to say "me too". >> > > Ok folks, I added the suggested stuff in /etc/rc.conf: > > ifconfig_wi0="inet xxx.xxx.xxx.xxx netmask 255.255.255.0 ssid XXX > wepmode on weptxkey 1 wepkey 1:0xxxxxxxxxxxxxxxxxxxxxxxxxxx" > > And /boot/loader.conf: > wlan_wep="YES" > > Still a no-go. Light on the wireless nic just blinks. > I'm pretty much at a loss - anyone? > Don't know if you've even associated (you didn't provide any info like the output of ifconfig to indicate one way or another). It's usually a good idea to verify you can associate with your ap w/o crypto before turning it on. If setting things up w/o crypto works then turn it back on and check for crypto errors (probably show up as input/output errors) that'd indicate your key setup is mismatched with the ap. Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?421825AB.3060604>