Date: Sat, 07 Jul 2007 13:10:50 -0700 From: Sam Leffler <sam@errno.com> To: Nathan Lay <nslay@comcast.net> Cc: freebsd-current@freebsd.org Subject: Re: -pureg doesn't stick Message-ID: <468FF34A.7070306@errno.com> In-Reply-To: <468C5FAF.8060702@comcast.net> References: <468C5FAF.8060702@comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Nathan Lay wrote: > Hi list, > I have a recent build (July 1st) and running it as a wireless AP (with > hostapd WPA-PSK TKIP) using an atheros card (Netgear WG311T). I've been > trying to get an 802.11b client on and I noticed the -pureg option > doesn't seem to stick at bootup. > e.g. this rc.conf line > ifconfig_ath0="ssid Lamp channel 9 mediaopt hostap -pureg up" > > Maybe -pureg should be specified somewhere else in that line (I also > tried "-pureg ssid Lamp channel 9 mediaopt hostap up")? Anyways, I have > to login and manually set ath0 to -pureg in order for the 802.11b client > to associate. pureg is not the default. Can you provide ifconfig -v output that shows it enabled? Also wlandebug auth+assoc should show why your 11b client is not allowed to associate. > > On the side, this same 802.11b client, which runs Windows XP SP2 on a > Thinkpad T41 with an Intel Pro Wireless 2100 card will crash both > 6.2-RELEASE and 7.0-CURRENT with medium traffic (e.g. streaming radio). > On the 6.2 system, the backtrace indicated that the crash occurred in > the atheros driver itself ... though I don't have that core handy. I > have no way to get the debugging information off of the 7.0 machine > until I get a serial cable, but the crash is fairly simple to reproduce > (The 6.2 system would crash 2-3 times a day due to this one client). I need a stack trace to proceed. Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?468FF34A.7070306>