<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Predictable interface names are inconsistent"
href="https://bugs.freedesktop.org/show_bug.cgi?id=59610#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Predictable interface names are inconsistent"
href="https://bugs.freedesktop.org/show_bug.cgi?id=59610">bug 59610</a>
from <span class="vcard"><a class="email" href="mailto:candyangel@electricjungle.org" title="candyangel@electricjungle.org">candyangel@electricjungle.org</a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=59610#c1">comment #1</a>)
Continuing from my above comment (which should have been a reply, I've not done
well getting things right these early hours), I have done some further testing
at the suggestion of someone in #archlinux.
Stopping dhcpcd.service and starting dhcpcd@wlp6s2 also fixes this behaviour
(the device gets wlp6s2 back when rmmod/modprobed). So the issue is
specifically with the dhcpcd.service interfering with the device renaming.
I just ran 'udevadm monitor -k & ' while reloading the module with
dhcpcd.service stopped and I can now also see the 'move' to the new name.
dhcpcd.service seems to be grabbing the interface as soon as it is added,
preventing udev from renaming it.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>