Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #186191

Re: Inconsistent predictable interface names

From Henning Follmann <hfollmann@itcfollmann.com>
Newsgroups linux.debian.user
Subject Re: Inconsistent predictable interface names
Date 2017-08-30 17:10 +0200
Message-ID <ukcMW-1sy-19@gated-at.bofh.it> (permalink)
References (1 earlier) <ujRS9-50m-1@gated-at.bofh.it> <ujSbx-5nB-39@gated-at.bofh.it> <ujSuR-5uV-15@gated-at.bofh.it> <ukaBr-8nI-7@gated-at.bofh.it> <ukb4u-li-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Wed, Aug 30, 2017 at 04:12:16PM +0300, Reco wrote:
> 	Hi.
> 
> On Wed, Aug 30, 2017 at 08:39:44AM -0400, Cindy-Sue Causey wrote:
> > On 8/29/17, Reco <recoverym4n@gmail.com> wrote:
> > 
> > 
[...]
> > I left everything in there in case somehow it already says "yes or
> > no". Is it possible that's previously declared somewhere, possibly
> > maybe in user configuration files that would carry over from upgrade
> > to upgrade?
> 
> OP's e-mail says to this:
> 
> > > I am experiencing an odd issue with a new install of Stretch.
> 
> My e-mails assumed that there was no upgrade.
> 'udevadm info' should've shown such stray configuration files BTW, hence
> 'trie on-disk' remark.
> 

Yep, this was a new install. Even though I tend to reuse old configurations
from previous installs, this very much happend with an untouched new
install (only deviation from a "default" was xfce instead of gnome).
I disabled the NM but at that time the names were already like they are
right now. 

BTW. all those "try on disk" were sent to stderr and I piped only the
stdout into my previous mail, that's why they were missing.


> 
> > Maybe like something manually altered via a network
> > manager at some point... or something....? :)
> 
> That's possible. Network Manager's ability to change MAC address of WLAN
> (for AP scanning), or, say, machanger intervention can lead to funny
> results if "Predictable" NIC Names are enabled. I haven't seen it
> manifested in NIC renaming though.
> 

That was my initial thought.


> It should not be possible in this case (all NICs are PCI devices) since
> "Predictable" NIC Names should set by udev from initrd long before root
> filesystem is mounted and things like Network Manager have a chance to
> interfere.
> 

Yes, and I see that in dmesg happening for eth0. However that does not
happen for the wlan0. I can see the firmware being loaded but no name
changing to predictable pattern.

FWIW

-H


-- 
Henning Follmann           | hfollmann@itcfollmann.com

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Inconsistent predictable interface names Henning Follmann <hfollmann@itcfollmann.com> - 2017-08-29 17:10 +0200
  Re: Inconsistent predictable interface names Reco <recoverym4n@gmail.com> - 2017-08-29 18:50 +0200
    Re: Inconsistent predictable interface names Henning Follmann <hfollmann@itcfollmann.com> - 2017-08-29 19:10 +0200
      Re: Inconsistent predictable interface names Reco <recoverym4n@gmail.com> - 2017-08-29 19:30 +0200
        Re: Inconsistent predictable interface names Henning Follmann <hfollmann@itcfollmann.com> - 2017-08-30 14:20 +0200
        Re: Inconsistent predictable interface names Cindy-Sue Causey <butterflybytes@gmail.com> - 2017-08-30 14:50 +0200
          Re: Inconsistent predictable interface names Reco <recoverym4n@gmail.com> - 2017-08-30 15:20 +0200
            Re: Inconsistent predictable interface names Henning Follmann <hfollmann@itcfollmann.com> - 2017-08-30 17:10 +0200
              Re: Inconsistent predictable interface names David Wright <deblis@lionunicorn.co.uk> - 2017-08-30 18:50 +0200

csiph-web