holm/shorewall_code
1
0
Fork 0
forked from extern/shorewall_code
Code Pull Requests Activity

Add comment to masq file regarding multi-ISP

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@3009 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2005-11-16 17:08:09 +00:00
parent 34dbd6ef28
commit 76929fb432
5 changed files with 24 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
Samples/three-interfaces/masq
View File

@ -6,6 +6,11 @@
# Use this file to define dynamic NAT (Masquerading) and to define
# Source NAT (SNAT).
#
# WARNING: If you have more than one ISP, adding entries to this
# file will *not* force connections to go out through a particular
# ISP. You must use PREROUTING entries in /etc/shorewall/tcrules
# to do that.
#
# Columns are:
#
# INTERFACE -- Outgoing interface. This is usually your internet

5
Samples/two-interfaces/masq
View File

@ -6,6 +6,11 @@
# Use this file to define dynamic NAT (Masquerading) and to define
# Source NAT (SNAT).
#
# WARNING: If you have more than one ISP, adding entries to this
# file will *not* force connections to go out through a particular
# ISP. You must use PREROUTING entries in /etc/shorewall/tcrules
# to do that.
#
# Columns are:
#
# INTERFACE -- Outgoing interface. This is usually your internet

2
Shorewall/changelog.txt
View File

@ -7,6 +7,8 @@ Changes in 3.0.1
3) Add Farkas ordering to generated SOURCE and DEST column when expanding
macros.
4) Clarify PORTS column in blacklist file.
Changes in 3.0.0 Final
None.

11
Shorewall/masq
View File

@ -6,6 +6,11 @@
# Use this file to define dynamic NAT (Masquerading) and to define
# Source NAT (SNAT).
#
# WARNING: If you have more than one ISP, adding entries to this
# file will *not* force connections to go out through a particular
# ISP. You must use PREROUTING entries in /etc/shorewall/tcrules
# to do that.
#
# Columns are:
#
# INTERFACE -- Outgoing interface. This is usually your internet
@ -80,7 +85,7 @@
# a port range with the format <low port>-
# <high port>. If this is done, you must
# specify "tcp" or "udp" in the PROTO column.
#
#
# Examples:
#
# 192.0.2.4:5000-6000
@ -117,12 +122,12 @@
# /etc/services) separated by commas or you
# may list a single port range
# (<low port>:<high port>).
#
#
# Where a comma-separated list is given, your
# kernel and iptables must have multiport match
# support and a maximum of 15 ports may be
# listed.
#
#
# IPSEC -- (Optional) If you specify a value other than "-" in this
# column, you must be running kernel 2.6 and
# your kernel and iptables must include policy

4
Shorewall/releasenotes.txt
View File

@ -13,6 +13,10 @@ Problems Corrected in 3.0.1
("-") appeared in the corresponding column of an invocation of that
macro, then an invalid rule was generated.
4) The comments in the /etc/shorewall/blacklist file have been updated to
clarify that the PORTS column refers to destination port number/service
names.
New Features in 3.0.1
1) To make the macro facility more flexible, Shorewall now examines the