On Sunday 31 Mar 2013 18:06:19 Mick wrote:
> From the elog which I applied carefully and the links to Flameeyes blog
> kindly shared in this M/L, I thought that I would have to rename *all* my
> interfaces.
> 
> Therefore I was surprised to find that only my eth0 changed to enp11s0,
> while my wlan0 stayed the same.  I even rebooted to make sure and had no
> problem connecting wirelessly.
> 
> Is this how it is supposed to be?
> 
> $ ifconfig -a
> enp11s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1492
>         inet 10.10.10.7  netmask 255.255.255.0  broadcast 10.10.10.255
>         inet6 fe80::226:b9ff:fe20:b49c  prefixlen 64  scopeid 0x20<link>
>         ether 00:26:b9:20:b4:9c  txqueuelen 1000  (Ethernet)
>         RX packets 666638  bytes 946921086 (903.0 MiB)
>         RX errors 0  dropped 132  overruns 0  frame 0
>         TX packets 346579  bytes 26003941 (24.7 MiB)
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>         device interrupt 17
> 
> ip6tnl0: flags=128<NOARP>  mtu 1452
>         unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen
> 0 (UNSPEC)
>         RX packets 0  bytes 0 (0.0 B)
>         RX errors 0  dropped 0  overruns 0  frame 0
>         TX packets 0  bytes 0 (0.0 B)
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 
> ip_vti0: flags=128<NOARP>  mtu 1500
>         tunnel   txqueuelen 0  (IPIP Tunnel)
>         RX packets 0  bytes 0 (0.0 B)
>         RX errors 0  dropped 0  overruns 0  frame 0
>         TX packets 0  bytes 0 (0.0 B)
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 
> lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
>         inet 127.0.0.1  netmask 255.0.0.0
>         inet6 ::1  prefixlen 128  scopeid 0x10<host>
>         loop  txqueuelen 0  (Local Loopback)
>         RX packets 789896  bytes 914674121 (872.3 MiB)
>         RX errors 0  dropped 0  overruns 0  frame 0
>         TX packets 789896  bytes 914674121 (872.3 MiB)
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 
> sit0: flags=128<NOARP>  mtu 1480
>         sit  txqueuelen 0  (IPv6-in-IPv4)
>         RX packets 0  bytes 0 (0.0 B)
>         RX errors 0  dropped 0  overruns 0  frame 0
>         TX packets 0  bytes 0 (0.0 B)
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 
> wlan0: flags=4098<BROADCAST,MULTICAST>  mtu 1500
>         ether 70:1a:04:d7:c3:09  txqueuelen 1000  (Ethernet)
>         RX packets 0  bytes 0 (0.0 B)
>         RX errors 0  dropped 0  overruns 0  frame 0
>         TX packets 0  bytes 0 (0.0 B)
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I think I may have found the reason that my wlan0 interface was not renamed, 
although I don't fully understand why it may be so.  It seems that my wireless 
interface is treated as a USB device, not a PCI device, despite the hardware 
being on a pci-express controller. From lshw:

        *-pci:2
             description: PCI bridge
             product: 5 Series/3400 Series Chipset PCI Express Root Port 2
             vendor: Intel Corporation
             physical id: 1c.1
             bus info: pci@0000:00:1c.1
             version: 05
             width: 32 bits
             clock: 33MHz
             capabilities: pci pciexpress msi pm normal_decode bus_master 
cap_list
             configuration: driver=pcieport
             resources: irq:17 ioport:4000(size=4096) memory:f0900000-f09fffff 
ioport:f0200000(size=2097152)
           *-network
                description: Network controller
                product: BCM4312 802.11b/g LP-PHY
                vendor: Broadcom Corporation
                physical id: 0
                bus info: pci@0000:05:00.0
                version: 01
                width: 64 bits
                clock: 33MHz
                capabilities: pm msi pciexpress bus_master cap_list
                configuration: driver=b43-pci-bridge latency=0
                resources: irq:17 memory:f0900000-f0903fff

and further down:

...
  *-network
       description: Wireless interface
       physical id: 4
       logical name: wlan0
       serial: 70:1a:04:d7:c3:09
       capabilities: ethernet physical wireless
       configuration: broadcast=yes driver=b43 driverversion=3.7.10-gentoo 
firmware=666.2 ip=XX.XXX.XX.X link=yes multicast=yes wireless=IEEE 802.11bg


From lsusb:

# lsusb
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0c45:640e Microdia 
Bus 002 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of 
BCM2046 Bluetooth)
Bus 002 Device 004: ID 413c:8157 Dell Computer Corp. Integrated Keyboard
Bus 002 Device 005: ID 413c:8158 Dell Computer Corp. Integrated Touchpad / 
Trackstick
Bus 002 Device 006: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth 
Mini-card

It may be that the steps for renaming explained here:

http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames

are followed through by udev and item 5 is applied to the wireless card.

Does this sound plausible?
-- 
Regards,
Mick

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to