| 30 Jun 2025 |
 hexa | you would possibly need to retrigger udev to cause the rename to happen | 15:12:50 |
| hexa | there are more interesting ways to shoot yourself in the foot | 15:13:06 |
 Molly Miller | the last time i looked at this 12-18 months ago, retriggering udev wouldn't rename the interfaces, that codepath was only triggered when they get added to the system for the first time | 15:13:34 |
| Molly Miller | the reasoning behind all of this is that our servers all have 4+ network interface each, so we name interfaces by function, and sometimes the interface assignment does change | 15:14:48 |
 K900 | That sounds like you should just use networkd link names for? | 15:15:41 |
 emily | links = {
"10-sfp-lan" = {
matchConfig.Property = [ "OF_FULLNAME=/soc/ethernet@15100000/mac@1" ];
linkConfig.Name = "sfp-lan";
};
"10-sfp-wan" = {
matchConfig.Property = [ "OF_FULLNAME=/soc/ethernet@15100000/mac@2" ];
linkConfig.Name = "sfp-wan";
};
};
| 15:16:00 |
| emily | I don't know if you can change this config and have stuff get re-assigned on the fly though which I guess is the question | 15:16:11 |
| Molly Miller | does that set the interface name properties or does that rename the kernel device? | 15:16:14 |
| K900 | Neither | 15:16:20 |
