Date: Wed, 22 Feb 2006 00:57:32 +1100 From: Norberto Meijome <freebsd@meijome.net> To: Vulpes Velox <v.velox@vvelox.net> Cc: David Reid <david@jetnet.co.uk>, freebsd@meijome.net, freebsd-mobile@freebsd.org Subject: Re: iwi failing after portupgrade Message-ID: <43FB1C4C.7000702@meijome.net> In-Reply-To: <20060219190749.12707fe8@vixen42.vulpes> References: <43F755CB.5000607@jetnet.co.uk> <20060218135951.2afc6763@vixen42.vulpes> <43F905EA.9080003@meijome.net> <20060219190749.12707fe8@vixen42.vulpes>
next in thread | previous in thread | raw e-mail | index | archive | help
Vulpes Velox wrote: >> Hi there, do you mind telling me how you do the 'listing' of >> available APs? I tried wistumbler but it locked up my box more >> often than not (was using 6.0 just before PRERELEASE#1, iwi as >> module). Maybe this issue is fixed if I build the latest iwi into >> the kernel? >> >> I also have installed kismet but havent configured it ... >> > > ifconfig iwi<whatever> list > gotcha, thanks. > If you want to rescan it is ifconfig iwi<whatever> list scan. > > This does cause problems if you have all ready associated true, once i have set it to bss MySSID it will always show that item... resetting SSID to "" i think fixes this. > and I have > under certain circumstances it will lock up. It seems worse with G > than B. yes, I agree with the lockup issue. it also happens to me if I do sudo iwicontrol iwi0 -k ifconfig [LOCKUP] nasty. thx Beto
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43FB1C4C.7000702>