q3k :blobcatcoffee:
Systemd predictable network interface names are awesome.
Not only I get easy to remember names like enp2s0f0u7u3c2 but I _also_ get to experience a machine not coming back up after reboot because a new (non-NIC!) PCIe card caused existing names to shuffle around.
Leah Neukirchen
@manawyrm @q3k @artemist @wolf480pl reinventing ifrename, but fine, it works too.
Manawyrm | Sarah
I'm always doing this sort of stuff on my machines:
# cat /etc/udev/rules.d/70-if-names.rules
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="36:8a:56:7b:8c:d7", NAME="locix"
systemd can then do whatever the hell it wants, but my interfaces names will stay the same :)
q3k :blobcatcoffee:
@artemist @wolf480pl What I would like (and I don't mean to sound like some kind of RETVRN TO DEVUAN freak) is the oldschool way of using kernel enumeration as a base (eth0, eth1, usb0, etc), and then pinning it statefully to MAC in userspace.
I know it's not great for us NixOS folks, but there we could just declaratively pin interface names to MAC via nixos-generate-config. Effectively the same behaviour.
artemist
@q3k @wolf480pl i think systemd supports using mac address in interface names but doesn't by default for some weird reason?
q3k :blobcatcoffee:
@wolf480pl ... if only there was a universally present, globally unique identifier that could be used to track network devices across bus swaps!
Wolf480pl
@q3k
Nobody expected that ethernet network pcie 2 subdevice 0 function 0 usb 7 usb 3 configuration 2 would stop being pcie 2 at some point
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.