L2TP Client: FireBrick: Difference between revisions
Content deleted Content added
→FireBrick FB2500/2700 Fully Loaded: syntax highlight! |
mNo edit summary |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
__NOTOC__<indicator name="L2TP">[[File:Menu-L2TP.svg|link=:Category:Incoming L2TP|30px|Back up to the Incoming L2TP Category]]</indicator> |
__NOTOC__<indicator name="L2TP">[[File:Menu-L2TP.svg|link=:Category:Incoming L2TP|30px|Back up to the Incoming L2TP Category]]</indicator> |
||
[[Category:Incoming L2TP]] |
[[Category:Incoming L2TP]] |
||
== FireBrick FB2500/ |
== FireBrick FB2500/FB2700/FB2900 Fully Loaded == |
||
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. |
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. |
||
| Line 16: | Line 16: | ||
<outgoing name="AAISP" |
<outgoing name="AAISP" |
||
hostname="AAISP" |
hostname="AAISP" |
||
server="l2tp.aa.net.uk" |
|||
graph="AAISP" |
graph="AAISP" |
||
table="1" |
table="1" |
||