I don't think this is a "security" related posting. But for what it's
worth, I constantly have to keep restarting rcnetwork manually to get
my nic's to wake up and grab ip's. it's been like that for ages, i am
used to it. i always keep an console open for just that.
On Nov 25, 2007 10:12 AM,
Hi,
Recently I upgraded from Open Suse 10.2 to 10.3, hoping for faster updates than I had with ZMD. This became true, but I have to manually start the network interfaces (ifup eth0 etc) and then I have to start OpenSue updater by hand. The cause of the problem is that Suse does not start my networkinterfaces. As I have upgraded Suse since I started with Suse Professional 8.0 and never ever had such a weird problem, I was not expecting this at all.
The only way to overcome this is to enable knetworkmanager. This starts my first networkinterface, but not the other two.
When ifup (the traditional way) is specified in Yast, the network interfaces don't start, and hence SuseUpdater always tells me there are no updates available, even after enabling eth0 manually.
On the same machine a fresh install of Suse 10.3 solves this problem, but then I miss all that I have installed over the years.
Knetworkmanager is kind of a solution, but I hope someone has a better suggestion for me.
Regards, Marc
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-security+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-security+help@opensuse.org
-- cheers, dg Darko Gavrilovic, CISSP http://www.linkedin.com/in/darkog --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-security+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-security+help@opensuse.org