extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2024-12-23 06:38:53 +01:00
Code Issues Packages Projects Releases Wiki Activity

Add some additional links in the tcrules manpage

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@5256 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2007-01-18 16:35:59 +00:00
parent e0ae817cab
commit 05bc4bb7e4
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
manpages/shorewall-tcrules.xml
View File

@ -32,8 +32,8 @@
matches.</para>
<para>If you use multiple internet providers with the 'track' option, in
/etc/shorewall/providers be sure to read the restrictions at
http://shorewall.net/MultiISP.html.</para>
/etc/shorewall/providers be sure to read the restrictions at <ulink
url="http://shorewall.net/MultiISP.html">http://shorewall.net/MultiISP.html</ulink>.</para>
</important>
<para>The columns in the file are as follows.</para>
@ -70,12 +70,14 @@
in your kernel and iptables; neither may be used with connection
marks (see below).</para>
<para>If HIGH_ROUTE_MARKS=Yes in shorewall.conf then you may
<para>If HIGH_ROUTE_MARKS=Yes in <ulink
url="shorewall.conf.html">shorewall.conf</ulink>(5) then you may
also specify a value in the range 0x0100-0xFF00 with the
low-order byte being zero. Such values may only be used in the
PREROUTING chain(value followed by <emphasis
role="bold">:F</emphasis> or you have set
MARK_IN_FORWARD_CHAIN=Yes in shorewall conf and have not
MARK_IN_FORWARD_CHAIN=Yes in <ulink
url="shorewall.conf.html">shorewall.conf</ulink>(5) and have not
followed the value with :P) or the OUTPUT chain (SOURCE is
<emphasis role="bold">$FW</emphasis>).</para>