#8387 NORM Not Tri: no static addresses for wireless

[Zarro Boogs per Child]

#8387: no static addresses for wireless
-------------------------------+--------------------------------------------
   Reporter:  pgf              |       Owner:  dcbw         
       Type:  defect           |      Status:  new          
   Priority:  normal           |   Milestone:  Not Triaged  
  Component:  network manager  |     Version:  not specified
 Resolution:                   |    Keywords:               
Next_action:  diagnose         |    Verified:  0            
  Blockedby:                   |    Blocking:               
-------------------------------+--------------------------------------------

Comment(by mikus):

 Replying to [comment:2 mstone]:
 > Why is it "not possible"? I believe it works fine without NM (and
 probably would work fine if I knew how to configure NM to work with
 statically assigned addresses.)
 [[BR]]YES.  YES.  YES.

 I can't count the number of hours I've spent struggling with my XO, just
 because the NM wanted to do something I knew wouldn't work, and in the
 process screwed up something I knew *would* work.

 If there is a simple way to tell NM "go to sleep, and DON'T wake up" -- I
 would like to know how to do that.

 [My biggest problem appears to be a "link" between NM and "device
 definitions".  I can brute-force stop NM - but then in practice I seem to
 end up with an error message 'Device not found' when I try to manually
 start up something.]

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