For those wo have used Kismet available on SuSe 10.1, the two screenshots
whould tell it all..
-----------------------------------------------------------
FSSuSe10:/home/abc # iwconfig
lo no wireless extensions.
eth0 IEEE 802.11g ESSID:"LAB406"
Mode:Managed Frequency:2.462 GHz Access Point: 00:13:A3:5F:73:66
Bit Rate=36 Mb/s Tx-Power=20 dBm
Retry limit:7 RTS thr
ff Fragment thr
ff
Encryption
key:E704-BBDB-B974-89A5-E440-F6DB-7E81-A320-42A4-D835-808B-EAE8-DE5D-BBB2-39D1-5B42
Security mode
pen
Power Management
ff
Link Quality=82/100 Signal level=-48 dBm Noise level=-84 dBm
Rx invalid nwid:0 Rx invalid crypt:1 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:5 Missed beacon:1
eth1 no wireless extensions.
sit0 no wireless extensions.
-------------------------------------------------------
FSSuSe10:/home/abc # kismet
Server options: none
Client options: none
Starting server...
Waiting for server to start before starting UI...
Suid priv-dropping disabled. This may not be secure.
No specific sources given to be enabled, all will be enabled.
Enabling channel hopping.
Enabling channel splitting.
Source 0 (eth0): Enabling monitor mode for ipw2200 source interface eth0
channel 11...
FATAL: Failed to set monitor mode: Invalid argument. This usually means
your drivers either do not support monitor mode, or use a different
mechanism for getting to it. Make sure you have a version of your drivers
that support monitor mode, and consult the troubleshooting section of the
README.
FSSuSe10:/home/abc #
-----------------------------------------------------
FSSuSe10:/home/abc # iwconfig eth0 mode Monitor
Error for wireless request "Set Mode" (8B06) :
SET failed on device eth0 ; Invalid argument.
-----------------------------------------------------
WHAT else can I try???
My Wireless card on Toshiba laptop is (as shown in yast) Intel/PRO Wireless
2200 bg.