<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="https://dev1galaxy.org/extern.php?action=feed&amp;tid=4692&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / [Raspberry Pi 400] Why is wifi interface named wlan1 on the Pi400?]]></title>
		<link>https://dev1galaxy.org/viewtopic.php?id=4692</link>
		<description><![CDATA[The most recent posts in [Raspberry Pi 400] Why is wifi interface named wlan1 on the Pi400?.]]></description>
		<lastBuildDate>Thu, 25 Nov 2021 23:41:09 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: [Raspberry Pi 400] Why is wifi interface named wlan1 on the Pi400?]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=32997#p32997</link>
			<description><![CDATA[<p>Well if you were using systemd you could just add net.ifnames=0 to the cmdline. But as this isn&#039;t an option on Devuan, you would need to play around with the udev rules.</p><div class="codebox"><pre><code>sudo tee /etc/udev/rules.d/80-net-setup-link.rules &lt;&lt;EOF

SUBSYSTEM!=&quot;net&quot;, GOTO=&quot;net_setup_link_end&quot;

IMPORT{builtin}=&quot;path_id&quot;

ACTION!=&quot;add&quot;, GOTO=&quot;net_setup_link_end&quot;

# IMPORT{builtin}=&quot;net_setup_link&quot;

NAME==&quot;&quot;, ENV{ID_NET_NAME}!=&quot;&quot;, NAME=&quot;wlan0&quot;

LABEL=&quot;net_setup_link_end&quot;
EOF</code></pre></div><p>I use a rule like this to insure the ethernet interface comes up as eth0 on Pi3&#039;s.</p>]]></description>
			<author><![CDATA[dummy@example.com (c0rnelius)]]></author>
			<pubDate>Thu, 25 Nov 2021 23:41:09 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=32997#p32997</guid>
		</item>
		<item>
			<title><![CDATA[Re: [Raspberry Pi 400] Why is wifi interface named wlan1 on the Pi400?]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=32996#p32996</link>
			<description><![CDATA[<p>Hello:</p><div class="quotebox"><cite>vanfanel wrote:</cite><blockquote><div><p>... Devuan on both Pi4b and Pi400, in aarch64 mode.<br />... WIFI interface is named WLAN0 on the Pi4b ...<br />... named WLAN1 on the Pi400 ...<br />Any clues?</p></div></blockquote></div><p>Can&#039;t imagine why.</p><p>But check this and see if there&#039;s something there: <a href="https://wiki.debian.org/NetworkInterfaceNames" rel="nofollow">https://wiki.debian.org/NetworkInterfaceNames</a><br />eg: the <span class="bbc">/etc/udev/rules.d/70-persistent-net.rules</span> file in each one of the installations and compare them.</p><p>Best,</p><p>A.</p>]]></description>
			<author><![CDATA[dummy@example.com (Altoid)]]></author>
			<pubDate>Thu, 25 Nov 2021 21:47:15 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=32996#p32996</guid>
		</item>
		<item>
			<title><![CDATA[[Raspberry Pi 400] Why is wifi interface named wlan1 on the Pi400?]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=32994#p32994</link>
			<description><![CDATA[<p>Hi there,</p><p>I use Devuan on both Pi4b and Pi400, in aarch64 mode.<br />In both cases, I manually load the bcrmfmac module when it&#039;s needed.<br />The problem is that the WIFI interface is named WLAN0 on the Pi4b but it&#039;s named WLAN1 on the Pi400, and that breaks some of my scripts.</p><p>So, what could be at play here? Any clues?</p><p>Thanks!</p>]]></description>
			<author><![CDATA[dummy@example.com (vanfanel)]]></author>
			<pubDate>Thu, 25 Nov 2021 19:35:56 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=32994#p32994</guid>
		</item>
	</channel>
</rss>
