On 10/08/12 09:18, Reindl Harald wrote:
and that is why i use /etc/udev/rules.d/70-persistent-net.rules to pin device-name / MAC and no mac-address in ifconfig-scripts since many years
+1
Alternatively, with the biosdevname, you can pin the interface name to the pci(e) slot. That way its a trivial exercise to get 'remote hands' to swap out a dead nic -- no need to fiddle with the mac address.
K
On Aug 9, 2012, at 7:43 PM, Kahlil Hodgson kahlil.hodgson@dealmax.com.au wrote:
On 10/08/12 09:18, Reindl Harald wrote:
and that is why i use /etc/udev/rules.d/70-persistent-net.rules to pin device-name / MAC and no mac-address in ifconfig-scripts since many years
+1
Alternatively, with the biosdevname, you can pin the interface name to the pci(e) slot. That way its a trivial exercise to get 'remote hands' to swap out a dead nic -- no need to fiddle with the mac address.
And if you don't...
Doing remote hands to swap a bad NIC with someone non-Linux qualified in another country, just became the seriously sucky part of your day. BTDT. Got the t-shirt.
Nate
On Fri, Aug 10, 2012 at 9:15 AM, Nate Duehr denverpilot@me.com wrote:
Alternatively, with the biosdevname, you can pin the interface name to the pci(e) slot. That way its a trivial exercise to get 'remote hands' to swap out a dead nic -- no need to fiddle with the mac address.
And if you don't...
Doing remote hands to swap a bad NIC with someone non-Linux qualified in another country, just became the seriously sucky part of your day. BTDT. Got the t-shirt.
No, it always has been since the 2.4 kernel days when a deterministic scan order would always give the same name to the same NIC position. 2.6 has always been a matter of chance if you have more than one card and don't pin with the MAC address (pairs on cards or the motherboard stay together and keep the order within the set, but the pairs will swap).
-
Kahlil Hodgson -
Les Mikesell -
Nate Duehr