|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: [suse-security] e1000 Problem after Kernel Update
From: Christian Boltz (suse-security
cboltz.de)
Date: Fri Jun 10 2005 - 17:00:32 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hello,
Am Freitag, 10. Juni 2005 21:42 schrieb Dirk Enrique Seiffert:
> > Result: the eth0 and eth1 are interchanged.
>
> I made a similar experience: Network cards now are identified by
> there MAC-Adress, like ifcfg-eth-id-00:0a:e6:e6:8f:fb. Have a look
> into /etc/sysconfig/network to find the values for your machine.
> These values should replace eth0/eth1 in /etc/sysconfig/SuSEfirewall2
Additionally, you can use a "stable" name. Just add something like
PERSISTENT_NAME='cable'
to /etc/sysconfig/network/ifconfig-*
Please note that you should not use "eth0" or any other existing device
name as persistent name - it will make trouble. (However, eth42 should
work as long as you don't really have that much network cards.)
Regards,
Christian Boltz
--
Sorry, mit java kenne ich mich gar nicht aus, das ist mir einfach zu
unportabel. [Thorsten Kukuk in suse-linux]
--
Check the headers for your unsubscription address
For additional commands, e-mail: suse-security-help
suse.com
Security-related bug reports go to security
suse.de, not here
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]