On Mon, 10 Mar 2008 07:54:48 -0500, Les Mikesell wrote: > Antonio M wrote: > > 2008/3/10, pursley1@xxxxxxxxxxxx <pursley1@xxxxxxxxxxxx>: > >> > >> > >> Unfortunately - > >> 1) We don't know which updated component is messing up the network > >> connection. > > from the list of updated component we should reduce the hunt > > > >> 2) I'm relatively new to Fedora (but not Linux) and so I don't know > >> where to file bugs anyway. > > > > bugzilla.redhat.com is the place. > > > >> 3) Since it only did it on 1 of my 2 computers, it seems to be some > >> problem dependent on the hardware...or luck. > >> > >> > > I assumed long ago that there is no luck or magic in software.... :-) > > It became magic when the kernel started detecting devices in parallel so > the names are essentially randomized. The ethN devices are supposed to > be sorted out and renamed before activation if you have the ethernet > hardware address in the corresponding > /etc/sysconfig/network-scripts/ifcfg-ethN file. Run 'ifconfig' and be > sure the hwaddr matches what is in your file for each nic. Doubtful. I do have the h/w addr in the files. The name of the devices did not change either. I just had to drop the appended ".bak" and bring up the if. On next boot, the failure is not repeated. -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
