Conversation

Notices

1. Embed this notice
   Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Saturday, 16-Dec-2023 06:31:56 JST Haelwenn /элвэн/ :triskell:

   • fleaz
   @fleaz
   > predictable
   > Mac address
   
   :not_like_this: (lot of embedded devices have the Mac Address defined in the OS)
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Saturday, 16-Dec-2023 07:57:50 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • fleaz
     • LEdoian
     @ledoian @fleaz MAC addresses one likely means painful to debug or even rescue situations.
     
     AFAIK there's only two ways to set the mac address if it's not stored in the NIC:
     - dtb, which is typically static and the same for a whole fleet of devices
     - setting a mac address afterwards, quite similarly to IP addresses, most software for this matches on interface name… woups
   • Embed this notice
     LEdoian (ledoian@pleroma.ledoian.cz)'s status on Saturday, 16-Dec-2023 07:57:52 JST LEdoian

     in reply to

     • fleaz
     @lanodan @fleaz The MAC address might be actually the most predictable of them (unless you set the interface names yourself), at least for the x86-* world: onboard device number ('o') depends on the capabilities of firmware, the positions ('p') can renumber when adding/removing devices (happened to me when I removed WiFi M.2 module from a laptop).
     
     I have probably never seen a computer (apart from a VM) to use the PCIe port numbers ('s'), so I can't say whether they can be reliable.
     
     (And for the embedded devices: when the OS sets the MAC address, it is supposedly controlled by the admin, so safe to match against, isn't it? It just means that on any change of MAC you might need to change multiple configs, which sucks, but IMHO much less than having the device be offline because the "predictable" name changed…)