Comment 11 for bug 1467640

Here are my observations running image #237 ( devel-proposed/ubuntu ) on mako.

First, as Alfonso pointed out in comment #6, there are some new devices that appear when running wily vs. vivid.

Here's a diff of the output of 'ip addr' on rc vs. devel-proposed:

 espy@shrike:% diff mako-vivid-ip-devices.out mako-wily-ip-devices.out
24,27c24,28
< 24: rmnet_usb0: <> mtu 2000 qdisc noop state DOWN group default qlen 1000
< 25: rmnet_usb1: <> mtu 2000 qdisc noop state DOWN group default qlen 1000
< 26: rmnet_usb2: <> mtu 2000 qdisc noop state DOWN group default qlen 1000
< 27: rmnet_usb3: <> mtu 2000 qdisc noop state DOWN group default qlen 1000
---
> 24: enx0af53fef2539: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 2000 qdisc pfifo_fast state UNKNOWN group default qlen 1000
> 25: enxda4f6c1d2a6d: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 2000 qdisc pfifo_fast state UNKNOWN group default qlen 1000
> 26: enxea43c82d167a: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 2000 qdisc pfifo_fast state UNKNOWN group default qlen 1000
> 27: enx66b76e767656: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 2000 qdisc pfifo_fast state UNKNOWN group default qlen 1000

Turns out this is due to the recent landing in wily of "stateless persistant network interface names", by Martin Pitt. See:

https://lists.ubuntu.com/archives/ubuntu-devel/2015-June/038786.html

As these devices are owned by rild, we need to investigate how to exclude these devices from being re-named. Also our current version of NetworkManager uses hard-coded paths in NMManager to ignore these devices, we need to prevent the re-name for the time-being. Note, we also need to come up with a more generic mechanism to keep network-manager from touching rild-owned devices.