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

Groups > linux.debian.user > #202294

Re: Mystery interface reported by ip.

Show all headers | View raw

    From: peter@easthope.ca
    Date: Fri, 02 Nov 2018 06:03:42 -0700
> ... will have another look at this and make a better report.

So here is the effective content of /etc/udev/rules.d/70-persistent-net.rules.  
(The definition of collect follows and is in http://easthope.ca/DebianPage.html .)

peter@joule:~$ collect /etc/udev/rules.d/70*
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:7e:00:ee:9f", \
ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="LocLCS1788"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="e8:94:f6:24:83:52", \
ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="a0:f3:c1:0a:28:f7", \
ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan1"

LocLCS1788 is present and LocLCS218301788 is absent.  Nevertheless, LocLCS218301788 
surfaces here.

peter@joule:~$ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
 group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: LocLCS218301788: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DE
FAULT group default qlen 1000
    link/ether 00:07:e9:78:a8:b0 brd ff:ff:ff:ff:ff:ff
3: LocLCS1788: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast sta
te DOWN mode DEFAULT group default qlen 1000
    link/ether 00:1d:7e:00:ee:9f brd ff:ff:ff:ff:ff:ff
4: rename4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT gr
oup default qlen 1000
    link/ether 00:1d:7e:01:3d:c2 brd ff:ff:ff:ff:ff:ff
5: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORM
ANT group default qlen 1000
    link/ether e8:94:f6:24:83:52 brd ff:ff:ff:ff:ff:ff

How does the system dredge up LocLCS218301788?  A cache?  Haven't seen 
a mention of wicd caching old device names.  Other ideas?

Thanks,                ... Peter E.

=======================================
peter@joule:~$ declare -f collect
collect ()
{
    case $# in
        0)
            echo "collect  <filename>"
        ;;
        1)
            egrep -v '(^ *#)|(^ *$)' $1
        ;;
        *)
            echo "Too many arguments."
        ;;
    esac
}

-- 
Message composed and transmitted by software designed to avoid the 
need, overhead and vulnerability of antivirus software.

123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202                                  +1 
http://easthope.ca/Peter.html              Bcc: peter at easthope. ca

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

Thread

Mystery interface reported by ip. peter@easthope.ca - 2018-10-28 20:00 +0100
  Re: Mystery interface reported by ip. Reco <recoverym4n@enotuniq.net> - 2018-10-28 20:10 +0100
  Re: Mystery interface reported by ip. peter@easthope.ca - 2018-10-30 18:30 +0100
    Re: Mystery interface reported by ip. Reco <recoverym4n@enotuniq.net> - 2018-10-30 19:50 +0100
      Re: Mystery interface reported by ip. peter@easthope.ca - 2018-11-02 14:30 +0100
        Re: Mystery interface reported by ip. Reco <recoverym4n@enotuniq.net> - 2018-11-09 18:00 +0100
          Re: Mystery interface reported by ip. peter@easthope.ca - 2018-11-12 22:40 +0100
            Re: Mystery interface reported by ip. Reco <recoverym4n@enotuniq.net> - 2018-11-13 07:10 +0100
            Subject: Re: Mystery interface reported by ip. peter@easthope.ca - 2018-11-13 16:40 +0100
        Re: Mystery interface reported by ip. peter@easthope.ca - 2018-11-09 18:00 +0100
          Re: Mystery interface reported by ip. Greg Wooledge <wooledg@eeg.ccf.org> - 2018-11-09 18:10 +0100

csiph-web