#6448 NORM 9.1.0: Local Link and access point sharing issue.

[Zarro Boogs per Child]

#6448: Local Link and access point sharing issue.
-------------------------------+--------------------------------------------
   Reporter:  jg               |       Owner:  Collabora
       Type:  defect           |      Status:  new      
   Priority:  normal           |   Milestone:  9.1.0    
  Component:  telepathy-salut  |     Version:           
 Resolution:                   |    Keywords:           
Next_action:  never set        |    Verified:  0        
  Blockedby:                   |    Blocking:           
-------------------------------+--------------------------------------------

Comment(by gdesmott):

 The problem is that when you are connected to an AP you have two
 interfaces up:

 * eth0: which has an IP from the AP

 * msh0: wich has an auto-ip on the mesh.

 Avahi will announce all the services on both interfaces; including the
 presence and OLPC activity. But the underlying activity protocol can only
 communicate using *one* interface (usually eth0 as that's the default one
 in the routing table).

 So, if an XO is only connected to the mesh, I'll see the activity but
 won't be able to collaborate with it.

 Question is: do we really want to have the msh0 interface up when we are
 connected to an AP? What's the rational of this choice?

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