but the solution i employ was add the HWADDR to the ifcfg file.
Thanks.
----- Mensaje Original -----
De: "Trevor Benson" <tbenson@xxxxxxxxxxxxxxx>
Para: "CentOS mailing list" <centos@xxxxxxxxxx>
Enviados: lunes 19 de noviembre de 2007 16H29 (GMT-0400) America/Santiago
Asunto: RE: Network Name issue
Patricio,
I had a very similar issue with a wireless Intel device coming up as _tmp29384792. I found that if I did a service network stop and removed the kernel module, loaded the kernel module and then service network start, everything went back to normal. I have not bothered to see why it loads this way, as its only every few boots on my personal laptop. If I remember correctly people noted the hardware timeout before it completed loading, but this is just a guess as to what it was as I never confirmed any comments people had made.
This isn’t a solution obviously to the issue, but does give you some steps to see if the devices can be reloaded and work or not.
Trevor
From:
centos-bounces@xxxxxxxxxx [mailto:centos-bounces@xxxxxxxxxx] On Behalf Of Patricio
A. Bruna
Sent: Monday, November 19, 2007 8:31 AM
To: CentOS mailing list
Subject: Network Name issue
Hi,
I've installed CentOS 5 on a Dell pe1950 with 2 dual port NICS.
One of the NIC is an Intel and use the e1000 module.
The problem is when the server is rebooted it does no asign the ethx name to
the NICs, instead the so assign something like _dev377362...
so i dont have networking on the server.
Any ideas what is happening and how to solve it?
Thanks.
_______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
