Package: ifscheme
Version: 1.7-6
Severity: important
X-Debbugs-Cc: richardle...@fastmail.co.uk

I've used ifscheme happily for a long time and on numerous
computers. Just recently I installed "unstable" from scratch on a Dell
XPS 13 9343. And now ifscheme doesn't work anymore.

This if the configuration I have in /etc/network/interfaces:

  mapping wlp2s0
      script ifscheme-mapping

  iface wlp2s0-home inet dhcp
      wpa-ssid MyWiFi
      wpa-psk MyPSK
      dns-nameservers 208.67.222.222 208.67.220.220

  iface wlp2s0-mobile inet dhcp
      wpa-ssid PhoneWiFi
      wpa-psk PhonePSK

I can verify that ifscheme is parsing my config correctly:

  $ sudo ifscheme --list
  home
  mobile

But when I try to select a network and bring up the interface, I get
the error "unknown interface":

  $ sudo ifscheme home
  Scheme changed to home.
  $ sudo ifup -v wlp2s0
  ifup: running mapping script ifscheme-mapping on wlp2s0
  ifup: ignoring unknown interface wlp2s0=wlp2s0

I know this isn't the correct way to use it, but just in case I also
tried bringing up the interface with the ifscheme suffix:

  $ sudo ifup -v wlp2s0-home
  ifup: configuring interface wlp2s0-home=wlp2s0-home (inet)
  /bin/run-parts --exit-on-error --verbose /etc/network/if-pre-up.d
  run-parts: executing /etc/network/if-pre-up.d/wireless-tools
  run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
  wpa_supplicant: wpa-driver nl80211,wext (default)
  wpa_supplicant: /sbin/wpa_supplicant -s -B -P 
/run/wpa_supplicant.wlp2s0-home.pid -i wlp2s0-home -D nl80211,wext -C 
/run/wpa_supplicant
  Starting /sbin/wpa_supplicant...
  wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
  run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
  ifup: failed to bring up wlp2s0-home

I guess this would happen even if I didn't have the ifscheme mapping
configured; it's effectively assuming that an interface called
literally wlp2s0-home exists.

I'm wondering if this might have something to do with the new(-ish)
"predictable" network interface names. The reason I considered this is
because my old laptop had a WiFi interface called wlan0 under the old
scheme (as well as eth0). That machine was also Debian "unstable" but
was originally installed c.2013 and just continuously upgraded.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8), LANGUAGE=en_GB.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ifscheme depends on:
ii  ifupdown             0.8.36
ii  init-system-helpers  1.60
ii  lsb-base             11.1.0

ifscheme recommends no packages.

ifscheme suggests no packages.

-- no debconf information

Reply via email to