#5144 HIGH 8.2.0 (: [firmware] Marvell firmware should have controls for turning mesh forwarding on and off

[Zarro Boogs per Child]

#5144: [firmware] Marvell firmware should  have controls for turning mesh
forwarding on and off
---------------------------+------------------------------------------------
   Reporter:  jg           |       Owner:  jcardona            
       Type:  defect       |      Status:  new                 
   Priority:  high         |   Milestone:  8.2.0 (was Update.2)
  Component:  wireless     |     Version:                      
 Resolution:               |    Keywords:  blocks-:8.2.0       
Next_action:  communicate  |    Verified:  0                   
  Blockedby:               |    Blocking:  7879                
---------------------------+------------------------------------------------

Comment(by mtd):

 Replying to [comment:26 mbletsas]:
 > I don't agree with the requirement that mesh forwarding should default
 to off.

 Is there a way a laptop owner can do this (default to off)?  I have a
 buggy access point and I'd rather not bug it (luckily, the AP survives but
 sends something dodgy causing the ADSL modem + router to reboot[1]) if I
 can avoid it.

 Martin

 1. Just so you know I'm not making this up :) - I've a NetGear and a
 DrayTek Vigor 2600, and this is how the Vigor (adsl) bites the dust after
 the NetGear (:e0:a1) spazzes out:
 Jan  1 00:22:50 217.155.220.158 adsl: PoE <== Protocol:LCP(c021) EchoRep
 Identifier:0x17Magic Number: 0x1764 27 6b ##
 Jan  1 00:23:15 217.155.220.158 adsl: WLAN_DBG - EAPoL_handler, from
 0:17:f2:3f:e0:a1
 Aug 29 00:19:17 cree kernel: eth0: link down.

 Unfortunately a few others have had this type of problem (
 http://forums.whirlpool.net.au/forum-replies-archive.cfm/902842.html ),
 but it only happens for me when the XO is around.

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