Date: Tue, 21 Feb 2006 23:48:33 -0600 From: Vulpes Velox <v.velox@vvelox.net> To: freebsd@meijome.net Cc: David Reid <david@jetnet.co.uk>, freebsd-mobile@freebsd.org Subject: Re: iwi failing after portupgrade Message-ID: <20060221234833.512eea38@vixen42.vulpes> In-Reply-To: <43FB1C4C.7000702@meijome.net> References: <43F755CB.5000607@jetnet.co.uk> <20060218135951.2afc6763@vixen42.vulpes> <43F905EA.9080003@meijome.net> <20060219190749.12707fe8@vixen42.vulpes> <43FB1C4C.7000702@meijome.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 22 Feb 2006 00:57:32 +1100 Norberto Meijome <freebsd@meijome.net> wrote: > 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. Just noticed I screwed that up there. Ifconfig list scan shows the results of scan and ifconfig scan scans. Meant to post about the error, but last two days have been hectic. Any ways, check the man, it is handy. ^_^ > > 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]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060221234833.512eea38>