Problem with Kismet

[djbeenie]

Has anyone had this problem with Kismet?

I am running a D600 with an ipw2100 driver. Kismet seemed to install correctly.

[root@localhost ~]# kismet
Server options: none
Client options: none
Starting server...
Waiting for server to start before starting UI...
Will drop privs to bbrooks (500) gid 500
No specific sources given to be enabled, all will be ena
Enabling channel hopping.
Enabling channel splitting.
Source 0 (kismet): Enabling monitor mode for ipw2100 sou el 6...
FATAL: Failed to set channel 6 95:Operation not supported

[Jman]

The monitor mode is not supported on some drivers. I do not know the status of ipw2100.

[abatis]

what does #iwconfig show for the wireless card.

[djbeenie]

eth0 no wireless extensions.

eth1 unassociated ESSID:off/any Nickname:"ipw2100"
Mode:Managed Channel=0 Access Point: 00:00:00:00:00:00
Bit Rate=0 kb/s Tx-Power:off
Retry:on RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

sit0 no wireless extensions.

[abatis]

Here is mine (different interface) but what it looks like. Did you go through all the steps and set up the Kismet.conf? Yours looks like no signal level.

IEEE 802.11 ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: 00:00:00:00:00:00
Bit Rate:0 kb/s Tx-Power:20 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=0/94 Signal level=-95 dBm Noise level=-95 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


Also from the Kismet change log

May 17 2005 devel Added ipw2200 support with temporary sw_reset support to try
to come out of monitor mode. You'll need the 1.0.4 drivers
and new firmware, and you can force a reset of the card by
reloading the drivers
Added ipw2200 to fuzzy crypt list
Tweaked IP detection to not attempt to process IPs for any

maybe the 2100 needs other drivers for monitor mode.

Also did you use the latest drivers: http://svn.kismetwireless.net/links.shtml

[djbeenie]

This is what I go now. I was having issues connecting to wireless.

eth1 IEEE 802.11b ESSID:XXXXX" Nickname:"localhost.localdomain"
Mode:Managed Frequency:2.442 GHz Access Point: 00:12:XX:9E:XX:E0
Bit Rate=11 Mb/s Tx-Power:off
Retry:on RTS thr:off Fragment thr:off
Encryption key:11C0-FFXX-1234-1234-1234-C0FF-XX Security mode:open
Power Management:off
Link Quality=98/100 Signal level=-60 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:1 Missed beacon:0

[djbeenie]

Actualy it might be my Kismet.conf.

I am not sure how to set this up. I have this...i do not know if its right or not.

For my sources : ipw2100, eth1, kismet

Regards,
Beenie

[djbeenie]

Anyone have any ideas?

[abatis]

Here is mine I :) smiled the important stuff. i did shorten by deleting some # stuff.

# Kismet config file

# not continually reading --help!

# Version of Kismet config
version=2005.01.R1a

# Name of server (Purely for organiational purposes)
servername=Kismet

# User to setid to (should be your normal user)
:) suiduser=???????

# The initial channel is optional, if hopping is not enabled it can be used
# to set the channel the interface listens on.
# YOU MUST CHANGE THIS TO BE THE SOURCE YOU WANT TO USE
:) source=madwifi_g,ath0,madwifi
ipmap=ip_map

[Iron_Mike]

I just installed Kismet to see if I could get it to work. When you start it you have to start it from root, but you have to be in your bbrooks home directory when you do it..

I just noticed that you tried to start it from root@localhost, change to
bbrooks@localhost and try to start it....

[abatis]

Great point also I think the other key is to have suiduser=bbrooks in kismet conf.

[djbeenie]

Well I just logged on with bbrooks and same thing. :)

[root@localhost bbrooks]# kismet
Server options: none
Client options: none
Starting server...
Waiting for server to start before starting UI...
Will drop privs to bbrooks (500) gid 500
No specific sources given to be enabled, all will be enabled.
Enabling channel hopping.
Enabling channel splitting.
Source 0 (intel): Enabling monitor mode for ipw2100 source interface eth1 channel 6...
FATAL: Failed to set channel 6 95:Operation not supported
[root@localhost bbrooks]#

Is there any way to check to see if monitor mode is working correctly? Or is there any information about the sources. I think they are setup correctly but not sure of it.

Regards,
Beenie

[Iron_Mike]

Log in as bbrooks, but open a terminal window and su to root, once you are root make sure that you are in your bbrooks home directory and NOT roots home directory, then try to start kismet..

[djbeenie]

Same error message. I don't think the config file is setup properly. I do not know what they mean sources. The directions realy does not give good examples.

Regards,
Beenie

[Iron_Mike]

Did you change anything in the config file other than the suiduser=bbrooks, and the sources=ipw2100, eth1, kismet??? Other than I'm running out of ideas. Did you D/L for the 2100 from sourceforge, is the card showing "active" before runnning kismet.

[djbeenie]

Yes sir I did. Thats why I am banging my head on the table. HAHA

[Iron_Mike]

Simple then rerun make and make install, and create a config to start from scratch......

[djbeenie]

So you think my config file is configured correctly then?

Regards,
Beenie

[Iron_Mike]

Yep, if you only changed the suiduser=, and the source=, the values you have are correct.

[djbeenie]

Sweet, well then I will try to uninstall and resinstall...maybe just wipe the system and start over.

Regards,
Beenie

[Iron_Mike]

Before you do that. I just thought of something, about the channel. In the kismet config file for the Sources=ipw2100, eth1, kismet Do you happen to have the number 6 tacked onto the end of the string???? so it looks like this

Sources=ipw2100, eth1, kismet, 6 If you do, remove it and run it again.

[djbeenie]

No string - 6. :(