[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Mystery interface reported by ip.


On Fri, Nov 09, 2018 at 08:11:06AM -0800, peter@easthope.ca wrote:
>     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.

Ok, let's do it the hard way.

udevadm info /sys/class/net/LocLCS218301788
udevadm trigger /sys/class/net/LocLCS218301788

and, while we're at it,

udevadm info /sys/class/net/rename4
udevadm trigger /sys/class/net/rename4


Reply to: