HWADDR variable in RHAS 3

[Karasik, Vitaly]

You can change NICs order with nameif utility [from net-tools package]

Rgds,
Vitaly

> -----Original Message-----
> From: redhat-list-bounces at redhat.com
> [mailto:redhat-list-bounces at redhat.com]On Behalf Of Harry Hoffman
> Sent: Tue, November 16, 2004 4:44 PM
> To: General Red Hat Linux discussion list
> Subject: HWADDR variable in RHAS 3
> 
> 
> Hi All,
> 
> 
> I'm wondering if anyone else has seen this:
> 
> IBM 306 with 3 e1000 cards, 2 onboard and 1 add-on PCI.
> 
> After an up2date of the kernel to 2.4.21-20.ELsmp (and a 
> reboot to use 
> the new kernel) eth1 and eth2 flip-flopped.
> 
> I tried to manually force the cards to be associated in a 
> specific order 
> by setting the HWADDR variable in:
> /etc/sysconfig/network-scripts/ifcfg-eth[x]
> 
> but this caused an error (which didn't get logged to 
> /var/log/messages 
> but was displayed on the console) to the effect of "Can't 
> assign MAC to 
> eth2, already in use" [my paraphrasing]. (This is a 
> production box so I 
> had to get it back working and couldn't spend more time testing)
> 
> 
> I quick search on bugzilla showed this to be a bug in earlier 
> releases 
> but also stated that it was now fixed.
> 
> So, before I open a new bug report has anyone else seen this behavior 
> under RHAS-3 (Update 3)?
> 
> Thanks,
> Harry
> 
> -- 
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
> 
***********************************************************************************
Information contained in this email message is intended only for use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the postmaster at nds.com and destroy the original message.
***********************************************************************************