On Thu, 26 Jun 2008, Dan Long wrote:
ifcfg-eth0 - realteak 8139 Fibre w/ HWADDR ... alias eth3 8139too
You have a mismatch here. I'm not saying that this will explain the behaviour that you see, but keeping things in sync makes for less surprises.
The hwconf content is based on walking the PCI bus; that is a serial operation. Module loading managed by udev can happen in parallel and, if the timing in different runs differs, the order in which the modules are loaded and the hardware is detected is different.
The interesting thing is that if I ping 192 network, it returns good ping.
Why should it not ? Also keep in mind that with Linux IPs are assigned to the host and not to interfaces.
We considered udev rules. I think most of them are in the 70 or 75-network.rules? We do use udev rules for some other stuff for our application.
Sorry, I never needed to write udev rules on RHEL, a properly set HWADDR always worked. I did have unpleasant encounters with udev on Debian etch where the HWADDR mechanism doesn't exist.
-- Bogdan Costescu IWR, University of Heidelberg, INF 368, D-69120 Heidelberg, Germany Phone: +49 6221 54 8869/8240, Fax: +49 6221 54 8868/8850 E-mail: [EMAIL PROTECTED] _______________________________________________ rhelv5-list mailing list rhelv5-list@redhat.com https://www.redhat.com/mailman/listinfo/rhelv5-list
