msh0 and haldaemon.

Chris Ball cjb at
Thu Aug 21 19:22:31 EDT 2008

Dear libertas-dev people,

We're seeing an OLPC bug with the following characteristics:

When haldaemon and NM start up, they notice and manage eth0 and msh0.
When the 8388 device goes away (due to purposefully powering it down
and then up again) haldaemon only notices eth0 returning, and so NM
claims msh0 doesn't exist at that point and won't manage it.

So, wherever the problem is here, it's at or below haldaemon.  Maybe
there's something that we do to announce eth0 in the kernel on connect
that we aren't doing for msh0?

Here's an lshal --monitor session:

bash-3.2# lshal --monitor &
Start monitoring devicelist:

bash-3.2# echo 0 > /sys/power/wlan-enabled 
23:14:25.387: usb_device_1286_2001_noserial_if0 removed
23:14:27.478: net_00_17_c4_10_c4_da removed
23:14:27.500: net_00_17_c4_10_c4_da_0 removed
23:14:27.505: usb_device_1286_2001_noserial removed

bash-3.2# echo 1 > /sys/power/wlan-enabled
23:14:40.162: usb_device_1286_2001_noserial added
23:14:40.435: usb_device_ffffffff_ffffffff_noserial added
23:14:41.452: net_00_17_c4_10_c4_da added

bash-3.2# ifconfig msh0
msh0      Link encap:Ethernet  HWaddr 00:17:C4:10:C4:DA  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:51 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2856 (2.7 KiB)  TX bytes:308 (308.0 b)

bash-3.2# lshal | grep eth0
  linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:0f.4/usb1/1-1/net/eth0'
  net.interface = 'eth0'  (string)
bash-3.2# lshal | grep msh0

Any ideas?  Thanks!  (This is OLPC

- Chris.
Chris Ball   <cjb at>

More information about the libertas-dev mailing list