SuSE 9.3: network configuration goes nuts
From: Eric (eric000_at_gmx.net)
Date: 11/02/05
- Next message: Amnon Feiner: "Re: what does it mean?"
- Previous message: mst: "Re: Kaffeine refuses to start"
- Next in thread: graham: "Re: SuSE 9.3: network configuration goes nuts"
- Reply: graham: "Re: SuSE 9.3: network configuration goes nuts"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 02 Nov 2005 22:25:46 +0100
Hi everyone,
lately i upgraded from SuSE 9.1 (everything worked great) to 9.3. Right
after the upgrade, i realized my onboard network controller (nvidia),
actually used for internal network (eth0) is useless, because of strange
behaviour (i don't want to describe right now).
So, i installed a new controller (1 GBit) for inernal network (eth1)
besides the controller (100MBit) for external traffic (eth2). I
configured both with Yast2 and everything worked fine.
But every Bootup will bring up a random configuration. Sometimes
internal controller will be eth1 and external eth2 and sometimes they
are setup the other way around.
What is it, a circus? I tried to configure them with eth1 and eth2
instead of the default device name settings of Yast, without success.
Is there a way to have one configuration all the time? What causes this
behaviour, which is really disturbing and confusing?
Thanks,
Eric
- Next message: Amnon Feiner: "Re: what does it mean?"
- Previous message: mst: "Re: Kaffeine refuses to start"
- Next in thread: graham: "Re: SuSE 9.3: network configuration goes nuts"
- Reply: graham: "Re: SuSE 9.3: network configuration goes nuts"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|