#9895 NORM 1.5-sof: Should we inhibit suspend when we're connected to an ad-hoc network?

[Zarro Boogs per Child]

#9895: Should we inhibit suspend when we're connected to an ad-hoc network?
----------------------------------------------+-----------------------------
           Reporter:  cjb                     |       Owner:  pgf                              
               Type:  defect                  |      Status:  new                              
           Priority:  normal                  |   Milestone:  1.5-software-later               
          Component:  power manager (powerd)  |     Version:  Development build as of this date
         Resolution:                          |    Keywords:                                   
        Next_action:  review                  |    Verified:  0                                
Deployment_affected:                          |   Blockedby:                                   
           Blocking:                          |  
----------------------------------------------+-----------------------------

Comment(by pgf):

 Replying to [comment:5 Quozl]:
 > Test results in #9896 are relevant to this ticket description ...
 joining an ad-hoc network with one existing node is not possible if that
 node is suspended.  Once the network is larger than one node, joining
 works.

 what do you mean by "join"?  i would have thought it was possible to join
 an ad-hoc network with no existing nodes whatever, which is the same as
 other members being suspended, no?  perhaps you're referring to a higher-
 level join.

 >
 > Once a multi-node ad-hoc network is active, collaboration does continue.
 Test results in #9535 showed ''it only takes two link-local Chat instances
 to be awake for each chat line to survive into the transcript of all
 participants.''
 >
 > So my vote is to inhibit suspend when we are recently connected to an
 ad-hoc network with no other peers in the arp table.

 details on how one might detect such a scenario would be most welcome.
 (is looking at iwconfig output enough to detect "connected"?  how might i
 list my ad-hoc peers, in order to detect that some aren't in the arp
 table?

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