| 1 |
On Sunday 31 Mar 2013 18:06:19 Mick wrote: |
| 2 |
> From the elog which I applied carefully and the links to Flameeyes blog |
| 3 |
> kindly shared in this M/L, I thought that I would have to rename *all* my |
| 4 |
> interfaces. |
| 5 |
> |
| 6 |
> Therefore I was surprised to find that only my eth0 changed to enp11s0, |
| 7 |
> while my wlan0 stayed the same. I even rebooted to make sure and had no |
| 8 |
> problem connecting wirelessly. |
| 9 |
> |
| 10 |
> Is this how it is supposed to be? |
| 11 |
> |
| 12 |
> $ ifconfig -a |
| 13 |
> enp11s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1492 |
| 14 |
> inet 10.10.10.7 netmask 255.255.255.0 broadcast 10.10.10.255 |
| 15 |
> inet6 fe80::226:b9ff:fe20:b49c prefixlen 64 scopeid 0x20<link> |
| 16 |
> ether 00:26:b9:20:b4:9c txqueuelen 1000 (Ethernet) |
| 17 |
> RX packets 666638 bytes 946921086 (903.0 MiB) |
| 18 |
> RX errors 0 dropped 132 overruns 0 frame 0 |
| 19 |
> TX packets 346579 bytes 26003941 (24.7 MiB) |
| 20 |
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 |
| 21 |
> device interrupt 17 |
| 22 |
> |
| 23 |
> ip6tnl0: flags=128<NOARP> mtu 1452 |
| 24 |
> unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen |
| 25 |
> 0 (UNSPEC) |
| 26 |
> RX packets 0 bytes 0 (0.0 B) |
| 27 |
> RX errors 0 dropped 0 overruns 0 frame 0 |
| 28 |
> TX packets 0 bytes 0 (0.0 B) |
| 29 |
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 |
| 30 |
> |
| 31 |
> ip_vti0: flags=128<NOARP> mtu 1500 |
| 32 |
> tunnel txqueuelen 0 (IPIP Tunnel) |
| 33 |
> RX packets 0 bytes 0 (0.0 B) |
| 34 |
> RX errors 0 dropped 0 overruns 0 frame 0 |
| 35 |
> TX packets 0 bytes 0 (0.0 B) |
| 36 |
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 |
| 37 |
> |
| 38 |
> lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 |
| 39 |
> inet 127.0.0.1 netmask 255.0.0.0 |
| 40 |
> inet6 ::1 prefixlen 128 scopeid 0x10<host> |
| 41 |
> loop txqueuelen 0 (Local Loopback) |
| 42 |
> RX packets 789896 bytes 914674121 (872.3 MiB) |
| 43 |
> RX errors 0 dropped 0 overruns 0 frame 0 |
| 44 |
> TX packets 789896 bytes 914674121 (872.3 MiB) |
| 45 |
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 |
| 46 |
> |
| 47 |
> sit0: flags=128<NOARP> mtu 1480 |
| 48 |
> sit txqueuelen 0 (IPv6-in-IPv4) |
| 49 |
> RX packets 0 bytes 0 (0.0 B) |
| 50 |
> RX errors 0 dropped 0 overruns 0 frame 0 |
| 51 |
> TX packets 0 bytes 0 (0.0 B) |
| 52 |
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 |
| 53 |
> |
| 54 |
> wlan0: flags=4098<BROADCAST,MULTICAST> mtu 1500 |
| 55 |
> ether 70:1a:04:d7:c3:09 txqueuelen 1000 (Ethernet) |
| 56 |
> RX packets 0 bytes 0 (0.0 B) |
| 57 |
> RX errors 0 dropped 0 overruns 0 frame 0 |
| 58 |
> TX packets 0 bytes 0 (0.0 B) |
| 59 |
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 |
| 60 |
|
| 61 |
I think I may have found the reason that my wlan0 interface was not renamed, |
| 62 |
although I don't fully understand why it may be so. It seems that my wireless |
| 63 |
interface is treated as a USB device, not a PCI device, despite the hardware |
| 64 |
being on a pci-express controller. From lshw: |
| 65 |
|
| 66 |
*-pci:2 |
| 67 |
description: PCI bridge |
| 68 |
product: 5 Series/3400 Series Chipset PCI Express Root Port 2 |
| 69 |
vendor: Intel Corporation |
| 70 |
physical id: 1c.1 |
| 71 |
bus info: pci@0000:00:1c.1 |
| 72 |
version: 05 |
| 73 |
width: 32 bits |
| 74 |
clock: 33MHz |
| 75 |
capabilities: pci pciexpress msi pm normal_decode bus_master |
| 76 |
cap_list |
| 77 |
configuration: driver=pcieport |
| 78 |
resources: irq:17 ioport:4000(size=4096) memory:f0900000-f09fffff |
| 79 |
ioport:f0200000(size=2097152) |
| 80 |
*-network |
| 81 |
description: Network controller |
| 82 |
product: BCM4312 802.11b/g LP-PHY |
| 83 |
vendor: Broadcom Corporation |
| 84 |
physical id: 0 |
| 85 |
bus info: pci@0000:05:00.0 |
| 86 |
version: 01 |
| 87 |
width: 64 bits |
| 88 |
clock: 33MHz |
| 89 |
capabilities: pm msi pciexpress bus_master cap_list |
| 90 |
configuration: driver=b43-pci-bridge latency=0 |
| 91 |
resources: irq:17 memory:f0900000-f0903fff |
| 92 |
|
| 93 |
and further down: |
| 94 |
|
| 95 |
... |
| 96 |
*-network |
| 97 |
description: Wireless interface |
| 98 |
physical id: 4 |
| 99 |
logical name: wlan0 |
| 100 |
serial: 70:1a:04:d7:c3:09 |
| 101 |
capabilities: ethernet physical wireless |
| 102 |
configuration: broadcast=yes driver=b43 driverversion=3.7.10-gentoo |
| 103 |
firmware=666.2 ip=XX.XXX.XX.X link=yes multicast=yes wireless=IEEE 802.11bg |
| 104 |
|
| 105 |
|
| 106 |
From lsusb: |
| 107 |
|
| 108 |
# lsusb |
| 109 |
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub |
| 110 |
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub |
| 111 |
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub |
| 112 |
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub |
| 113 |
Bus 001 Device 003: ID 0c45:640e Microdia |
| 114 |
Bus 002 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of |
| 115 |
BCM2046 Bluetooth) |
| 116 |
Bus 002 Device 004: ID 413c:8157 Dell Computer Corp. Integrated Keyboard |
| 117 |
Bus 002 Device 005: ID 413c:8158 Dell Computer Corp. Integrated Touchpad / |
| 118 |
Trackstick |
| 119 |
Bus 002 Device 006: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth |
| 120 |
Mini-card |
| 121 |
|
| 122 |
It may be that the steps for renaming explained here: |
| 123 |
|
| 124 |
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames |
| 125 |
|
| 126 |
are followed through by udev and item 5 is applied to the wireless card. |
| 127 |
|
| 128 |
Does this sound plausible? |
| 129 |
-- |
| 130 |
Regards, |
| 131 |
Mick |
Archives