On 04/03/2014 11:28 PM, Michael Biebl wrote:

On 4. April 2014 05:43:10 MESZ, Stephen Powell <zlinux...@wowway.com> wrote:
On Thu, 03 Apr 2014 22:14:28 -0400 (EDT), Michael Biebl wrote:
Actually, this doesn't tell the whole story. While it is true, that
upstream has deliberately removed that feature (for the reasons you
mentioned, renaming network interfaces within the same namespace is
racy), in the Debian udev package we decided to keep the old network
interface naming scheme and make the new predictable interface names
[0]
explicitly opt-in [1].
Yes, for the change in interface names to work properly, one must
specify net.ifnames=1 as a kernel boot option when using a kernel
compiled from Debian kernel sources.
So even in jessie, we still ship
/lib/udev/rules.d/75-persistent-net-generator.rules which is
responsible
for creating /etc/udev/rules.d/70-persistent-net.rules.
You may ship it, but it doesn't actually work.  It may be useful during
installation, but if you erase the file after installation, it does not
get re-created, and if you add a new NIC after installation, the new
data for the new card does not get appended.  Are you saying that, in
the
Debian version of systemd, this is supposed to work?  If that is your
claim,
then in Debian, this is a bug after all.
If it doesn't work it's a bug

I can vouch that it doesn't work.

Also referencing one of Stephen's comments:

"If you only have one network interface of a given type, you
probably don't need this file.  After all, if your machine only
has one ethernet interface, it's a pretty safe bet that it will
be called eth0."

That would be wonderful if it always worked that way; however, when I replaced the NIC in a jessie system, there was no network connection and lshw informed me that the new NIC was now eth1. That might be because of the still existing persistent net rule. I did not try without the file, which follows from the fact that I didn't know why the net rule was not being updated in the first place.

As of late, I've been building wireless routers using 2 NIC's and a wireless adapter, bridging one of the NIC's with the wireless. For this purpose, it really helps to have a persistent naming system, as much of the supporting software uses ethX in their config files.

Gentlemen, I appreciate the input.  Thanks for your help.

Dale


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to