extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2025-02-18 02:31:11 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update TRACK_PROVIDER description in the man pages.

Browse Source 
Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
Tom Eastep 2010-01-14 08:36:22 -08:00
parent 45d975cb45
commit 25d433b36f
2 changed files with 22 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
manpages/shorewall.conf.xml
View File

@ -1521,16 +1521,16 @@ net all DROP info</programlisting>then the chain name is 'net2all'
Previously, when TC_EXPERT=No, packets arriving through 'tracked' Previously, when TC_EXPERT=No, packets arriving through 'tracked'
provider interfaces were unconditionally passed to the PREROUTING provider interfaces were unconditionally passed to the PREROUTING
tcrules. This was done so that tcrules could reset the packet mark tcrules. This was done so that tcrules could reset the packet mark
to zero so that the packet would be routed using the 'main' routing to zero, thus allowing the packet to be routed using the 'main'
table. Using the main table allowed dynamic routes (such as those routing table. Using the main table allowed dynamic routes (such as
added for VPNs) to be effective. The route_rules file was created to those added for VPNs) to be effective. The route_rules file was
provide a better alternative to clearing the packet mark. As a created to provide a better alternative to clearing the packet mark.
consequence, passing these packets to PREROUTING complicates things As a consequence, passing these packets to PREROUTING complicates
without providing any real benefit. Beginning with Shorewall 4.4.6, things without providing any real benefit. Beginning with Shorewall
when TRACK_PROVIDERS=Yes and TC_EXPERT=No, packets arriving through 4.4.6, when TRACK_PROVIDERS=Yes and TC_EXPERT=No, packets arriving
'tracked' interfaces will not be passed to the PREROUTING rules. through 'tracked' interfaces will not be passed to the PREROUTING
Since TRACK_PROVIDERS was just introduced in 4.4.3, this change rules. Since TRACK_PROVIDERS was just introduced in 4.4.3, this
should be transparent to most, if not all, users.</para> change should be transparent to most, if not all, users.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>

22
manpages6/shorewall6.conf.xml
View File

@ -1307,16 +1307,18 @@ net all DROP info</programlisting>then the chain name is 'net2all'
Previously, when TC_EXPERT=No, packets arriving through 'tracked' Previously, when TC_EXPERT=No, packets arriving through 'tracked'
provider interfaces were unconditionally passed to the PREROUTING provider interfaces were unconditionally passed to the PREROUTING
tcrules. This was done so that tcrules could reset the packet mark tcrules. This was done so that tcrules could reset the packet mark
to zero so that the packet would be routed using the 'main' routing to zero, thus allowing the packet to be routed using the 'main'
table. Using the main table allowed dynamic routes (such as those routing table. Using the main table allowed dynamic routes (such as
added for VPNs) to be effective. The route_rules file was created to those added for VPNs) to be effective. The <ulink
provide a better alternative to clearing the packet mark. As a url="shorewall6-route_rules.html">shorewall6-route_rules</ulink>(5)
consequence, passing these packets to PREROUTING complicates things file was created to provide a better alternative to clearing the
without providing any real benefit. Beginning with Shorewall 4.4.6, packet mark. As a consequence, passing these packets to PREROUTING
when TRACK_PROVIDERS=Yes and TC_EXPERT=No, packets arriving through complicates things without providing any real benefit. Beginning
'tracked' interfaces will not be passed to the PREROUTING rules. with Shorewall 4.4.6, when TRACK_PROVIDERS=Yes and TC_EXPERT=No,
Since TRACK_PROVIDERS was just introduced in 4.4.3, this change packets arriving through 'tracked' interfaces will not be passed to
should be transparent to most, if not all, users.</para> the PREROUTING rules. Since TRACK_PROVIDERS was just introduced in
4.4.3, this change should be transparent to most, if not all,
users.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>