#8947 HIGH Not Tri: olpc-xos command doesn't show correct value

[Zarro Boogs per Child]

#8947: olpc-xos command doesn't show correct value
----------------------------------------+-----------------------------------
           Reporter:  joe               |       Owner:  Collabora    
               Type:  defect            |      Status:  new          
           Priority:  high              |   Milestone:  Not Triaged  
          Component:  presence-service  |     Version:  not specified
         Resolution:                    |    Keywords:               
        Next_action:  never set         |    Verified:  0            
Deployment_affected:                    |   Blockedby:               
           Blocking:                    |  
----------------------------------------+-----------------------------------
Changes (by garycmartin):

 * cc: garycmartin (added)


Comment:

 This may be related to the bug I reported before regarding the Mesh
 interface still being active and chatting while associated to an AP. I
 didn't know about the olpc-xos command, but when I run it on the 3 XOs
 here (all 8.2-767 and associated to my AP), I get these results:

 {{{
 [olpc at xo-10-B0-DA ~]$ olpc-xos
 Time   : 17:14:23
 Total  : 4
 169.254.2.73     garycmartin (blue-yellow)
 169.254.9.3      garycmartin (cyan-red)
 192.168.1.5      garycmartin (red-green)
 --> TOTAL: 3
 }}}

 {{{
 [olpc at xo-05-24-02 ~]$ olpc-xos
 Time   : 17:34:01
 Total  : 4
 192.168.1.4      garycmartin (blue-yellow)
 169.254.9.3      garycmartin (cyan-red)
 169.254.8.210    garycmartin (red-green)
 --> TOTAL: 3
 }}}

 {{{
 [olpc at xo-0C-E6-BB ~]$ olpc-xos
 Time   : 17:34:35
 Total  : 4
 169.254.2.73     garycmartin (blue-yellow)
 192.168.1.6      garycmartin (cyan-red)
 169.254.8.210    garycmartin (red-green)
 --> TOTAL: 3
 }}}

 Note the IP addresses... My AP subnet is the 192.168.1.x range, yet a lot
 of the addresses reported by olpc-xos are the 169.254.x.x mesh. If this is
 also the network information activities are using ti try and open
 collaborative sessions, I can see a lot of potential for activity sharing
 bugs.

 Looking at the IP address pattern a little closer, it looks like olpc-xos
 is showing the eth0 IP address for its self, and the msh0 IP address for
 any remote machines.

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