#972: Monitor mode acts strange and doesnt work
------------------------------+---------------------------------------------
 Reporter:  [EMAIL PROTECTED]  |            Owner:                              
                       
     Type:  defect            |           Status:  new                          
                      
 Priority:  major             |        Milestone:  version 0.9.x - progressive 
release candidate phase
Component:  madwifi: driver   |          Version:  trunk                        
                      
 Keywords:  monitor           |   Patch_attached:  0                            
                      
------------------------------+---------------------------------------------
 Hi
 The card is a DLink G510, which has Atheros 5005G. It connects to a WAP
 router without any problem(using wpa_supplicant), but the monitor mode
 acts strange and cant work at all.

 {{{
 madwifi # wlanconfig ath1 create nounit wlandev wifi0 wlanmode monitor
 ath1

  madwifi # iwconfig
 lo        no wireless extensions.

 wifi0     no wireless extensions.

 ath0      IEEE 802.11g  ESSID:"NetGear"
           Mode:Managed  Frequency:2.422 GHz  Access Point:
 00:14:6C:90:4B:F8
           Bit Rate:12 Mb/s   Tx-Power:18 dBm   Sensitivity=0/3
           Retry:off   RTS thr:off   Fragment thr:off
           Encryption key:9C68-E5C5-140C-625C-85A7-503C-517E-43B3
 Security mode:restricted
           Power Management:off
           Link Quality=7/94  Signal level=-86 dBm  Noise level=-93 dBm
           Rx invalid nwid:1139  Rx invalid crypt:0  Rx invalid frag:0
           Tx excessive retries:0  Invalid misc:0   Missed beacon:0

 ath135    IEEE 802.11g  ESSID:""
           Mode:Monitor  Channel:0  Access Point: Not-Associated
           Bit Rate:0 kb/s   Tx-Power:18 dBm   Sensitivity=0/3
           Retry:off   RTS thr:off   Fragment thr:off
           Encryption key:off
           Power Management:off
           Link Quality=7/94  Signal level=-86 dBm  Noise level=-93 dBm
           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
 }}}

 Please notice that the result of wlanconfig shows ath1 but I actually get
 an ath135. The number keeps increasing each time when I add and then
 destroy a monitor device(even after reboot)

 after "ifconfig ath135 up", I run "airodump-ng ath135", the scan interface
 appears but I cant get any AP shown.

 If I add the module with
 {{{
 # modprobe ath_pci autocreate=monitor ath_debug=1
 # airodump-ng ath0
 }}}

 this works fine and I can get the AP list, but adding a sta vap would fail
 {{{
  # wlanconfig ath1 create nounit wlandev wifi0 wlanmode sta
 wlanconfig: ioctl: Input/output error
 }}}


 The system is gentoo linux on a dual-core amd(x86),  kernel 2.6.18-r1. I
 tried madwifi-ng 0.92 and lastest svn(r1758), same problem.

-- 
Ticket URL: <http://madwifi.org/ticket/972>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets

Reply via email to