Very Computer

..but I can't ping a thing...

dual boot machine with win98 on one drive, redhat 5.2 on the other drive
(aka, the drive in question.)

over the weekend I took out the Intel AL440LX motherboard and the PII266
and put in an ABIT BH6 Motherboard and a PII400.

The NIC is an Etherlink III ISA/EISA - 3c509
irq:10, I/0 base 300
ethernet address 0020af728ce2

according to dmesg and /var/log/messages all of these settings are being
passed correctly at boot time.  

Looking back at the messages prior to the change of motherboard, the
outputs related to eth0 (points to the correct module, 3c509) are all
identical, all related services are still being fired up correctly.

I'm using the same network configs that I was using prior to the Mboard
swap, they worked fine for months, so I'm pretty damned sure they're
correct.

I've pulled out the module, removed all network settings, shutdown,
removed the physical card, booted, shutdown, put the card back in,
checked to see that the right module was loaded (3c509) and reset all my
network configs.  Here they are just in case there is something obvious
I'm missing:

hostname: artemis.shults.org
domain: speakeasy.net

nameservers:  
primary: 206.253.194.65
(this is a pnap.net dns server which speakeasy.net uses for it's dsl
accounts.  it is correct for me and works great in windows and used to
work great from linux.)
secondary: 206.191.160.2
tertiary:  206.191.168.2

interface:
io    127.0.0.1  localhost  localhost.localdomain
eth0  206.191.173.4  artemis.shults.org

gateway 206.191.173.1  (yes, this is correct, I am in the same ip block)

netmask 255.255.255.0

broadcast address 206.191.173.255

network 206.191.173.0

I've tried it with ip forwarding both on and off.  (used to work off)

The above all looks great in red hat's gui network configurator, and
looks the same when I run ifconfig with no commands, and with netstat
-rn

here's a red hat oddity that I can't find documentation for:

when I run:

/etc/rc.d/init.d/network status

I get:

"network dead but subsys locked"

start and stop pretend to work but don't.  restart gives a "file not
found" which is comepletely bizarre and wrong (not a typo I've done it
repeatedly)

there is also a file, /var/lock/subsys/network which is comepletely
inaccessible to root, even though it's owned by root and is chmoded 700
(rwx for owner.)  I don't know if this is related or not, but it sure is
curious.

Anyway, I can't ping anything, either by IP or by name, not the machine
on my LAN, not the gateway machine, none of the ns machines, not
www.yahoo.com, not anything.  Well, I can ping myself by name and by ip,
so the loopback is working at least.  *sigh*

Any ideas of where to turn next, what to try next, what docs to read
next, where to post, who to write etc will be much appreciated.

btw, I've been through the appropriate sections of the redhat online
manual for 5.2, I've been through Ethernet-HOWTO, and the applicable
sections of O'Reilly's "Running Linux" and I'm still dead in the water
(posting this from my win98 drive)

Please help if ya think you can (or even if you think you're making a
wild guess, I'll try anything twice.)

Thanks in advance,
~Steven

I just played this hair pulling game with RedHat, yours might (or might
not) be the same problem.  Check /etc/rc.d/rc3.d and see if network is a
K90network or something like that.  Mine was, I changed it back to
S10network and rebooted (it's GOT to start before almost anything else)
and it worked.

Check the other /etc/rc.d/rcx.d as well, only 1, 5 and 6 should be K??

Dan
--
UNIX - Not just for vestal *s anymore
Linux - Choice of a GNU generation

Thanks Dan, Thanks Tom,

This is a new avenue I've not explored yet, so my hopes are raised yet
again.

Here's what I've got in /etc/rc.d/rc*.d

each of these *network files is actually a symlink pointing to
../init.d/network

rc0.d  -  K97network -> ../init.d/network
rc1.d  -  K97network (this and the symlinks below all point to same file
as above)
rc2.d  -  S10network
rc3.d  -  S10network
rc4.d  -  S10network
rc5.d  -  S10network
rc6.d  -  K97network

So, should they all match, or should they be just as they are?

for 0,1 & 6, should I

rm K97network
and
ln -s ../init.d/network S10network

or should I leave it all alone and dig elsewhere for the problem ya
think?

Thanks again,
~Steven

If you start your system in run level 5 (e.g., xdm , kdm, gdm, etc.)
then you should have S10network in rc5.d as well...

-Tom
--
Tom Eastep               \    Opinions expressed here

Shoreline, Washington USA  \    those of my employer

Regrettably, your links look ok....

-Tom
--
Tom Eastep               \    Opinions expressed here

Shoreline, Washington USA  \    those of my employer

Shit, you're right.  I was thinking Linux and typing Solaris (where init
5 is shutdown and init 6 is reboot.)

Oops

Dan
--
UNIX - Not just for vestal *s anymore
Linux - Choice of a GNU generation

No, those are correct.  Run level 0 is shutdown, 1 is single user mode
and 6 is reboot.  What you printed is correct to have it come up in
networked mode for the multi-user modes.  I'm at a loss now.  Have you
done the DOS boot disk and tried to reset the card's configuration?  May
have lost it's mind or the IRQ is reset because you've got it in a
different PCI slot?  Try a different slot and see if the IRQ changes.

Dan
--
UNIX - Not just for vestal *s anymore
Linux - Choice of a GNU generation