From 3621e5ca1f257338975aeb9ca36c71b1174b2199 Mon Sep 17 00:00:00 2001 From: teastep Date: Thu, 18 Dec 2008 17:20:38 +0000 Subject: [PATCH] Change another IPv4 address to an IPv6 address git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@9117 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb --- manpages6/shorewall6-tcrules.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/manpages6/shorewall6-tcrules.xml b/manpages6/shorewall6-tcrules.xml index 2030e4496..f0b894e69 100644 --- a/manpages6/shorewall6-tcrules.xml +++ b/manpages6/shorewall6-tcrules.xml @@ -257,11 +257,11 @@ names, IP addresses, MAC addresses and/or subnets for packets being routed through a common path. List elements may also consist of an interface name followed by ":" and an address (e.g., - eth1:192.168.1.0/24). For example, all packets for connections - masqueraded to eth0 from other interfaces can be matched in a single - rule with several alternative SOURCE criteria. However, a connection - whose packets gets to eth0 in a different way, e.g., direct from the - firewall itself, needs a different rule. + eth1:<2002:ce7c:92b4::/48>). For example, all packets for + connections masqueraded to eth0 from other interfaces can be matched + in a single rule with several alternative SOURCE criteria. However, + a connection whose packets gets to eth0 in a different way, e.g., + direct from the firewall itself, needs a different rule. Accordingly, use $FW in its own separate rule for packets originating on the firewall. In such a