After a quick test, with the olpc 802 build and all the newer ones (including dextrose), I saw that only on the 802 build, Network Manager starts autoip after the dhcpclient has given up. <br><br>Researching on the web, I found this [1]. Basically autoip was causing confusion when making the users to believe that the ethernet connection was _always_ successful. <br>
<br>So I asked Dan Williams and he told me they disabled it by default (since NM 0.7.0). Apparently the only (easy) way to make this work is to create a custom wired setting from _some_ UI...<br><br>1) <a href="http://www.mail-archive.com/networkmanager-list@gnome.org/msg04835.html">http://www.mail-archive.com/networkmanager-list@gnome.org/msg04835.html</a><br>
<br>Saludos,<br><br><div class="gmail_quote">On Sun, Dec 26, 2010 at 11:48 PM, Mikus Grinbergs <span dir="ltr"><<a href="mailto:mikus@bga.com">mikus@bga.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Kevin, here is how my XOs communicate:<br>
<br>
1) I haven't seen any reason to ever go to Gnome -- instead I've<br>
written several scripts which I run from Terminal, and which set up<br>
communication between XOs (when it hasn't been setup automatically).<br>
<br>
2) Much of my inter-XO communication has been using (NON-adhoc) mesh.<br>
[I've written scripts to turn (non-adhoc) mesh on/off, and scripts to<br>
turn ad-hoc wireless on/off.]<br>
<br>
Until very recently, I have __NOT__ tried Associating to the same<br>
Access Point in order to communicate between XOs. When my trial network<br>
has included an XO-1.5 (which does not currently support plain mesh),<br>
I've been able to use the ad-hoc (XO initiated) network instead of a<br>
plain mash network in order to communicate between my test XOs.<br>
<br>
3) So far, all of my internet connections have gone through a local<br>
ethernet LAN.<br>
<br>
[Note: in the XO, which 'eth_' gets assigned to the ethernet seems<br>
to be somewhat hit or miss. If, when installing a new build, the<br>
"wrong" name gets assigned -- I edit<br>
/etc/udev/rules.d/70-persistent-net.rules and correct the name to what I<br>
want.]<br>
<br>
[Note: once in a while an XO would fail to communicate with the<br>
ethernet. My bypass has always been to unplug the ethernet cable from<br>
the XO, wait some seconds, then plug the cable back in. Usually,<br>
Network Manager recognizes "communications interface became present" --<br>
and sets up the software for properly accessing that interface.]<br>
<br>
3a) When I was using F7-based or F9-based XO builds, my local ethernet<br>
LAN had a DHCP server on it -- that DHCP server dynamically assigned<br>
IPv4 addresses to the XOs plugged in to that LAN. I __NEVER__ recall<br>
having a problem communicating between XOs via the ethernet (though very<br>
few Activities were able to collaborate).<br>
<br>
3b) About the time I started using F11-based XO builds, the hardware<br>
system housing my DHCP server gave out. I've been too lazy to set up a<br>
new DHCP server -- so for the last year I've been running without one on<br>
my ethernet LAN. I have defined static IPv4 addresses for the desktop<br>
systems on the ethernet LAN. The XO (e.g., via the Sugar control panel)<br>
does not support assigning an XO a static IPv4 address -- so I've<br>
written a script with which I do that. [I have to run that script every<br>
time I restart the session, or replug the ethernet cable.]<br>
<br>
[Note: Network Manager (or Avahi?) periodically overrides the<br>
static IPv4 address I assign. This happens infrequently enough that I<br>
simply re-run my script.]<br>
<br>
----<br>
<div class="im"><br>
> collaboration does not seem to work without the route commands<br>
<br>
</div>I have not yet figured out when specifying a "default route" is<br>
absolutely necessary. I've noticed that "multi-cast" seems used for<br>
collaboration -- so I make sure to run yet another script which issues<br>
(using a functioning interface) 'ip route add <a href="http://224.0.0.0/4" target="_blank">224.0.0.0/4</a>'.<br>
<font color="#888888"><br>
<br>
mikus<br>
</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@lists.laptop.org">Devel@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/devel" target="_blank">http://lists.laptop.org/listinfo/devel</a><br>
</div></div></blockquote></div><br>