1SHOREWALL-PROVIDERS(5) [FIXME: manual] SHOREWALL-PROVIDERS(5)
2
6 providers - Shorewall Providers file
7
9 /etc/shorewall/providers
10
12 This file is used to define additional routing tables. You will want to
13 define an additional table if:
14 · You have connections to more than one ISP or multiple connections
16 to the same ISP
17 · You run Squid as a transparent proxy on a host other than the
19 firewall.
20 · You have other requirements for policy routing.
22 Each entry in the file defines a single routing table.
24 If you wish to omit a column entry but want to include an entry in the
26 next column, use "-" for the omitted entry.
27 The columns in the file are as follows.
29 NAME - name
31 The provider name. Must be a valid shell variable name. The names
32 'local', 'main', 'default' and 'unspec' are reserved and may not be
33 used as provider names.
34 NUMBER - number
36 The provider number -- a number between 1 and 15. Each provider
37 must be assigned a unique value.
38 MARK (Optional) - value
40 A FWMARK value used in your shorewall-tcrules(5)[1] file to direct
41 packets to this provider.
42 If HIGH_ROUTE_MARKS=Yes in shorewall.conf(5)[2], then the value
44 must be a multiple of 256 between 256 and 65280 or their
45 hexadecimal equivalents (0x0100 and 0xff00 with the low-order byte
46 of the value being zero). Otherwise, the value must be between 1
47 and 255. Each provider must be assigned a unique mark value. This
48 column may be omitted if you don't use packet marking to direct
49 connections to a particular provider and you don't specify track in
50 the OPTIONS column.
51 DUPLICATE - routing-table-name
53 The name of an existing table to duplicate to create this routing
54 table. May be main or the name of a previously listed provider. You
55 may select only certain entries from the table to copy by using the
56 COPY column below. This column should contain a dash ("-') when
57 USE_DEFAULT_RT=Yes in shorewall.conf(5)[2].
58 INTERFACE - interface[:address]
60 The name of the network interface to the provider. Must be listed
61 in shorewall-interfaces(5)[3]. In general, that interface should
62 not have the proxyarp option specified unless loose is given in the
63 OPTIONS column of this entry.
64 Where more than one provider is serviced through a single
66 interface, the interface must be followed by a colon and the IP
67 address of the interface that is supplied by the associated
68 provider.
69 GATEWAY - {-|address|detect}
71 The IP address of the provider's gateway router.
72 You can enter "detect" here and Shorewall will attempt to detect
74 the gateway automatically.
75 For PPP devices, you may omit this column.
77 OPTIONS (Optional) - [-|option[,option]...]
79 A comma-separated list selected from the following. The order of
80 the options is not significant but the list may contain no embedded
81 whitespace.
82 track
84 If specified, inbound connections on this interface are to be
85 tracked so that responses may be routed back out this same
86 interface.
87 You want to specify track if internet hosts will be connecting
89 to local servers through this provider.
90 Beginning with Shorewall 4.4.3, track defaults to the setting
92 of the TRACK_PROVIDERS option in shorewall.conf[2] (5). If you
93 set TRACK_PROVIDERS=Yes and want to override that setting for
94 an individual provider, then specify notrack (see below).
95 balance[=weight]
97 The providers that have balance specified will get outbound
98 traffic load-balanced among them. By default, all interfaces
99 with balance specified will have the same weight (1). You can
100 change the weight of an interface by specifying balance=weight
101 where weight is the weight of the route out of this interface.
102 loose
104 Shorewall normally adds a routing rule for each IP address on
105 an interface which forces traffic whose source is that IP
106 address to be sent using the routing table for that interface.
107 Setting loose prevents creation of such rules on this
108 interface.
109 notrack
111 Added in Shorewall 4.4.3. When specified, turns off track.
112 optional (deprecated)
114 If the interface named in the INTERFACE column is not up and
115 configured with an IPv4 address then ignore this provider. If
116 not specified, the value of the optional option for the
117 INTERFACE in shorewall-interfaces(5)[3] is assumed. Use of that
118 option is preferred to this one.
119 src=source-address
121 Specifies the source address to use when routing to this
122 provider and none is known (the local client has bound to the 0
123 address). May not be specified when an address is given in the
124 INTERFACE column. If this option is not used, Shorewall
125 substitutes the primary IP address on the interface named in
126 the INTERFACE column.
127 mtu=number
129 Specifies the MTU when forwarding through this provider. If not
130 given, the MTU of the interface named in the INTERFACE column
131 is assumed.
132 fallback[=weight]
134 Indicates that a default route through the provider should be
135 added to the default routing table (table 253). If a weight is
136 given, a balanced route is added with the weight of this
137 provider equal to the specified weight. If the option is given
138 without a weight, an separate default route is added through
139 the provider's gateway; the route has a metric equal to the
140 provider's NUMBER. The option is ignored with a warning message
141 if USE_DEFAULT_RT=Yes in shorewall.conf.
142 COPY - [{none|interface[,interface]...}]
144 A comma-separated list of other interfaces on your firewall.
145 Wildcards specified using an asterisk ("*") are permitted (e.g.,
146 tun* ). Usually used only when DUPLICATE is main. Only copy routes
147 through INTERFACE and through interfaces listed here. If you only
148 wish to copy routes through INTERFACE, enter none in this column.
149
151 Example 1:
152 You run squid in your DMZ on IP address 192.168.2.99. Your DMZ
153 interface is eth2
154 #NAME NUMBER MARK DUPLICATE INTERFACE GATEWAY OPTIONS
156 Squid 1 1 - eth2 192.168.2.99 -
157 Example 2:
159 eth0 connects to ISP 1. The IP address of eth0 is 206.124.146.176
160 and the ISP's gateway router has IP address 206.124.146.254.
161 eth1 connects to ISP 2. The IP address of eth1 is 130.252.99.27 and
163 the ISP's gateway router has IP address 130.252.99.254.
164 eth2 connects to a local network.
166 #NAME NUMBER MARK DUPLICATE INTERFACE GATEWAY OPTIONS COPY
168 ISP1 1 1 main eth0 206.124.146.254 track,balance eth2
169 ISP2 2 2 main eth1 130.252.99.254 track,balance eth2
170
172 /etc/shorewall/providers
173
175 http://shorewall.net/MultiISP.html
176 shorewall(8), shorewall-accounting(5), shorewall-actions(5),
178 shorewall-blacklist(5), shorewall-hosts(5), shorewall_interfaces(5),
179 shorewall-ipsets(5), shorewall-maclist(5), shorewall-masq(5),
180 shorewall-nat(5), shorewall-netmap(5), shorewall-params(5),
181 shorewall-policy(5), shorewall-proxyarp(5), shorewall-route_rules(5),
182 shorewall-routestopped(5), shorewall-rules(5), shorewall.conf(5),
183 shorewall-secmarks(5), shorewall-tcclasses(5), shorewall-tcdevices(5),
184 shorewall-tcrules(5), shorewall-tos(5), shorewall-tunnels(5),
185 shorewall-zones(5)
186
188 1. shorewall-tcrules(5)
189 http://www.shorewall.net/manpages/shorewall-tcrules.html
190 2. shorewall.conf(5)
192 http://www.shorewall.net/manpages/shorewall.conf.html
193 3. shorewall-interfaces(5)
195 http://www.shorewall.net/manpages/shorewall-interfaces.html
196[FIXME: source] 09/16/2011 SHOREWALL-PROVIDERS(5)