editor
706
edits
IPsec Firewall: Difference between revisions
→top: clean up
mNo edit summary |
(→top: clean up) |
||
| (2 intermediate revisions by 2 users not shown) | |||
|
<indicator name="Tunnels">[[File:Menu-IPsec.svg|link=:Category:
If there is no NAT involved, you need:
*UDP port 500 for the IKE control channel
*IP protocol ESP (50) for the data channel.
Example:
<syntaxhighlight lang=xml>
<rule-set name="IPsec" source-interface="pppoe" target-interface="self" no-match-action="continue" comment="Non-NATed IPsec connections from PPP to the Brick">
<rule name="IKE" target-port="500" protocol="17" action="accept" comment="Internet Key Exchange"/>
The config force-NAT option [Note the capitalisation ] can be used to force IKE to treat the connection as if it was NATed. This is in the top-level ipsec-ike config item and you need "Show all" on the UI.
Example:
<syntaxhighlight lang=xml>▼
▲<syntaxhighlight>
<rule-set name="IPsec" source-interface="pppoe" target-interface="self" no-match-action="continue" comment="Allow NATed IPsec connections from PPP to the Brick">
<rule name="IKE" target-port="500 4500" protocol="17" action="accept" comment="Internet Key Exchange"/>
</syntaxhighlight>
You can join the two rules to create a set that will work for NAT and
Example:
<syntaxhighlight lang=xml>
<rule-set name="IPsec" source-interface="pppoe" target-interface="self" no-match-action="continue" comment="Allow NATed and Non-NATed IPsec connections from PPP to the Brick">
<rule name="IKE" target-port="500 4500" protocol="17" action="accept" comment="Internet Key Exchange"/>
</syntaxhighlight>
[[Category:
| |||