Tom Eastep wrote: > Network Operation Center wrote: >> ok, no other solution ? i can map ip per ip ? > > Did you read the last section of http://www.shorewall.net/netmap.html? > > As I mention in that section, I think that it can be done with a combination > of NETMAP and policy routing but I haven't tried to sit down a work out how > to do it exactly.
I would start with: /etc/shorewall/netmap: SNAT 192.168.2.0/24 eth1 192.168.3.0/24 DNAT 192.168.3.0/24 eth1 192.168.2.0/24 /etc/shorewall/tcrules: 1:P 192.168.2.0/24 192.168.3.0/24 /etc/shorewall/providers: #NAME NUMBER MARK DUPLICATE INTERFACE GATEWAY OPTIONS COPY map 1 1 - eth1 192.168.11.253 And be sure that routefiltering is turned off on eth1. -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
