Who cares?
drwho
There are two models I've used for this over the years, the Linksys EA8300 and the WRT 1900AC. Here's how I did it both times (though I only got around to writing up my notes the second time.
Just defining the threat model of hardware addressing, as it stands.
I don't agree with them sending more than the first half either.
Not that the local DHCP servers falling over has anything to do with it...
A MAC address isn't really unique. Each has six octets, of which three refer to the manufacturer. The other three octets have at most 16,777,216 possible values. That seems like a lot but it really isn't; a MAC is supposed to be unique on a LAN, not globally. Rollovers during manufacturing happen, and collisions are rare but happen once in a while.
What do you mean, custom firmware? Are you trying to boot a different distro of Linux?
When you have the USB drive plugged in, how are you booting up? What's the process you're using?
The first three octets of a MAC specify the manufacturer of a NIC chipset. That could come in handy for driver debugging.
Manufacturers and firmware versions of storage devices? You can make the argument; perhaps it would have helped figure out the SSD firmware bugs years ago.
But stuff like whether or not you have video capture card or your current system temperature stats? Nah.. that's getting into "identifiable information as toxic waste" territory.
You can have them installed next to one another. Just like you can have Firefox and Links installed at the same time. Or twm and gnome3. It comes down to how much work you want for yourself.
Depends on your distro, I think.
If only for the sake of one's CV. Making your bones by having a couple of 0-days under your belt helps a lot of folks find jobs these days.
It is. That's why Wayland is being pushed so hard, it's a codebase that's actually maintainable, with hopefully some more modern design and engineering principles.
'till all are one. o7