>>>>> "Eric" == Eric Pinnell <[EMAIL PROTECTED]> writes:
Eric> This isn't going to work like you have it here. The router
Eric> will be confused thinking that 128.135.x.x is one both eth0
Eric> and eht1. This is a no-no. You would have to set the
Eric> router up as a bridge and doing that would break all the
Eric> 192.168 stuff.
Eric> What you can do is give the 128.135.97.144 machine a
Eric> 192.168.x.x address and have the router statically map
Eric> 128.135.97.144 to 192.168.x.x. Sorta like an inbound NAT
Eric> kinda thing.
Yep, that's what happened. I thought the router would try both paths
(internal and external) when given a 128.135.97.* address. If it
couldn't find it on the eth1 gateway, it would try the default (eth0)
gateway. But as you say, that ain't how it works. I discovered that
I could ping eth1 128.135.97.* machines, or eth0 128.135.97.* machines
depending on how I set up my route tables, but not both.
Eric> How you would do this would depend on your hardware.
I forgot to mention the hardware again. I am running a RHL 7.1 linux
box as a dedicated firewall router. kernel 2.4.9 with iptables.
I am going to set up the port forwarding now.
JDH
