Thank you for all or your suggestions and requests for more info.
I now have the system to the point where eth0 is initialized
correctly at boot but can't ping a host on the same subnet -
PING 10.4.4.185 (10.4.4.185) 56(84) bytes of data.
From 10.4.4.179 icmp_seq=1 Destination Host Unreachable
From 10.4.4.179 icmp_seq=2 Destination Host Unreachable
Cable is OK - previously used by telecommuter to plug in her
laptop.
I followed Wayne's suggestion and audited all of the
files mentioned in his post - everything looks as it should.
I suspect the routing table entries are the culprit - should
there be a "Gateway" entry other than 0.0.0.0 for 10.4.4.0?
The 169.* address is coming from an 'if' stmt in the ifup
script - seems relatively innocuous.
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
Use Iface
10.4.4.0 0.0.0.0 255.255.255.0 U 0 0
0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0
0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
0 lo
0.0.0.0 10.4.4.1 0.0.0.0 UG 0 0
0 eth0
/var/log/messages <snipped>:
Jul 31 08:46:05 linux-dev kernel: ip_tables: (C) 2000-2002 Netfilter
core team
Jul 31 08:46:05 linux-dev kernel: Linux Tulip driver version
0.9.15-pre12 (Aug 9, 2002)
Jul 31 08:46:05 linux-dev kernel: PCI: Found IRQ 9 for device 00:11.0
Jul 31 08:46:05 linux-dev kernel: eth0: Lite-On 82c168 PNIC rev 17 at
0xc8884000, 00:A0:CC:20:8A:8D, IRQ 9.
lsmod output:
Module Size Used by Not tainted
nls_iso8859-1 3516 1 (autoclean)
nls_cp437 5116 1 (autoclean)
vfat 13004 1 (autoclean)
fat 38808 0 (autoclean) [vfat]
ide-cd 35708 0 (autoclean)
cdrom 33728 0 (autoclean) [ide-cd]
parport_pc 19076 1 (autoclean)
lp 8996 0 (autoclean)
parport 37056 1 (autoclean) [parport_pc lp]
autofs 13268 0 (autoclean) (unused)
tulip 43840 1
ipt_REJECT 3928 6 (autoclean)
iptable_filter 2412 1 (autoclean)
ip_tables 15096 2 [ipt_REJECT iptable_filter]
keybdev 2944 0 (unused)
mousedev 5492 1
hid 22148 0 (unused)
input 5856 0 [keybdev mousedev hid]
usb-uhci 26348 0 (unused)
usbcore 78784 1 [hid usb-uhci]
ext3 70784 2
jbd 51892 2 [ext3]
<lament>
I am a Unix developer by trade, with just enough admin knowledge
to get into trouble - amidst a sea of Micro$oft naysayers.
Wayne <(E-Mail Removed)> wrote in message news:<bga6v7$iob$(E-Mail Removed)>...
> Red Hat's GUI network setup tools haven't work right since
> 7.1. Use webmin or re-edit the files in /etc/sysconfig:
> network
> network-scripts/ifcfg-eth0
>
> THEN REPLACE any files in networking/* with symlinks to the
> real files in network-scripts. The GUI RH tools create
> inconsistant files in network-scripts and networking. The
> boot-time and ifup, ifdown scripts generally defer to
> network-scripts/* but the code is really bizzare, at least
> in RH 7.3 and 8.0. I guess whoever was updating this
> for RH must have changed jobs before the conversion was
> complete, and didn't leave good notes for whomever is
> maintaining it now. I think the updates are to support
> IPv6 and the new "ip" configuration command.
>
> (I don't have RH 9 but as I understand it 9.0 is really
> 8.1 and so probably has the same nasty scripts.)
>
> And don't forget to update the /etc files: hosts,
> resolv.conf, defaultroute, nsswitch.conf, ...
>
> Good luck!
>
> -Wayne
>
> Bit Twister wrote:
>
> > On 30 Jul 2003 13:37:16 -0700, KFWebb wrote:
> >
> >>I have installed RH 9.0 twice on the same box
> >>and for the network config I have selected STATIC
> >>and entered my IP address in the appropriate
> >>text widget. After each install I am getting DHCP
> >>entries in the routing table. I am now trying to give
> >>the machine a 'hand-job' (wink, wink, nudge, nudge
> >>for all of the pervs out there), and I am finding
> >>I must be missing something. The 'Network Tool'
> >>indicates the correct IP address and hostname,
> >>routing table just has the loopback entry, and the
> >>boot output indicates eth0 init is failing. Here is my
> >>ifcfg-eth0:
> >>
> >>DEVICE=eth0
> >>BOOTPROTO=static
> >>ONBOOT=yes
> >>IPADDR=X.X.X.X
> >>NETMASK=255.255.255.0
> >>NETWORK-X.X.X.0
> >>BROADCAST=X.X.X.255
> >>GATEWAY=X.X.X.1
> >>
> >>
> >>Any ideas? What am I missing?
> >
> >
> > Yes, providing us with error messages in /var/log/messages after doing a
> > service network restart ?
|