(no subject)

Marc Owen (yjs@kpmg.com.my)
Tue, 22 Jun 1999 09:40:40 +0800


My private side: 10.166.166.x/255.255.255.0
My LAN side: 10.187.x.x/255.255.224.0

I can ping from:
client (private) to client (LAN)
client (private) to server (LAN)
linux firewall to client (LAN) and server (LAN)
linux firewall to client (private)

The problem is this:
I do not have control over the router in the LAN side. So any packets going
to 10.166.166.x from the LAN side will be ignored by the router. This is
fine. However, I have eth0 on the Linux firewall configured with 2 IP
addresses - 10.187.7.2 and 10.187.7.3. The first IP acts as the gateway to
the LAN side so all clients on the private-side will use 10.187.7.2 as the
default gateway. What I want is for the 2nd IP to channel packets directly
to an IP in the private side (specifically 10.166.166.2). I can't seem to do
this.

To put it in graphical terms.

Private-side Linux firewall LAN side
Client(#)-----------(&) (*)------($)

(#) = Client's NIC. IP = 10.166.166.2
(&) = eth1. IP = 10.166.166.1
(*) = eth0. IP = 10.187.7.2 and 10.187.7.3
($) = a RJ-45 socket in the wall.

I require a client on the LAN side to open a HTTP connection to 10.187.7.3.
Linux should forward the packets received via 10.187.7.3 specifically to
10.166.166.2 ONLY. 10.166.166.2 will never use 10.187.7.2. 10.187.7.2 is
for all other machines on the private-side OTHER than 10.166.166.2.

Any help??

-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.rutgers.edu