#4665 HIGH Update.: Should we turn off mesh beacons now?

[Zarro Boogs per Child]

#4665: Should we turn off mesh beacons now?
-----------------------+----------------------------------------------------
  Reporter:  cjb       |       Owner:  dilinger
      Type:  defect    |      Status:  new     
  Priority:  high      |   Milestone:  Update.1
 Component:  wireless  |     Version:          
Resolution:            |    Keywords:          
  Verified:  0         |  
-----------------------+----------------------------------------------------

Comment(by dilinger):

 Replying to [comment:3 cjb]:
 > There's a private ioctl.  From #2750:
 >
 > {{{
 > iwpriv ethX bcn_control 1 $INTERVAL
 >
 > $INTERVAL in ms (20 to 1000)
 > }}}
 >
 > With a 20<ms<1000 interface, we can only go as slow as 1Hz.  Does anyone
 know why?

 Thanks.  Looks like that's BCN_CTRL, which is handled by
 libertas_bcn_ioctl.

 That function has the following:
 {{{
                 data[0] = adapter->beacon_enable;
                 data[1] = adapter->beacon_period;
 }}}

 I'm assuming if we were to do 'iwpriv ethX bcn_control 0 $INTERVAL', that
 would disable beacons altogether?

 The minimum (and maximum) beacon periods are hardcoded in the driver:

 {{{
 #define MRVDRV_MIN_BEACON_INTERVAL              20
 #define MRVDRV_MAX_BEACON_INTERVAL              1000
 #define MRVDRV_BEACON_INTERVAL                  100
 }}}

 I could try setting MAX_BEACON_INTERVAL higher and see what explodes...

-- 
Ticket URL: <http://dev.laptop.org/ticket/4665#comment:4>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system