Bug#881771: release-notes: No mention of "predictable network interface names" in Debian 10
Justin B Rye wrote:
>>> In issues.dbk:
>>>
>>> <section id="migrate-interface-names">
>>> <title>Migrating from legacy network interface names</title>
>>> <para>
[...]
>>>
>>> Then in upgrading.dbk
>>>
>>> <section id="review-interface-names">
>>> <title>Verify network interface name support</title>
>>> <para>
[...]
I wasn't sure exactly where in upgrading.dbk to add it, but here's a
suggested patch.
Meanwhile I notice a new grammar nitpick in issues.dbk: "to login"
should be "to log in" (just as with "backup", "setup", and so on, the
noun is a single word, but the verb is two words that can be separated
in phrases like "log yourself straight back in".).
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
diff --git a/en/issues.dbk b/en/issues.dbk
index 3ef1d90e..ce2ed284 100644
--- a/en/issues.dbk
+++ b/en/issues.dbk
@@ -93,6 +93,79 @@ information mentioned in <xref linkend="morereading"/>.
</para>
</section>
+ <section id="migrate-interface-names">
+ <!-- (jessie to) stretch to buster -->
+ <title>Migrating from legacy network interface names</title>
+ <para>
+ If your system was upgraded from an earlier release, and still uses
+ the old-style network interface names that were deprecated with
+ stretch (such as <literal>eth0</literal> or <literal>wlan</literal>),
+ you should be aware that <systemitem role="package">udev</systemitem>
+ in buster no longer supports the mechanism of defining their names via
+ <filename>/etc/udev/rules.d/70-persistent-net.rules</filename>. To
+ avoid the danger of your machine losing networking after the upgrade
+ to buster, it is recommended that you migrate in advance to the new
+ naming scheme (usually meaning names like <literal>enp0s1</literal> or
+ <literal>wlp2s5</literal>, which incorporate PCI bus- and
+ slot-numbers). Take care to update any interface names hard-coded in
+ configuration for firewalls, <systemitem role="package">ifupdown</systemitem>.
+ and so on.
+ </para>
+ <para>
+ The alternative is to switch to a supported mechanism for enforcing
+ the old naming scheme, such as the <literal>net.ifname=0</literal>
+ kernel commandline option or a systemd <filename>.link</filename>
+ file (see <ulink
+ url="https://manpages.debian.org/systemd.link";>systemd.link(5)</ulink>).
+ </para>
+ <para>
+ To find the new-style names that will be used, first find the
+ current names of the relevant interfaces:
+ </para>
+ <screen
+ $ echo /sys/class/net/[ew]*
+ </screen>
+ <para>
+ For each one, check whether it is used in configuration files:
+ </para>
+ <screen>
+ $ sudo rgrep -w eth0 /etc
+ </screen>
+ <para>
+ And what name <systemitem role="package">udev</systemitem> would prefer to
+ use for it:
+ </para>
+ <screen>
+ $ udevadm test-builtin net_id /sys/class/net/eth0 2>/dev/null
+ </screen>
+ <para>
+ (One of these may be a fallback MAC-based name, sometimes needed
+ for USB network hardware.)
+ </para>
+ <para>
+ To switch over, disable <filename>70-persistent-net.rules</filename>
+ either by renaming it or by commenting out individual lines.
+ On virtual machines you will need to remove the files
+ <filename>/etc/systemd/network/99-default.link</filename> and
+ (if using virtio network devices)
+ <filename>/etc/systemd/network/50-virtio-kernel-names.link</filename>.
+ Then rebuild the <filename>initrd</filename>:
+ </para>
+ <screen>
+ $ sudo update-initramfs -u
+ </screen>
+ <para>
+ and reboot. Your system should now have new-style network interface
+ names. Adjust any remaining configuration files, and test your system.
+ </para>
+ <para>
+ See the
+ <ulink url="https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/";>upstream
+ documentation</link> and the <literal>udev</literal>
+ <filename>README.Debian</file> for further information.
+ </para>
+ </section>
+
<section id="noteworthy-obsolete-packages" condition="fixme">
<title>Noteworthy obsolete packages</title>
<para>
diff --git a/en/upgrading.dbk b/en/upgrading.dbk
index 58561d64..4c6386d3 100644
--- a/en/upgrading.dbk
+++ b/en/upgrading.dbk
@@ -241,6 +241,17 @@
</section>
+ <section id="review-interface-names">
+ <!-- (jessie to) stretch to buster-->
+ <title>Verify network interface name support</title>
+ <para>
+ Systems upgraded from older releases that still use network interfaces
+ with names like <literal>eth0</literal> or <literal>wlan0</literal> are
+ at risk of losing networking once they switch to buster; see
+ <xref linkend="migrate-interface-names"/> for migration instructions.
+ </para>
+ </section>
+
</section>
<section id="system-status">
diff --git a/en/issues.dbk b/en/issues.dbk
index 3ef1d90e..a4871f98 100644
--- a/en/issues.dbk
+++ b/en/issues.dbk
@@ -67,7 +67,7 @@ information mentioned in <xref linkend="morereading"/>.
<filename>/etc/default/nis</filename> does not include
<literal>-no-dbus</literal>. With <literal>-no-dbus</literal> present,
<command>ypbind</command> will fail to start, and you may not be able to
- login. For more info see bug <ulink url="&url-bts;906436">bug
+ log in. For more info see bug <ulink url="&url-bts;906436">bug
#906436</ulink>.
</para>
</section>
Reply to: