editor
698
edits
L2TP Client: FireBrick: Difference between revisions
→FireBrick FB2500/2700 Fully Loaded: 2900 can do it too
(→top: clean up) |
(→FireBrick FB2500/2700 Fully Loaded: 2900 can do it too) |
||
| (One intermediate revision by the same user not shown) | |||
|
__NOTOC__<indicator name="L2TP">[[File:Menu-L2TP.svg|link=:Category:Incoming L2TP|30px|Back up to the Incoming L2TP Category]]</indicator>
[[Category:Incoming L2TP]]
== FireBrick FB2500/
The FireBrick can connect as an L2TP client for fallback and for its main connection. One thing to watch out for is making sure that the FB doesn't set its own gateway to be the tunnel (which would logically send tunnel packets up the tunnel, which is horrid). You can get around this by using separate routing tables.
This example is for L2TP being the main connection:
<syntaxhighlight lang="xml">
<interface name="WAN"
port="WAN1"
comment="L2TP tunnel to AAISP"/>
</l2tp>
</syntaxhighlight>
You can set to fall back to NAT if the tunnel is down. Traffic on routing table 0 won't have a default gateway if the L2TP is down, so will match this rule set that has target interface "nowhere":
<syntaxhighlight lang="xml">
<rule-set name="Fallback"
target-interface="nowhere"
action="accept"/>
</rule-set>
</syntaxhighlight>
If the L2TP is being used for fallback, you are probably better off setting the routing table for the L2TP to something other than 0. Remember firewall rules only apply to single routing tables. You can then use profiles to bring the L2TP in to service in the even of the PPP going down etc.
| |||