FAILED for eth0

[Brad Bonkoski]

Paul Smith wrote:
> On 8/17/06, Brad Bonkoski <bbonkoski at mediaguide.com> wrote:
>> what do you get when you run /sbin/ifconfig -a?
>> Perhaps the new network card requires a different driver for your 
>> kernel...
>> And if you are not familiar with the process of building/loading new
>> modules for the kernel, I am not sure if there is an *easy* way to do
>> this, except for letting the installer run and guessing what modules you
>> need....
>>
>> >> > When I turn off my computer, I get an OK for everything, except for
>> >> > eth0. Is there some way of automatically reconfiguring that device?
>> >>
>> >> Your query is a bit vague,
>> >> but the entry in /etc/sysconfig/network-scripts/ifcfg-eth0
>> >> has to be correct.
>> >> The various network wizards should hopefully do this.
>> >
>> > Thanks, Timothy. I agree that my query is vague, but I do not know how
>> > to make it more detailed. Maybe someone could tell me what I should
>> > add to describe better my problem. However, I suspect from what I see
>> > at shutdown time that the problem is related with HWADDR. The content
>> > of /etc/sysconfig/network-scripts/ifcfg-eth0 is quoted below:
>> >
>> > # more /etc/sysconfig/network-scripts/ifcfg-eth0
>> > # Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+
>> > DEVICE=eth0
>> > BOOTPROTO=none
>> > HWADDR=00:30:4F:2B:8C:84
>> > ONBOOT=yes
>> > TYPE=Ethernet
>> > NETMASK=255.255.255.0
>> > IPADDR=192.168.1.2
>> > USERCTL=no
>> > IPV6INIT=no
>> > PEERDNS=yes
>> > GATEWAY=192.168.1.1
>> > #
>> >
>> > I would like to add that my Ethernet card was changed together with
>> > the processor upgrade.
>
> Thanks, Brad. The result of '/sbin/ifconfig -a' follows:
>
> # /sbin/ifconfig -a
> eth0      Link encap:Ethernet  HWaddr 00:14:85:38:2C:93
>          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
>          inet6 addr: fe80::214:85ff:fe38:2c93/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:273531 errors:1057 dropped:0 overruns:0 frame:929
>          TX packets:310170 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:1057 txqueuelen:1000
>          RX bytes:181391697 (172.9 MiB)  TX bytes:72930268 (69.5 MiB)
>          Interrupt:177
>
This is good...it shows your device it up and looks to be *working* as 
it has transmitted and received packets...
Questions:
Do you have more then 1 Ethernet device in your system?
Do the network settings listed look accurate?
Can you ping any internal machines, like your gateway (192.168.1.1)
Can you ping external machines?

> lo        Link encap:Local Loopback
>          inet addr:127.0.0.1  Mask:255.0.0.0
>          inet6 addr: ::1/128 Scope:Host
>          UP LOOPBACK RUNNING  MTU:16436  Metric:1
>          RX packets:2434 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:2434 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:2298167 (2.1 MiB)  TX bytes:2298167 (2.1 MiB)
>
> sit0      Link encap:IPv6-in-IPv4
>          NOARP  MTU:1480  Metric:1
>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>
> #
>
> Paul
>