some changes to the ikev2/nat-two-rw-mark scenario
This commit is contained in:
@@ -5,8 +5,10 @@ after ESP decryption to map these subnets to 10.3.0.10 and 10.3.0.20, respective
|
|||||||
<p/>
|
<p/>
|
||||||
In order to differentiate between the tunnels to <b>alice</b> and <b>venus</b>, respectively,
|
In order to differentiate between the tunnels to <b>alice</b> and <b>venus</b>, respectively,
|
||||||
<b>XFRM marks</b> are defined for both the inbound and outbound IPsec SAs and policies using
|
<b>XFRM marks</b> are defined for both the inbound and outbound IPsec SAs and policies using
|
||||||
the <b>mark=</b> ipsec.conf parameter. <b>iptables -t mangle</b> rules are then used in the PREROUTING
|
the <b>mark</b> parameter in ipsec.conf.
|
||||||
chain to mark the traffic to and from <b>alice</b> and <b>venus</b>, respectively.
|
<p/>
|
||||||
|
<b>iptables -t mangle</b> rules are then used in the PREROUTING chain to mark the traffic to
|
||||||
|
and from <b>alice</b> and <b>venus</b>, respectively.
|
||||||
<p/>
|
<p/>
|
||||||
<b>leftfirewall=yes</b> automatically inserts iptables-based firewall rules that let pass
|
<b>leftfirewall=yes</b> automatically inserts iptables-based firewall rules that let pass
|
||||||
the tunneled traffic. In order to test the tunnel, the NAT-ed hosts <b>alice</b> and <b>venus</b>
|
the tunneled traffic. In order to test the tunnel, the NAT-ed hosts <b>alice</b> and <b>venus</b>
|
||||||
|
|||||||
@@ -6,6 +6,4 @@ venus::/etc/init.d/iptables stop 2> /dev/null
|
|||||||
sun::/etc/init.d/iptables stop 2> /dev/null
|
sun::/etc/init.d/iptables stop 2> /dev/null
|
||||||
moon::iptables -t nat -F
|
moon::iptables -t nat -F
|
||||||
moon::conntrack -F
|
moon::conntrack -F
|
||||||
sun::iptables -t mangle -F
|
|
||||||
sun::iptables -t nat -F
|
|
||||||
sun::conntrack -F
|
sun::conntrack -F
|
||||||
|
|||||||
Reference in New Issue
Block a user