xo-1 os300 -- switch off mesh?

Mikus Grinbergs mikus at bga.com
Tue Jul 13 08:11:01 EDT 2010

> Is there a way to tweak the os300 build so that it brings up the
> Libertas device just as eth0

I presume you are asking about installing a distribution which embodies
that definition - I myself do not understand how to modify the "build
process".  But if the question refers only to "hacking" an existing
build for someone's use - my answer is 'yes':

 *  File /etc/udev/rules.d/70-persistent-net.rules lists the names
assigned to the device interfaces.  [These names appear to be assigned
in the order in which the respective devices were presented to the
system -- I ran into this problem in 2008, with my no-wireless setup.
Randomly a new build would initialize itself with my ethernet on eth0
(instead of on eth1) -- but there was code in the system which assumed
the XO's radio HAD TO BE at eth0.  Plus I found that if I had been using
an external ethernet adapter with a particular XO, but then plugged in a
different adapter -- that connection got assigned the next name (e.g.,
eth2).  Nowadays I always check this file to verify name assignments -
and manually edit names if they're not what my procedures expect.]

  *  And names are merely "parameters" specifiable on whatever command
causes that "device interface" to be created.  For instance, 'wlan_'
gets assigned by command 'iw interface add' (or equivalent).

> (and doesn't enable the 802.11s features in the firmware)?

I'm not familiar with the various "methods" implemented in the software.
 But (for "hacking" an existing build) there might well exist a
'service' (reachable via DBUS) which disables the XO's 802.11s feature.


More information about the Devel mailing list