extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2025-06-24 19:51:40 +02:00
Code Issues Packages Projects Releases Wiki Activity

Change another IPv4 address to an IPv6 address

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@9117 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2008-12-18 17:20:38 +00:00
parent 1ebd59ccde
commit 3621e5ca1f
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
manpages6/shorewall6-tcrules.xml
View File

@ -257,11 +257,11 @@
names, IP addresses, MAC addresses and/or subnets for packets being names, IP addresses, MAC addresses and/or subnets for packets being
routed through a common path. List elements may also consist of an routed through a common path. List elements may also consist of an
interface name followed by ":" and an address (e.g., interface name followed by ":" and an address (e.g.,
eth1:192.168.1.0/24). For example, all packets for connections eth1:<2002:ce7c:92b4::/48>). For example, all packets for
masqueraded to eth0 from other interfaces can be matched in a single connections masqueraded to eth0 from other interfaces can be matched
rule with several alternative SOURCE criteria. However, a connection in a single rule with several alternative SOURCE criteria. However,
whose packets gets to eth0 in a different way, e.g., direct from the a connection whose packets gets to eth0 in a different way, e.g.,
firewall itself, needs a different rule.</para> direct from the firewall itself, needs a different rule.</para>
<para>Accordingly, use $<emphasis role="bold">FW</emphasis> in its <para>Accordingly, use $<emphasis role="bold">FW</emphasis> in its
own separate rule for packets originating on the firewall. In such a own separate rule for packets originating on the firewall. In such a