I'm on Xenial and I ran an apt-get update; apt-get dist-upgrade and my
eth0 changed back to enxb827djdk after reboot :(

My biggest issue is virtual interfaces do NOT work with these
"predictable" network names. I can do ifconfig eth0:0 192.168.123.123
but I cannot do ifconfig enxb827djdk:0 192.168.123.123 - it just
overrites the main IP, rather than creating another virtual interface :(

Previously, I was able to follow these steps:

Edit/boot/firmware/config.txt to add:
  net.ifnames=0
  biosdevname=0

Run: ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules

Make sure this file is absent (which it was anyway):
/lib/udev/rules.d/73-usb-net-by-mac.rules

Run: update-initramfs -k all -u

But now, running the above steps no longer works and I'm getting
enxb827djdk again :(

I also checked /proc/cmdline and I have net.ifnames=0 there so it's
definitely being passed. I'm running kernel 4.4.0-1023-raspi2 Sep 6
16:12:44 UTC 2016

Is there a solution/workaround?

-- 
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/1593379

Title:
  systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or
  /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd package in Debian:
  Fix Released

Bug description:
  Description:    Ubuntu 16.04 LTS
  Release:        16.04

  The upgrade to systemd/udev 229-4ubuntu6 breaks net.ifnames=0 for USB
  devices.

  It appears the regression is here:
  * Set MAC based name for USB network interfaces only for universally
      administered (i. e. stable) MACs, not for locally administered (i. e.
      randomly generated) ones. Drop /lib/systemd/network/90-mac-for-usb.link
      (as link files don't currently support globs for MACAddress=) and replace
      with an udev rule in /lib/udev/rules.d/73-special-net-names.rules.
      (Closes: #812575, LP: #1574483)

  As Raspberry Pi's use eth0 via USB, this breaks running systems.

  Before:
  ii  systemd        229-4ubuntu4 armhf        system and service manager
  ii  udev           229-4ubuntu4 armhf        /dev/ and hotplug management daem

  3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP 
mode DEFAULT group default qlen 1000
      link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff

  After:

  ii  systemd                      229-4ubuntu6        armhf               
system and service manager
  ii  udev                         229-4ubuntu6        armhf               
/dev/ and hotplug management daemon

  3: enxb827eb1639e9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc 
pfifo_fast state UP mode DEFAULT group default qlen 1000
      link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff

  cat /proc/cmdline
  dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 
bcm2709.boardrev=0xa01041 bcm2709.serial=0x37b38253 
smsc95xx.macaddr=B8:27:EB:B3:82:53 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=250000000 
vc_mem.mem_base=0x3dc00000 vc_mem.mem_size=0x3f000000  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 
rootfstype=ext4 elevator=deadline rootwait

  With the default interfaces configuration, all networking is lost on
  reboot after upgrade.

  
  SRU TEST CASE
  =============
   * Boot with "net.ifnames=0" on the kernel command line, and connect an USB 
ethernet device. It will still be called enxDEADBEEF with current xenial. With 
the -proposed version it will instead keep the kernel name, like "usb0" as 
intended.

   * Do "sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules"
  (the other documented way to disable ifnames) and do the above
  connect/name check test again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1593379/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to