| 1 |
On Thu, Dec 22, 2016 at 10:40 AM, Daniel Frey <djqfrey@×××××.com> wrote: |
| 2 |
> On 12/21/2016 10:53 PM, Tom H wrote: |
| 3 |
>> On Tue, Dec 20, 2016 at 3:35 PM, Daniel Frey <djqfrey@×××××.com> wrote: |
| 4 |
>>> |
| 5 |
>>> It could be I found a bug. After a reboot it went from the normal |
| 6 |
>>> enp0s1 (or whatever) to eno1677789 or something ridiculous. I had |
| 7 |
>>> this happen on two different machines. |
| 8 |
>> |
| 9 |
>> https://github.com/systemd/systemd/commit/6c1e69f9 |
| 10 |
> |
| 11 |
> So it wasn't just me! My memory seems to lose voltage once in a while, |
| 12 |
> but I remember wondering what happened to the system I was working on |
| 13 |
> remotely after I rebooted, that's why I was sure it happened! ;-) |
| 14 |
|
| 15 |
LOL |
| 16 |
|
| 17 |
I was intrigued by the "non-sensically high onboard indexes" and |
| 18 |
Google gave me the following (you're definitely not alone): |
| 19 |
|
| 20 |
http://serverfault.com/questions/636621/why-is-my-eth0-called-eno16777736 |
| 21 |
|
| 22 |
http://unix.stackexchange.com/questions/91085/udev-renaming-my-network-interface |
| 23 |
|
| 24 |
http://unix.stackexchange.com/questions/153785/what-does-eno-mean-in-network-interface-name-eno16777736-for-centos-7-or-rhel |
| 25 |
|
| 26 |
From the last link: |
| 27 |
|
| 28 |
The /(0000:1000208:01.0)/ above is the Domain:Bus:Device.Function |
| 29 |
address with the bus value, "1000208", being the hexadecimal |
| 30 |
representation of 16777736. However, "0x100" (256) Should be the maximum |
| 31 |
value that you can have for "Bus." |
Archives