Re: avahi might show confusing IP-addresses for the XOs it reports
On Sun, 2010-10-17 at 08:37 -0500, Mikus Grinbergs wrote: > XO-1 os852 (with updated olpc-powerd) > > DISCLAIMER: This is FYI - I'm sharing my experiences > > While troubleshooting a problem I have on os852 xo1 (interface eth0 > disappears), You're probably seeing this bug: After a very long chase, we fixed it for good in Dextrose by disabling mesh support: http://dev.laptop.org/ticket/10195 Besides this particular bug, we could never get the mesh to work reliably on the XO-1, and at this point I don't believe it will ever happen. The ad-hoc mode covers 99% of the real-world use-cases for the mesh, using a mature, standard protocol. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
avahi might show confusing IP-addresses for the XOs it reports
XO-1 os852 (with updated olpc-powerd) DISCLAIMER: This is FYI - I'm sharing my experiences While troubleshooting a problem I have on os852 xo1 (interface eth0 disappears), I saw strange output from 'olpc-xos -avahi' on a system where eth0 worked (I was using this other system for eth0 comparison): > 0 [~]$ olpc-xos -avahi > Time : 06:44:24 > > 06f4a...@lauva 192.168.1.27Lauva-8 > 55c4a...@purvs fe80::210:60ff:fe15:41dcPurvs-1 > 2733b...@uguns 192.168.1.16Uguns-1 > 11276...@zemes 169.254.9.44Zemes-1 > 11276...@zemes 192.168.1.18Zemes-1 > 0 [~]$ The listing for Zemes (taken on Zemes) is slightly confusing - there are two entries. The one (192...) is for its wired ethernet connection, and the other (169...) is for the automatically-started mesh connection. Does OLPC expect an XO to have only one IP-address ? The listing for Purvs is the one I think is inappropriate. Apparently, Purvs at this time did not have its ethernet software (IPv4) address set - so its ethernet-hardware-derived (IPv6) address got shown. [I do __NOT__ use IPv6 addresses to communicate between XOs.] A little later, Purvs had set up its IPv4 ethernet address (I forget - was that manual, or automatic ?) - now repeating 'olpc-xos -avahi' at Zemes resulted in the appropriate (192...) address for Purvs being reported. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
