Hi,

sorry if this is lengthy, but I'm tearing my hair out here...
I am experiencing an odd problem with redhat 9.

I have two network cards in my redhat 9 system... eth0 and eth1

eth0 is a realtek 8139 and eth1 is an ne2k-pci

eth0 goes to the internal lan and eth1 goes to a seperate network which has my webserver on it.

the redhat machine can talk to any of the eth0 (192.168.0.*) systems and to the gateway for eth1 (192.168.1.1), although when I try to ping the webserver on eth1 (192.168.1.2), I get destination host unreachable.

btw if anyone is wondering why I have it set up this way, it's because eth1 is a DMZ but I haven't configured the firewall yet, so it's just NAT'd at the moment.

both network cards are aliased in modules.conf

here's my ifconfigs:

eth0 Link encap:Ethernet HWaddr 00:30:BD:09:56:B4
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
<snip>

eth1 Link encap:Ethernet HWaddr 00:40:05:46:05:C0
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
<snip>

route is as follows:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
1.cust2.nsw.dsl * 255.255.255.255 UH 0 0 0 ppp0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
169.254.0.0 * 255.255.255.0 U 0 0 0 eth0
127.0.0.0 * 255.255.255.0 U 0 0 0 lo
default * 0.0.0.0 U 0 0 0 ppp0

what's this 169.254.0.0 ? I read about zeroconf route somewhere ... although I've noticed that 169.254.0.0 switches from eth0 to eth1 if you bring down the network and bring it back up.. I have no idea what this is... wasn't there in redhat 8... :P

Here's an entry from my logs which I think may be relevant to the problem..

May 7 06:05:09 espace kernel: divert: allocating divert_blk for eth0
May 7 06:05:09 espace kernel: eth0 identified 8139 chip type 'RTL-8139C'
May 7 06:05:09 espace kernel: divert: allocating divert_blk for eth1
May 7 06:05:33 espace kernel: divert: not allocating divert_blk for non-ethernet device ppp0

If anyone has any ideas on how I could fix this, I'd be most grateful.

ur ethO that shld be used unlike eth1 although there is no restriction in using any
check if u r ethernet cable is connected ?

yes, it is... I'd be so cheesed off if it was that simple.... :P

wat is ur gate way ?i had similar problems

-srikant

I have 192.168.1.1 as the gateway for eth1 and 192.168.0.1 for eth0... this config was working with redhat 8... I'm not sure how different rh9 is....

check out my posts and replies hope that my help on that subject

where are your posts? I did a search and it only came up with your sendmail posts... sorry

also go through the following hope it might help u

http://www.tldp.org/LDP/nag2/

Turns out that it was a simple fix .... grrrrrr

I rebooted the web server and then the pings started coming through WTF????

Anyway, thanks for your assistance...

One question tho... does anyone know where this 169.254.0.0 come from and why, and why in the process list, there is a process called [eth0]? I believe they're related, but I've never seen them in a previous distro...