Been running Redhat 8 (kernal 18 I think) for a couple of weeks but due to ssh slogin problems (slogin times out) I decided to update.
Reinstalled from 2 disk set ok - using the workstation model and no firewall option. Registered with readhat and downloaded all the rpms that it wanted (eth0 fine at this point) using up2date.
Rebooted onto kernal 20 and eth0 would not go. ifconfig down & up wouldn't make any difference. No configuration changes were made. Same situation when I boot on kernal 18.

When I try to ping an address on the same subnet (e.g. the gateway that it had used 10 minutes before) it replies that the destination is unreachable. Other machines on the subnet cannot ping the redhat box.

running ifconfig reports nothing that I can detect as being unusual. I do see that the base address has sometimes changed from 0x5000 to higher values.

Can ping localhost fine.

After many reinstalls from scratch (the initial install usually works fine - but not always) the upgrades always flake out.

Hardware is Compaq Deskpro EN SFF with 450Mhz CPU using embedded controller.

All static IP information (addr, g/w etc.)

Suggestions please.
Peter.

what's your route table look like - is the default route specifically stated?

netstat -r and look for you gw address - i.e mine is 10.117.1.5 (as an example)

Destination Gateway Genmask Flags MSS Window irtt Iface
10.117.1.0 * 255.255.255.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 10.117.1.5 0.0.0.0 UG 0 0 0 eth0

using route the output is

10.0.0.0 * 255.255.255.0 U 0 0 0 etho
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
then it thinks for a while and prints
default 10.0.0.1 0.0.0.0 UG 0 0 0 eth0

The static I address I an using is 10.0.0.16 and I cannot ping 10.0.0.1 so I shouldn't need a gateway. Similarly I cannot ping 10.0.0.2 which is a M$ server.

Peter.

ok. Lets drill it down to the base.

1. Can you ping your loopback? (ping localhost and ping 127.0.0.1)
2. Can you ping your own ip

run the following:

#service network stop
tail your /var/log/messages - post the result
#service network start
tail your /var/log/messages - post the result
#ifdown eth0
tail your /var/log/messages - post the result
#ifup eth0
tail your /var/log/messages - post the result

post the following:

/etc/sysconfig/network-scripts/ifcfg-eth0

Hi,
I can ping localhost and 127.0.0.1 without any problems.
The ifdown and ifup didn't alter the contents of the messages file so I tried ifconfig eth0 down and ifconfig eth0 up (which I guesss is the same thing) and it didn't make any difference either. I have included a printout from ifconfig in case it helps.

Thanks for your help.


[root@RIL-L1 root]# ping 10.0.0.1
PING 10.0.0.1 (10.0.0.1) from 10.0.0.16 : 56(84) bytes of data.
From 10.0.0.16 icmp_seq=1 Destination Host Unreachable
[root@RIL-L1 root]# ping 10.0.0.16
PING 10.0.0.16 (10.0.0.16) from 10.0.0.16 : 56(84) bytes of data.
64 bytes from 10.0.0.16: icmp_seq=1 ttl=64 time=0.081 ms
64 bytes from 10.0.0.16: icmp_seq=2 ttl=64 time=0.065 ms

--- 10.0.0.16 ping statistics ---
2 packets transmitted, 2 received, 0% loss, time 1001ms
rtt min/avg/max/mdev = 0.065/0.073/0.081/0.008 ms
[root@RIL-L1 root]# service network stop
Shutting down interface eth0: [ OK ]
Shutting down loopback interface: [ OK ]
[root@RIL-L1 root]# tail /var/log/messages
Sep 4 08:54:46 RIL-L1 gconfd (root-859): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults"
to a read-only config source at position 2
Sep 4 08:54:51 RIL-L1 xinetd[869]: warning: can't get client address: Transport endpoint is not connected
Sep 4 08:54:52 RIL-L1 modprobe: modprobe: Can't locate module sound-slot-0
Sep 4 08:54:52 RIL-L1 modprobe: modprobe: Can't locate module sound-service-0-3
Sep 4 08:54:56 RIL-L1 kernel: ide-floppy driver 0.99.newide
Sep 4 08:54:59 RIL-L1 kernel: hdc: ATAPI 24X CD-ROM drive, 512kB Cache
Sep 4 08:54:59 RIL-L1 kernel: Uniform CD-ROM driver Revision: 3.12
Sep 4 08:55:01 RIL-L1 kernel: cdrom: This disc doesn't have any tracks I recognize!
Sep 4 13:26:01 RIL-L1 network: Shutting down interface eth0: succeeded
Sep 4 13:26:02 RIL-L1 network: Shutting down loopback interface: succeeded
[root@RIL-L1 root]# service network start
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
[root@RIL-L1 root]#tail /var/log/messages
Sep 4 08:55:01 RIL-L1 kernel: cdrom: This disc doesn't have any tracks I recognize!
Sep 4 13:26:01 RIL-L1 network: Shutting down interface eth0: succeeded
Sep 4 13:26:02 RIL-L1 network: Shutting down loopback interface: succeeded
Sep 4 13:27:46 RIL-L1 sysctl: net.ipv4.ip_forward = 0
Sep 4 13:27:46 RIL-L1 sysctl: net.ipv4.conf.default.rp_filter = 1
Sep 4 13:27:46 RIL-L1 sysctl: kernel.sysrq = 0
Sep 4 13:27:46 RIL-L1 sysctl: kernel.core_uses_pid = 1
Sep 4 13:27:46 RIL-L1 network: Setting network parameters: succeeded
Sep 4 13:27:47 RIL-L1 network: Bringing up loopback interface: succeeded
Sep 4 13:27:50 RIL-L1 network: Bringing up interface eth0: succeeded
[root@RIL-L1 root]#ifdown eth0
[root@RIL-L1 root]# tail /var/log/messages
Sep 4 08:55:01 RIL-L1 kernel: cdrom: This disc doesn't have any tracks I recognize!
Sep 4 13:26:01 RIL-L1 network: Shutting down interface eth0: succeeded
Sep 4 13:26:02 RIL-L1 network: Shutting down loopback interface: succeeded
Sep 4 13:27:46 RIL-L1 sysctl: net.ipv4.ip_forward = 0
Sep 4 13:27:46 RIL-L1 sysctl: net.ipv4.conf.default.rp_filter = 1
Sep 4 13:27:46 RIL-L1 sysctl: kernel.sysrq = 0
Sep 4 13:27:46 RIL-L1 sysctl: kernel.core_uses_pid = 1
Sep 4 13:27:46 RIL-L1 network: Setting network parameters: succeeded
Sep 4 13:27:47 RIL-L1 network: Bringing up loopback interface: succeeded
Sep 4 13:27:50 RIL-L1 network: Bringing up interface eth0: succeeded
[root@RIL-L1 root]# ifup eth0
[root@RIL-L1 root]# tail /var/log/messages
Sep 4 08:55:01 RIL-L1 kernel: cdrom: This disc doesn't have any tracks I recognize!
Sep 4 13:26:01 RIL-L1 network: Shutting down interface eth0: succeeded
Sep 4 13:26:02 RIL-L1 network: Shutting down loopback interface: succeeded
Sep 4 13:27:46 RIL-L1 sysctl: net.ipv4.ip_forward = 0
Sep 4 13:27:46 RIL-L1 sysctl: net.ipv4.conf.default.rp_filter = 1
Sep 4 13:27:46 RIL-L1 sysctl: kernel.sysrq = 0
Sep 4 13:27:46 RIL-L1 sysctl: kernel.core_uses_pid = 1
Sep 4 13:27:46 RIL-L1 network: Setting network parameters: succeeded
Sep 4 13:27:47 RIL-L1 network: Bringing up loopback interface: succeeded
Sep 4 13:27:50 RIL-L1 network: Bringing up interface eth0: succeeded
[root@RIL-L1 root]#more ifcfg-eth0
DEVICE=eth0
BOOTPROTO=none
BROADCAST=10.0.0.255
IPADDR=10.0.0.16
NETMASK=255.255.255.0
NETWORK=10.0.0.0
ONBOOT=yes
USERCTL=no
PEERDNS=no
GATEWAY=10.0.0.1
TYPE=Ethernet


ifconfig
eth0 Link encap:Ethernet HWaddr 00:50:8B:71:E3:F0
inet addr:10.0.0.16 Bcast:10.0.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:119 errors:0 dropped:0 overruns:7 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:4998 (4.8 Kb)
Interrupt:11 Base address:0x5000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:159 errors:0 dropped:0 overruns:0 frame:0
TX packets:159 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:13170 (12.8 Kb) TX bytes:13170 (12.8 Kb)

have you checked your cable and the port you are connected to?
try using a different cable and different port

what kind of cable are you using?

The hardware is fine because I use it to download the upgrade from the redhat site. Once I reboot with the upgraded kernal it alll stops working. So reinstall from the CDs again and it is usually fine (had a couple of times that I needed to do yet another install). Going back to the old kernal doesn't help.

I am assuming that the driver gets upgraded and there is a fault in it. Unfortunately, while I can download the new source and break out the source file from the rpm package I don't know how to get it compiled and made active.

I have tried to install from diagnostic programs that I downloaded and transfered to the machine but they don't show anything out of the ordinary.

Peter.