ORBIT-USER: Monitor Mode on baseline-2.3

[Kishore Ramachandran]

Hi Vijay:

I believe baseline-2.3.ndz has madwifi v0.9.3.1, which uses wlanconfig to
create a monitor mode VAP. For more details, you can refer to:
http://madwifi.org/wiki/UserDocs/MonitorModeInterface

Basically, the command to put the interface in monitor mode is different in
the new versions of the driver.

regards,
Kishore

On 7/31/07, Vijay Subramanian <subramanian.vijay at gmail.com> wrote:
>
> Hi,
> Can anyone confirm that monitor mode works on baseline-2.3.ndz?
>
> It looks like the driver and kernel use different versions of Wireless
> Extensions and some commands do not work.
>
> The following is an attempt to manually set the mode on this image.
> This problem means tcpdump does not work in monitor mode on
> baseline-2.3. As can be seen below, I can set it to managed mode.
>
> Any pointers will be highly appreciated. (A quick check on madwifi
> Trac seems to suggest this can be fixed by a kernel upgrade. I am
> hoping to avoid that.:)   )
> Monitor mode seems to work fine on baseline.ndz (with the old madwifi
> driver)
>
> Thanks for any help.
>
> root at node16-15:/tmp# ifconfig ath0 up
> root at node16-15:/tmp# ifconfig ath0 192.168.16.15
> root at node16-15:/tmp# iwconfig
> lo        no wireless extensions.
>
> eth0      no wireless extensions.
>
> eth1      no wireless extensions.
>
> wifi0     no wireless extensions.
>
> Warning: Driver for device ath0 has been compiled with version 22
> of Wireless Extension, while this program supports up to version 20.
> Some things may be broken...
>
> ath0      IEEE 802.11g  ESSID:"WINMAIN"  Nickname:""
>           Mode:Managed  Frequency:2.437 GHz  Access Point:
> 00:13:C4:F4:25:30
>           Bit Rate:1 Mb/s   Tx-Power:16 dBm   Sensitivity=0/3
>           Retry:off   RTS thr:off   Fragment thr:off
>           Encryption key:off
>           Power Management:off
>           Link Quality=26/94  Signal level=-68 dBm  Noise level=-94 dBm
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
>
> wifi1     no wireless extensions.
>
> ath1      IEEE 802.11b  ESSID:""  Nickname:""
>           Mode:Managed  Channel:0  Access Point: Not-Associated
>           Bit Rate:0 kb/s   Tx-Power:0 dBm   Sensitivity=0/3
>           Retry:off   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
>
> root at node16-15:/tmp# iwconfig ath0 mode
> Error for wireless request "Set Mode" (8B06) :
>     too few arguments.
> root at node16-15:/tmp# iwconfig ath0 mode Monitor
> Error for wireless request "Set Mode" (8B06) :
>     SET failed on device ath0 ; Invalid argument.
> root at node16-15:/tmp# iwconfig ath0 mode Managed
> root at node16-15:
>
>
>
> --
> Networks Lab, RPI
> http://poisson.ecse.rpi.edu/~vijay
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://orbit-lab.org/pipermail/orbit-user/attachments/20070731/8e74f296/attachment.htm