Ray, We were correct in that when I removed the extra IP from the interface it solved the initial problems at least partially. I can now ping eth1 and eth2 on the lrp but not eth0. In other words both subnets can ping the others interface on the router but not past it to the rest of the subnet. If the DMZ (192.168.10.1) can see the interface at 192.168.1.254 (eth1on lrp) shouldn't the router handle the rest of the routing? As well as out to the internet? The route command on the DMZ shows:
Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.10.0 * 255.255.255.0 U 0 0 0 eth0 127.0.0.0 * 255.0.0.0 U 0 0 0 lo default * 0.0.0.0 U 0 0 0 eth0 default 192.168.10.254 0.0.0.0 UG 0 0 0 eth0 Again netstat -nr on the lrp gives: # netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2 24.209.X.X 0.0.0.0 255.255.248.0 U 0 0 0 eth0 0.0.0.0 24.209.x.x 0.0.0.0 UG 0 0 0 eth0 I thought I understood the rout command well enough to clean up the router tables on the DMZ but I have had a bit of difficulty. I tried to delete the extra default entry but I am not sure which one needs to be there. Should the default gateway be 0.0.0.0 0.0.0.0 or point to the interface 192.168.10.254 with a netmask of 255.255.255.0. All my Win boxes on subnet 1 point to 192.168.1.254 255.255.255.0 and work fine. Thanks again, Kory Ray Olszewski wrote: > > At 06:24 PM 12/25/01 -0500, Kory Krofft wrote: > >Ray, > ... > >If I ping www.msn.com or www.rr.com it resolves the ip's but the request > >times out. > > The same thing happens with these two FQDNs if I try them from here. They > may be set not to respond to ping traffic. Try different addresses (try mine > -- comarre.com = 63.198.182.124 -- if you like; it should respond to > standard pings). > > >The DMZ is a Redhat box and is the only machine on that net. I reset > >the ip to the same as the windows subnet and connected directly to the > >hub. I was then able to telnet into it and so I believe the networking > >is functional. > > You provided a lot of detail, in which I spot only one problem, the same one > you spotted: > > >2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100 > > link/ether 00:06:29:4f:2a:ee brd ff:ff:ff:ff:ff:ff > > inet 192.168.1.10/24 brd 192.168.1.255 scope global eth0 > > (This looks like a leftover from the last config. How do I get rid of > >it? ) > > inet 192.168.10.1/24 brd 192.168.10.255 scope global eth0 > > I don't know how to interpret this dual address for the eth0 interface, but > if it really means that the kernel thinks eth0 has two different IP > addresses, I bet it is the source of the problem (combined with a > routing-table problem). > > I'm not a Red Hat specialist (I use Debian and LEAF), but I'd suggest using > the "ifconfig" command to bring this eth0 interface down, then restart it > with just the one, correct address. Then use the "route" command to do any > needed tidying up to the routing table. Then see if it will ping. If it > will, fix whatever init scripts you have that start up networking on this host. > > If that is not the source of the problem, then everything else looks OK ... > assuming you are trying the ping to address 192.168.10.254, not some > hostname that resolves to it. If the failure does happen when you ping by > hostname, the box might be telling you it can't find a route to its > nameserver (whatever that is -- does the RH box run named or use resolvers > listed in /etc/resolv.conf ?). > > [rest deleted] > > -- > ------------------------------------"Never tell me the odds!"--- > Ray Olszewski -- Han Solo > Palo Alto, CA [EMAIL PROTECTED] > ---------------------------------------------------------------- > > _______________________________________________ > Leaf-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-user _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
