If the kernel reads an apparently invalid MAC address, it should first try reversing the bit-order. The Network Working Group documented the issue in 1998 and provided the correct solution: reverse the bit order of the LAN adapter to restore it to canonical form.
This is an old problem that has bee solved. Scott James Remnant is correct: "The kernel need not pick a *RANDOM* MAC address, it could use one that's at least predictable" Status: D0 PME-Enable+ DSel=0 DScale=0 PME-Ĭapabilities: Message Signalled Interrupts: Mask+ 64bit+ Queue=0/3 Enable-Ĭapabilities: HyperTransport: MSI Mapping Region 0: Memory at dfffd000 (32-bit, non-prefetchable) Ĭapabilities: Power Management version 2įlags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- # file however you are also free to add your own entries. Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells With over 10 pre-installed distros to choose from, the worry-free installation life is here Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use. # Entries are automatically added by the 75-persistent- net-generator. # This file maintains persistent names for network interfaces. $ cat /etc/udev/ rules.d/ 70-persistent- net.rules
0 kommentar(er)
