Network Operation Center wrote: > Hi > > i am search a solution for masquera all ip of my network. > > I have 1 Linux server with Shorewall 3.2.1. > with: > eth1 192.168.11.254 > eth1:1 192.168.1.253 > > 192.168.2.0 192.168.1.254 255.255.255.0 UG 0 0 0 eth1 > 192.168.18.0 192.168.11.253 255.255.255.0 UG 10 0 0 eth1 > > no problemes, 192.168.1 and 192.168.11 can ping 192.168.18.X > > But my problems that 192.168.18.0 know a another network in 192.168.2.0 > not based on my network. > > I want create a new IP: 192.168.3.0/24, on 192.168.18.0 router put a route > 192.168.3.0/24 to 192.168.1.253 > > and on my linux router put a masq: > > 192.168.3.1 = 192.168.2.1 > 192.168.3.2 = 192.168.2.2 > <..> > > and when a user in 192.168.18 want access to 192.168.2, he put 192.168.3 > and when a user of 192.168.2 want access to 192.168.18,my linux router > change automatiquely 192.168.2.X in 192.168.3.X for the 192.168.18 can > answer. > > It's possible ? > It's in /etc/shorewall/masq ?
See http://www.shorewall.net/netmap.html -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
