[Bug 1567744] Re: USB NICs get too long name for ifupdown aliases or bridge names
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567744 Title: USB NICs get too long name for ifupdown aliases or bridge names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567744] Re: USB NICs get too long name for ifupdown aliases or bridge names
** Changed in: systemd (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567744 Title: USB NICs get too long name for ifupdown aliases or bridge names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567744] Re: USB NICs get too long name for ifupdown aliases or bridge names
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567744 Title: USB NICs get too long name for ifupdown aliases or bridge names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567744] Re: USB NICs get too long name for ifupdown aliases or bridge names
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 /etc/network/interfaces -file so, that they work also after this change. Steps: 1) Update /etc/default/grub as follows: GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0" 2) Update GRUB: sudo update-grub 3) If necessary, modify /etc/network/interfaces, specially if you have static IP addresses 4) Reboot the computer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567744 Title: USB NICs get too long name for ifupdown aliases or bridge names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567744] Re: USB NICs get too long name for ifupdown aliases or bridge names
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 handle VLANs, bridges, aliases at least in the typical situations; especially given that there *are* workarounds. ** Changed in: systemd (Ubuntu) Milestone: ubuntu-17.03 => ubuntu-17.05 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567744 Title: USB NICs get too long name for ifupdown aliases or bridge names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567744] Re: USB NICs get too long name for ifupdown aliases or bridge names
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567744 Title: USB NICs get too long name for ifupdown aliases or bridge names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567744] Re: USB NICs get too long name for ifupdown aliases or bridge names
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) Milestone: None => ubuntu-17.03 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567744 Title: USB NICs get too long name for ifupdown aliases or bridge names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567744] Re: USB NICs get too long name for ifupdown aliases or bridge names
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 networks mapped to vlan interfaces on a pair of USB ethernet adapters connected to a BRIX used for testing. Couldn't get a bond on the pair to work, couldn't figure out why, then tried for just VLAN interfaces, and that didn't work either. Thought I was losing it, didn't seem that hard. Not sure how I figured it out, but realized if I switched back to using eth1, eth2 for the USB ethernet devices, using "net.ifnames=0 biosdevname=0" boot options + old-style mac-address rules to map, I could get everything to work. But, wasn't happy with the workaround, as I'd prefer to use the new predictable names. I like the idea of using last 6 digits of Mac address. I thought of doing this: sudo ln -s /dev/null /etc/udev/rules.d/73-usb-net-by-mac.rules to go back to slot names, but if I plug into different ports, names change, so no. Perhaps some different prefix other than enx to avoid confusion, usb123456 anyone? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567744 Title: USB NICs get too long name for ifupdown aliases or bridge names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567744] Re: USB NICs get too long name for ifupdown aliases or bridge names
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 enx0016:0. ---8<---8<--- The earlier installation was made using Xubuntu 16.04 installation media and this time I installed the system using Ubuntu 16.04.01 mini iso media, if this makes any difference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567744 Title: USB NICs get too long name for ifupdown aliases or bridge names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567744] Re: USB NICs get too long name for ifupdown aliases
Maybe, but that will affect all nics in all nodes. ** Summary changed: - USB NICs get too long name for ifupdown aliases + USB NICs get too long name for ifupdown aliases or bridge names -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567744 Title: USB NICs get too long name for ifupdown aliases or bridge names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567744] Re: USB NICs get too long name for ifupdown aliases
Doesn't adding "net.ifnames=0 biosdevname=0" to your kernel boot line fix this for you? It will stop udev from creating the longer-than- desired names. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567744 Title: USB NICs get too long name for ifupdown aliases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567744] Re: USB NICs get too long name for ifupdown aliases
@andres that's a cool feature, btw :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567744 Title: USB NICs get too long name for ifupdown aliases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567744] Re: USB NICs get too long name for ifupdown aliases
I renamed the NIC in the MAAS node page to enx0 to workaround this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567744 Title: USB NICs get too long name for ifupdown aliases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567744] Re: USB NICs get too long name for ifupdown aliases
I just hit this deploying a MAAS2 xenial node that has a usb nic: # ifup br-enx0023552c6029 Waiting for br-enx0023552c6029 to get ready (MAXWAIT is 76 seconds). RTNETLINK answers: Numerical result out of range Failed to bring up br-enx0023552c6029. It went far enough to create the bridge, but with a truncated name and no IP: # brctl show (...) br-enx0023552c6 8000.0023552c6029 no enx0023552c6029 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567744 Title: USB NICs get too long name for ifupdown aliases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567744] Re: USB NICs get too long name for ifupdown aliases
Additionally, Juju creates bridges on top of both physical and VLAN interfaces to allow for the same level of addressability for containers as regular machines. The bridges currently use the "br-" prefix and the underlying device name, which if it happens to be "enxxaabbccddeef0.1234" already, obviously won't work. So the length limit on interface names can be even lower than what Mike suggested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567744 Title: USB NICs get too long name for ifupdown aliases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567744] Re: USB NICs get too long name for ifupdown aliases
This is also an issue for VLAN interfaces. To support VLANs, 10 characters should be the max. (16 - 1 [for \0], -1 [.], -4 [vid]) Throw in VLANs plus aliases, and, well, I guess we ought to use shorter names, such as (I don't know) "eth0". ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567744 Title: USB NICs get too long name for ifupdown aliases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567744] Re: USB NICs get too long name for ifupdown aliases
Indeed it's not iproute's fault, it's just an unforseen consequence of using a long string like a MAC to name the device. Perhaps reducing it by half and using just the second half of the MAC might be good? The chance of collisions would remain pretty low. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567744 Title: USB NICs get too long name for ifupdown aliases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567744] Re: USB NICs get too long name for ifupdown aliases
This isn't iproute's fault IMHO. There hasn't been much response to the thread so far, and it's getting tight. Reassigning to udev as that's where USB NIC names are set. ** Summary changed: - RTNETLINK answers: Numerical result out of range for alias interface from a usb NIC + USB NICs get too long name for ifupdown aliases ** Package changed: iproute2 (Ubuntu) => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Importance: Critical => Medium ** Changed in: systemd (Ubuntu) Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned) ** Changed in: systemd (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567744 Title: USB NICs get too long name for ifupdown aliases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs