-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday 20 January 2003 08:16 am, Chmouel Boudjnah wrote:
> Jeremy Salch <[EMAIL PROTECTED]> writes:
> > Yes sir! I will test anything you want with the wireless stuff. I work
> > for a Wireless Internet SService Provider so i use wireless stuff every
> > day
>
> great, would you start to use wireless-tools which should be fixed the
> version conflict ?
The program is saying that it is still running with version 13 ?
[root@pr2 salch]# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
Warning: Driver for device eth1 has been compiled with version 15
of Wireless Extension, while this program is using version 13.
Some things may be broken...
eth1 IEEE 802.11-DS ESSID:""
Mode:Managed Frequency:2.412GHz Access Point: FF:FF:FF:FF:FF:FF
Bit Rate:11Mb/s Tx-Power=0 dBm Sensitivity=0/65535
Retry limit:16 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:176/10 Signal level:-111 dBm Noise level:-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:20 Missed beacon:0
wifi0 IEEE 802.11-DS ESSID:""
Mode:Managed Frequency:2.412GHz Access Point: FF:FF:FF:FF:FF:FF
Bit Rate:11Mb/s Tx-Power=0 dBm Sensitivity=0/65535
Retry limit:16 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:176/10 Signal level:-111 dBm Noise level:-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:20 Missed beacon:0
And the other issue was kismet not working, and it still doesn't work. output
following:
[root@pr2 salch]# kismet_monitor
Using /etc/kismet.conf sources...
Enabling monitor mode for a cisco card on eth1
Modifying device eth1
[root@pr2 salch]# kismet
Server options: none
Client options: none
Starting server...
Will drop privs to salch (501)
No enable sources specified, all sources will be enabled.
Source 0 (cisco): Using pcap to capture packets from eth1
FATAL: Source 0 (cisco): pcap reported netlink type 1 (EN10MB) for eth1. This
probably means you're not in RFMON mode or your drivers are reporting a bad
value. Make sure you have run kismet_monitor.
Starting UI...
FATAL: Could not connect to localhost:2501.
Terminating...
Done. Run kismet_unmonitor or eject and re-insert your card (or restart your
pcmcia services) to return your card to normal operation.
[root@pr2 salch]#
I'm not sure if the problem with kismet is related to the problem with the
wireless estensions version or not, all i do know is with the other driver
removed, leaving the one that matched the wireless extensions versoin, in
mkd9.0 kismet was able to access the device properly.
- --
http://tblx.net/encrypt/index.html for pgp key
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+LBNvxqewf6/SKYURAqE+AJ91JLY2ttKjywUrKUKu6KrknHLNwQCeLh/g
0RYMV8RM63AlP9bCdH6/HbM=
=5jzh
-----END PGP SIGNATURE-----