/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! 
/* ALSO: Don't quote this header. It makes you look lame :-) */

On Tue, Jul 02, 2002 at 09:46:43AM +0100 or so it is rumoured hereabouts, 
Moore, Paul thought:
> 
> > Here are the basics of what you would need to do. Make
> > sure that the system you are going to use as the gateway
> > to the client's network/system, lets call this machine
> > CG (client gateway) can indeed connect to the client's
> > network/system. Arrange for all desired internal machines
> > to have a route(s) added that list the CG as their gateway
> > to the clients network. Then on the CG system, configure
> > iptables (or ipchains) to NAT/MASQ all traffic from the
> > internal machines to the client network.

As I understand it, it may be necessary to set the route to this network
*only* on the LAN's _current_ default gateway.  

eg.  If each machine has a default route of 192.168.1.254 (the internet
router) and your linux masq box is on 192.168.1.250, instead of creating a
route entry for each machine in your network, just create a route entry on
192.168.1.254 pointing to 192.168.1.250 as the route to the clinet's LAN.

Though, now that I think further, that will route the masqued traffic back
to the linux box repeatedly won't it?

Conor
-- 
Conor Daly <[EMAIL PROTECTED]>

Domestic Sysadmin :-)
---------------------
Faenor.cod.ie
 10:41pm  up 41 days,  7:58,  0 users,  load average: 0.00, 0.00, 0.00
Hobbiton.cod.ie
 10:33pm  up 14 days, 21:55,  1 user,  load average: 0.04, 0.06, 0.02
_______________________________________________
Masq maillist  -  [EMAIL PROTECTED]
Admin requests can be handled at http://www.indyramp.com/masq-list/ -- 
THIS INCLUDES UNSUBSCRIBING!
or email to [EMAIL PROTECTED]

PLEASE read the HOWTO and search the archives before posting.
You can start your search at http://www.indyramp.com/masq/
Please keep general linux/unix/pc/internet questions off the list.

Reply via email to