I don't understand why this is a won't fix bug.
If users pick a long NIC name by themselves, then it's users'
responsibility to fix it. But apparently this is not the case, it's an
unexpected behavior caused by internal conflicts of different linux
components.
--
You received this bug
** Changed in: systemd (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1567744
Title:
USB NICs get too long name for ifupdown
Hi,
we're running into the same problem and wonder whether we could use a
sub-string of the MAC address instead. Does the UDEV library support
something like $env{MAC_ADDR:6}?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Just an update - this problem still exists in Ubuntu 16.04.3 LTS.
In case someone gets to this page due to this problem, there is a
workaround. Downside on this workaround is, that all network interface
names are then changed to eth0, eth1, eth2 etc, so one must change
settings on the
Moving to "ubuntu-17.05" (in other words, "just past zesty release"). I
think this still needs to be addressed and I'm sorry it hasn't been
fixed yet. I'll revive the discussion on this subject and look at the
already proposed solutions.
Seems like we don't need vastly new technology to properly
Good that we have a workaround - "net.ifnames=0 biosdevname=0". Still, I
think we need to reevaluate the importance level of "medium" - this is
toxic.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Milestoning, since we should try to not drop the ball on this bug; I
will need to revisit the mailing list thread and how exactly we do the
naming for these devices.
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: systemd (Ubuntu)
I just lost 3 days to this issue before I realized what was happening. I
realize this is an edge case, and understand the issues with fixing
this, but at least some type of better error messages would have helped
prevent that waste of time.
I was trying to setup a host to run docker with macvlan
This feature worked well in my earlier installation (16.04LTS), but when
I re-installed the system yesterday, adding an alias to my USB network
adapter didn't work any more.
---8<---8<---
$ sudo ifup enx0016:0
RTNETLINK answers: Numerical result out of range
Failed to bring up
9 matches
Mail list logo
