Add support for explicit routing rules -- Add rtrules file to SVN

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@3765 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2006-04-02 15:23:01 +00:00
parent 66c2939d64
commit 4bd4a393ea

57
Shorewall/rtrules Normal file
View File

@ -0,0 +1,57 @@
#
# Shorewall version 3.2 - rtrules File
#
# /etc/shorewall/rtrules
#
# Entries in this file cause traffic to be routed to one of the
# providers listed in /etc/shorewall/providers.
#
# Columns are:
#
# PROVIDER The provider to route the traffic through.
# May be expressed either as the provider name
# or the provider number.
#
# PRIORITY
# The rule's priority which determines the order
# in which the rules are processed.
#
# 1000-1999 Before Shorewall-generated
# 'MARK' rules
#
# 11000- 11999 After 'MARK' rules but before
# Shorewall-generated rules for
# ISP interfaces.
#
# 26000-26999 After ISP interface rules but
# before 'default' rule.
#
# Rules with equal priority are applied in
# the order in which they appear in the file.
#
# SOURCE(optonal) An ip address (network or host) that
# matches the source IP address in a packet.
# May also be specified as an interface
# name optionally followed by ":" and an
# address. If the define 'lo' is specified,
# the packet must originate from the firewall
# itself.
#
# DEST(optional) An ip address (network or host) that
# matches the destination IP address in a packet.
#
# If you choose to omit either SOURCE or DEST,
# place "-" in that column (or you can simply
# leave the DEST column empty). Note that you
# may not omit both SOURCE and DEST.
#
# Example: You want all traffic coming in on eth1 to be routed to the ISP1
# provider:
#
# #PROVIDER PRIORITY SOURCE DEST
# ISP1 1000 eth1
#
# For additional information, see http://www.shorewall.net/MultiISP.html
##############################################################################
#PROVIDER PRIORITY SOURCE DEST
#LAST LINE -- ADD YOUR ENTRIES BEFORE THIS ONE -- DO NOT REMOVE