#572: madwifi-ng mode changes modification (iwpriv XX mode YY) and (iwconfig XX
channel YY) / (iwconfig XX freq YY)
----------------------------------+-----------------------------------------
      Reporter:  dyqith           |       Owner:  dyqith                        
                     
          Type:  defect           |      Status:  assigned                      
                     
      Priority:  major            |   Milestone:  version 0.9.x - progressive 
release candidate phase
     Component:  madwifi: driver  |     Version:  trunk                         
                     
    Resolution:                   |    Keywords:  mode channel freq             
                     
Patch_attached:  0                |  
----------------------------------+-----------------------------------------
Comment (by dyqith):

 New comment (relating to ticket:275, ticket:228):
 (abg) mode changes, channel changes and scanning are all inter-related.

 Classifying information by VAP operation:
  STA/managed::
    An STA has no concept of a fixed channel when its not assoc/auth
 because of its SCAN_STATE.
    In the SCAN_STATE, the STA jumps from channel to channel (channels set
 by athchans)

    What everyone was hoping for was this (i think): When we put "iwconfig
 ath0 channel 10", the sta will stop jumping channels, and stick with the
 one given (correct ?)

   Another thing is the way scanning is not getting cancelled when another
 call is coming in. Cancelling the scan may not be appropriate (i.e. One
 program asks for a scan, another asks for a scan afterwards, should the
 second cancel the firsts scan ? I would think not)

  AP/master::
    Changing channel/mode is fine (except when channel is set to something
 other than 0 and then mode can't be changed from a to b/g).
    Scanning is not supported by AP (even though a wlan_scan_ap is present)

  monitor/wds::
    Channel/mode changes are not happening because these are not AP nor
 STA. They do not call create_ibss() or jump channels when SCANNING. These
 do not have a SCANNING state (gets put into RUN). To help put them into a
 correct channel/mode, new code must be placed to force them as such
 (ticket:612), but must also force all VAPs to change like any other code.

  adhoc/ahdemo::
    Haven't looked into it, someone want to provide something for it ?

-- 
Ticket URL: <http://madwifi.org/ticket/572>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity

Reply via email to