On Mi, 03 iul 19, 18:22:30, Michael Biebl wrote: > > Usually ethernet interfaces are name eth* and wifi interfaces are named > wlan*, so yeah, if you have a single ethernet interface which is named > eth0 and a single wifi interface that is named wlan0, then you are safe > as well. I do vaguely remember seeing wifi interfaces named as eth* > though. I've seen this a long time ago, not sure if this is still valid > today and you can safely say nowadays that wifi interfaces are always > called wlan*.
Here is a confirmed report of a wireless that is named ethX by the kernel. https://lists.debian.org/debian-user/2019/07/msg00610.html (I received full dmesg off list if someone is interested) To be on the safe side the entry could be adjusted as per this patch (also attached for convenience): diff --git a/en/issues.dbk b/en/issues.dbk index 7b46d168..3b463f2d 100644 --- a/en/issues.dbk +++ b/en/issues.dbk @@ -153,7 +153,10 @@ information mentioned in <xref linkend="morereading"/>. file (see <ulink url="&url-man;systemd.link"> systemd.link(5)</ulink>). The <literal>net.ifnames=0</literal> kernel commandline option might - also work for systems with only one network interface (of a given type). + also work for systems with only one network interface<footnote><para> + It should also work for systems with interfaces of different types (e.g. + Ethernet and wireless) as the kernel it typically using different + different naming conventions for them (i.e. eth0 and wlan0).</para></footnote>. </para> <para> To find the new-style names that will be used, first find the Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
diff --git a/en/issues.dbk b/en/issues.dbk
index 7b46d168..3b463f2d 100644
--- a/en/issues.dbk
+++ b/en/issues.dbk
@@ -153,7 +153,10 @@ information mentioned in <xref linkend="morereading"/>.
file (see <ulink url="&url-man;systemd.link">
systemd.link(5)</ulink>).
The <literal>net.ifnames=0</literal> kernel commandline option might
- also work for systems with only one network interface (of a given type).
+ also work for systems with only one network interface<footnote><para>
+ It should also work for systems with interfaces of different types (e.g.
+ Ethernet and wireless) as the kernel it typically using different
+ different naming conventions for them (i.e. eth0 and wlan0).</para></footnote>.
</para>
<para>
To find the new-style names that will be used, first find the
signature.asc
Description: PGP signature
