[Touch-packages] [Bug 1567744] Re: RTNETLINK answers: Numerical result out of range for alias interface from a usb NIC

2016-04-12 Thread Martin Pitt
I actually re-started the discussion about that (about the third time) a few days ago on https://lists.ubuntu.com/archives/ubuntu- devel/2016-April/039302.html . This is actually another point in favor of moving to location based USB names by default. @Andres: For the time being, please see

[Touch-packages] [Bug 1567744] Re: RTNETLINK answers: Numerical result out of range for alias interface from a usb NIC

2016-04-11 Thread Mathieu Trudel-Lapierre
I pinged pitti on IRC earlier today, and just subscribed him for guidance on whether this can be fixed in systemd; which seems to be the least intrusive way to handle this (aside from expecting users to know about this limitation and renaming interfaces themselves). ** Changed in: iproute2

[Touch-packages] [Bug 1567744] Re: RTNETLINK answers: Numerical result out of range for alias interface from a usb NIC

2016-04-11 Thread Mathieu Trudel-Lapierre
This isn't a simple problem at all. The new naming scheme from systemd makes it so that these specific devices (USB dongles) get their MAC address encoded in the device name, which brings it up to a length of 15 characters + \0; so 16 bytes. This happens to also be the size limit for interface

[Touch-packages] [Bug 1567744] Re: RTNETLINK answers: Numerical result out of range for alias interface from a usb NIC

2016-04-11 Thread Mathieu Trudel-Lapierre
ifupdown handles the passed names correctly, but it looks like iproute2 is very unhappy about something in these long names like "enx000be608397d:1"; when setting the label for the address. Since the label must match the device and it otherwise works with "eth1:1", I'll looking into the iproute2

[Touch-packages] [Bug 1567744] Re: RTNETLINK answers: Numerical result out of range for alias interface from a usb NIC

2016-04-11 Thread Mathieu Trudel-Lapierre
Looks like at first glance ifupdown is confused by this naming format together with the subif. I'll try to reproduce here, I do happen to have a USB ethernet dongle that should show this problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages,

[Touch-packages] [Bug 1567744] Re: RTNETLINK answers: Numerical result out of range for alias interface from a usb NIC

2016-04-11 Thread Andres Rodriguez
** Changed in: ifupdown (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1567744 Title: RTNETLINK answers: Numerical result

[Touch-packages] [Bug 1567744] Re: RTNETLINK answers: Numerical result out of range for alias interface from a usb NIC

2016-04-11 Thread Steve Langasek
** Changed in: ifupdown (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1567744 Title:

[Touch-packages] [Bug 1567744] Re: RTNETLINK answers: Numerical result out of range for alias interface from a usb NIC

2016-04-08 Thread Andres Rodriguez
** Description changed: - I have a USB NIC that is connected to my xenial system: + I have a USB NIC that is connected to my denial system. I tried to + create an alias, and after reboot, it wasn't created. When I manually + try to bring it up I have the error. /e/n/i: auto