RedHat 9 and routing

Hi

I have the following problem:

I've got a RedHat9-box with two ethernet interfaces.
eth0 is 10.49.0.3/24, eth1 is 10.49.1.1/24.
I want the machine to act as a router between those two subnets.
The gateway to the internet is 10.49.0.1.

I've already changed the value of net.ipv4-ip_forward to "1" in
/etc/sysctl.conf, so /proc/sys/net/ipv4Ip-forward contains "1".

The routing table looks like this:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
255.255.255.255 * 255.255.255.255 UH 0 0 0 eth1
10.49.0.0 * 255.255.255.0 U 0 0 0 eth0
10.49.1.0 * 255.255.255.0 U 0 0 0 eth1
169.254.0.0 * 255.255.0.0 U 0 0 0 eth1
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 10.49.0.1 0.0.0.0 UG 0 0 0 eth0

I can ping the 10.49.1.1 interface as well as the 10.49.0.3 interface from
any host in the 10.49.1.0/24 subnet. What do i have to do, to reach the
othe hosts in the 10.49.0.0/24 subnet (and even more important: the internet)?
This is pretty urgent and it seems I've forgotten something basic! :-)

Rgds
SMG

After reading some other postings with similar concerns I realized
that you might need som more information.
Basically I try to create a dmz, so here's the setup:

DSL-Modem
|
|
outgate.xx.xxxx.com /*RH9 w/ iptables and NAT*/
eth1:192.168.49.1/24 /*AFAIK unimportant for pppoe*/
eth0:10.49.0.1/24
|
|
Ethernet-Switch /*some more machines are connected to this,*/
| /*all of them in the 10.49.0.0/24 subnet*/
|
ingate.xx.xxxx.com /*RH9, running dhcpd and named for*/
eth0:10.49.0.3/24 /*subnet 10.49.1.0/24 over eth1*/
eth1:10.49.1.1/24 /dhcpd and named working fine*/
|
|
Ethernet-Switch
|
|
wks-xx.xx.xxxx.com /*Several machines running WinXP Pro*/
eth0:10.49.0.5 /*(for an example)*/


As already mentioned, the Problem is routing on "ingate".
The kernelversion is 2.4.20-8 SMP (dual cpu-box)
This is the configuration data of the interfaces:

eth0 Link encap:Ethernet HWaddr 00:80:5F:EF:98:61
inet addr:10.49.0.3 Bcast:10.49.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1494 errors:0 dropped:0 overruns:0 frame:0
TX packets:1876 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:157273 (153.5 Kb) TX bytes:148254 (144.7 Kb)
Interrupt:9 Base address:0x6400

eth1 Link encap:Ethernet HWaddr 00:50:FC:6032
inet addr:10.49.1.1 Bcast:10.49.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:677 errors:0 dropped:0 overruns:0 frame:0
TX packets:373 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:55804 (54.4 Kb) TX bytes:35440 (34.6 Kb)
Interrupt:9 Base address:0xd000

Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt
Iface
255.255.255.255 0.0.0.0 255.255.255.255 UH 0 0 0
eth1
10.49.0.0 0.0.0.0 255.255.255.0 U 0 0 0
eth0
10.49.1.0 0.0.0.0 255.255.255.0 U 0 0 0
eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
eth1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 10.49.0.1 0.0.0.0 UG 0 0 0
eth0

The value of "/proc/sys/net/ipv4/ip-forward" is "1".

Pinging from 10.49.0.5 (WinXP Workstation) I get the following results:

/*for eth1 of the router*/
Pinging 10.49.1.1 with 32 bytes of data:
Reply from 10.49.1.1: bytes=32 time<1ms TTL=64
Reply from 10.49.1.1: bytes=32 time<1ms TTL=64
Reply from 10.49.1.1: bytes=32 time<1ms TTL=64
Reply from 10.49.1.1: bytes=32 time<1ms TTL=64
Ping statistics for 10.49.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

/*for eth0 of the router*/
Pinging 10.49.0.3 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 10.49.0.3:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

/*for eth0 of the internet-gateway (outgate)*/
Pinging 10.49.0.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 10.49.0.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

I do know that the 255.255.255.255 (host-) route is for dhcp,
but I can't imagine what that route to 169.254.0.0 should mean.

Folks, I'm completely bummed out and will appreciate ANY help! :-)

TIA
Rgds
Sven

OOOOOOPS... several typos ihn the last one, maybe I should go
and sleep for an hour or two... please disregard my last posting.
I rechecked the following twice, so this is the ACTUAL posting.


After reading several other postings with similar concerns I realized
that you might need some more information.
Basically I try to create a dmz, so here's the setup:

DSL-Modem
|
|
outgate.xx.xxxx.com /*RH9 w/ iptables and NAT*/
eth1:192.168.49.1/24 /*AFAIK unimportant for pppoe*/
eth0:10.49.0.1/24
|
|
Ethernet-Switch /*some more machines are connected to this,*/
| /*all of them in the 10.49.0.0/24 subnet*/
|
ingate.xx.xxxx.com /*RH9, running dhcpd and named for*/
eth0:10.49.0.3/24 /*subnet 10.49.1.0/24 over eth1*/
eth1:10.49.1.1/24 /dhcpd and named working fine*/
|
|
Ethernet-Switch
|
|
wks-xx.xx.xxxx.com /*Several machines running WinXP Pro*/
eth0:10.49.1.5 /*(for an example)*/

As already mentioned, the Problem is routing on "ingate".
The kernelversion is 2.4.20-8 SMP (dual cpu-box)
This is the configuration data of the interfaces:

eth0
Link encap:Ethernet HWaddr 00:80:5F:EF:98:61
inet addr:10.49.0.3 Bcast:10.49.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1494 errors:0 dropped:0 overruns:0 frame:0
TX packets:1876 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:157273 (153.5 Kb) TX bytes:148254 (144.7 Kb)
Interrupt:9 Base address:0x6400

eth1
Link encap:Ethernet HWaddr 00:50:FC:6032
inet addr:10.49.1.1 Bcast:10.49.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:677 errors:0 dropped:0 overruns:0 frame:0
TX packets:373 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:55804 (54.4 Kb) TX bytes:35440 (34.6 Kb)
Interrupt:9 Base address:0xd000

Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
255.255.255.255 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
10.49.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
10.49.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 10.49.0.1 0.0.0.0 UG 0 0 0 eth0

I do know that the 255.255.255.255 (host-) route is for dhcp,
but I can't imagine what that route to 169.254.0.0 should mean.
I suppose it's for APIPA (A utomatic P rivate IP A dressing)...

The value of "/proc/sys/net/ipv4/ip_forward" is "1".

Pinging from 10.49.0.5 (WinXP Workstation) I get the following results:

/*for eth1 of the router (ingate)*/
Pinging 10.49.1.1 with 32 bytes of data:
Reply from 10.49.1.1: bytes=32 time<1ms TTL=64
Reply from 10.49.1.1: bytes=32 time<1ms TTL=64
Reply from 10.49.1.1: bytes=32 time<1ms TTL=64
Reply from 10.49.1.1: bytes=32 time<1ms TTL=64
Ping statistics for 10.49.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

/*for eth0 of the router (ingate)*/
Pinging 10.49.0.3 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 10.49.0.3:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

/*for eth0 of the internet-gateway (outgate)*/
Pinging 10.49.0.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 10.49.0.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Pinging from the router (ingate) looks like this:

/*for eth0 of the internet-gateway (outgate)*/
PING 10.49.0.1 (10.49.0.1) 56(84) bytes of data.
64 bytes from 10.49.0.1: icmp_seq=1 ttl=64 time=0.916 ms
64 bytes from 10.49.0.1: icmp_seq=2 ttl=64 time=0.936 ms
64 bytes from 10.49.0.1: icmp_seq=3 ttl=64 time=0.968 ms
64 bytes from 10.49.0.1: icmp_seq=4 ttl=64 time=0.769 ms
--- 10.49.0.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 8048ms
rtt min/avg/max/mdev = 0.727/0.848/1.036/0.113 ms

/* for router's own eth0*/
PING 10.49.0.3 (10.49.0.3) 56(84) bytes of data.
64 bytes from 10.49.0.3: icmp_seq=1 ttl=64 time=0.219 ms
64 bytes from 10.49.0.3: icmp_seq=2 ttl=64 time=0.070 ms
64 bytes from 10.49.0.3: icmp_seq=3 ttl=64 time=0.065 ms
64 bytes from 10.49.0.3: icmp_seq=4 ttl=64 time=0.068 ms
--- 10.49.0.3 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 7033ms
rtt min/avg/max/mdev = 0.065/0.086/0.219/0.050 ms

/*for router's eth1*/
PING 10.49.1.1 (10.49.1.1) 56(84) bytes of data.
64 bytes from 10.49.1.1: icmp_seq=1 ttl=64 time=0.199 ms
64 bytes from 10.49.1.1: icmp_seq=2 ttl=64 time=0.260 ms
64 bytes from 10.49.1.1: icmp_seq=3 ttl=64 time=0.068 ms
64 bytes from 10.49.1.1: icmp_seq=4 ttl=64 time=0.072 ms
--- 10.49.1.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 5023ms
rtt min/avg/max/mdev = 0.065/0.121/0.260/0.079 ms

/*for one of the WinXP Workstations*/
PING 10.49.1.2 (10.49.1.2) 56(84) bytes of data.
64 bytes from 10.49.1.2: icmp_seq=1 ttl=128 time=0.302 ms
64 bytes from 10.49.1.2: icmp_seq=2 ttl=128 time=0.207 ms
64 bytes from 10.49.1.2: icmp_seq=3 ttl=128 time=0.188 ms
64 bytes from 10.49.1.2: icmp_seq=4 ttl=128 time=0.189 ms
--- 10.49.1.2 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 6026ms
rtt min/avg/max/mdev = 0.186/0.207/0.302/0.041 ms

A friend told me that I'd have to introduce one ore more static routes,
but as far as I can see all routes are strictly in compliance with the
documentation that I have.

Folks, I'm still completely bummed out and will appreciate ANY help! :-)

TIA

Rgds,
SMG

Folks, don't bother searching the answer, I've got it fixed!
The problem was that outgate (10.49.0.1) didn't have a route
back to the 10.49.1.0/24 subnet.
Sometimes it takes a little longer... :-)