On Wed, 17 May 2006, Lucian Stroe wrote:
> On Wed, 17 May 2006 16:53:59 -0400, Luke Scharf <[log in to unmask]> wrot=
>
> e:
>
> >Lucian Stroe wrote:
> >
> >>> This implies that the eth0 interface was never configured. The file
> >>>
> >>>/etc/sysconfig/network-scripts/ifcfg-eth0 needs to exist before a
> >>>"activate" will work.
> >>>
> >>>
> >>
> >>I can understand this, but it looks more as an explanation than a solut=
>
> io
> >>n
> >>for solving the problem. So, what I have to do?
> >>
> >>
> >The hard-core way:
> >
> ># nano /etc/sysconfig/network-scripts/ifcfg-eth0
> >
> >
> >Or, if you like vi:
> >
> ># vi /etc/sysconfig/network-scripts/ifcfg-eth0
> >
> >And set the appropriate variables in the file. I often use examples
> >from other machines for this. This is a very flexible way to configure
> >the NIC.
> >
> >The easy way (console):
> >
> ># /usr/sbin/netconfig
> >
> >
> >And then follow the prompts. This is very easy and fast; I use it when
> >I'm setting up a workstation with a vanilla IP configuration, where all
> >I need is a static-IP or a DHCP configuration. It's not so good for
> >unusual, multi-NIC, or multi-homed configurations -- but, how often
> >does one do those things?
> >
> >The GUI way:
> >
> >$ system-config-network
> >
> >I don't configure networks with the GUI. I've opened the GUI tool a
> >couple of times, and it looks like it works at least as well as
> >/usr/sbin/netconfitg -- but I prefer to have the fundamentals configured=
>
>
> >before I have to face a graphical desktop. Just my personal peeves,
> >mind you -- it's your system, and you can do it your way!
> >
>
> Do you mean, essentially, that I have to set the IP number, the gateway, =
>
> the
> DNS and so on? But this was already done during the installation... Why
> should I repeat it?
You should not have to. Check to see if there is a eth1 config file. The
installer might have gotten confused about which card was eth0 and which
was eth1.
Can you send me /root/anaconda-ks.cfg
-Connie
>
> Lucian.
>
|