Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 03 Aug 2005 08:53:02 -0700
From:      Sam Leffler <sam@errno.com>
To:        Muzaffar Ariff <mus.bsd@gmail.com>
Cc:        Stefan Bauer <duke@splatterworld.de>, freebsd-mobile@freebsd.org
Subject:   Re: Fwd: Orinoco classic gold and kismet.conf
Message-ID:  <42F0E85E.9070903@errno.com>
In-Reply-To: <8eb2b810508030116736dd52b@mail.gmail.com>
References:  <8eb2b810507252237652aa5f9@mail.gmail.com>	<42E5E2E0.4060707@splatterworld.de>	<8eb2b810508010013a5a8706@mail.gmail.com>	<42EE0C8C.2030405@splatterworld.de>	<8eb2b8105080205223553f0c8@mail.gmail.com>	<8eb2b81050802052328d9a1d1@mail.gmail.com>	<42EF949E.1080600@splatterworld.de>	<8eb2b8105080219257ab1dbb0@mail.gmail.com> <8eb2b810508030116736dd52b@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Muzaffar Ariff wrote:
> Some additional info on my problem, I've manage to capture the output
> when I start kismet.
> 
> .... removed the top half of the output
> Listening on port 2501.
> Allowing connections from 127.0.0.1/255.255.255.255
> Registering builtin client/server protocols...
> Registering requested alerts...
> Registering builtin timer events...
> Gathering packets...
> Starting UI...
> Looking for startup info from localhost:2501....FATAL: wi0: failed to
> set channel 52: Invalid argument

wi is an 11b-only card and you're trying to setup 11a channels; change 
the channel set in the kismet.conf file to only hold channels 1-11.  I 
don't recall what the exact knob is but it should be obvious.

I've suggested to the kismet author that on bsd systems kismet can 
figure out everything it needs to operate and should not require any of 
this configuration stuff--but the code is structured more for other 
systems where this isn't feasible.

> Terminating.
> Didn't detect any networks, unlinking network list.
> Didn't detect any networks, unlinking CSV network list.
> Didn't detect any networks, unlinking XML network list.
> Didn't detect any Cisco Discovery Packets, unlinking cisco dump
> Didn't capture any packets, unlinking dump file
> Didn't see any weak encryption packets, unlinking weak file
> Sending termination request to channel control child 807...
> Waiting for channel control child 807 to exit...
> Kismet exiting.
> 
> Now its says its exiting kismet but the gui still starts up with no
> activity at all. I see that I might have a problem to set my wi on
> channel 52 but looking at kismet.conf I can't seem to find anything
> wrong with it.
> 
> My kismet.conf (only the channel part):
> # Users outside the US might want to use this list:
> # defaultchannels=IEEE80211b:1,7,13,2,8,3,14,9,4,10,5,11,6,12
> # defaultchannels=IEEE80211b:1,6,11,2,7,3,8,4,9,5,10
> defaultchannels=IEEE80211b:1,7,13,2,8,3,14,9,4,10,5,11,6,12
> 
> # 802.11g uses the same channels as 802.11b...
> # defaultchannels=IEEE80211g:1,6,11,2,7,3,8,4,9,5,10
> defaultchannels=IEEE80211g:1,7,13,2,8,3,14,9,4,10,5,11,6,12
> 
> # 802.11a channels are non-overlapping so sequential is fine.  You may want to
> # adjust the list depending on the channels your card actually supports.
> #defaultchannels=IEEE80211a:36,40,44,48,52,56,60,64,100,104,108,112,116,120,124,128,132,136,140,149,153,157,161,184,188,192,196,200,204,208,212,216
> defaultchannels=IEEE80211a:36,40,44,48,52,56,60,64
> 
> # Combo cards like Atheros use both 'a' and 'b/g' channels.  Of course, you
> # can also explicitly override a given source.  You can use the script
> # extras/listchan.pl to extract all the channels your card supports.
> defaultchannels=IEEE80211ab:1,6,11,2,7,3,8,4,9,5,10,36,40,44,48,52,56,60,64
> 
> Does anyone have an idea to fix this?

I believe the source= stmt defines the underlying channel set.  If you 
can't figure this out try posting your entire kismet.conf file.

	Sam




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42F0E85E.9070903>