FireBrick to FireBrick IPsec (Howto): Difference between revisions

Line 1:

<indicator name="Tunnels">[[File:Menu-IPsec.svg|link=:Category:~~FireBrick_IPsec~~|30px|Back up to the FireBrick IPsec Tunnels Category Page]]</indicator>

<indicator name="Tunnels">[[File:Menu-IPsec.svg|link=:Category:FireBrick IPsec|30px|Back up to the FireBrick IPsec Tunnels Category Page]]</indicator>

Here we will use an IPsec tunnel between two FireBricks. We will use IKEv2 and use a preshared-secret password.

Line 7:

Do read the official FireBrick manuals for more information - this is just a simple howto covering the basics.

==Network Overview:==

==Network Overview==

{| class="wikitable"

Line 33:

</syntaxhighlight>

If you firewall WAN to 'Self' (The FireBrick), then a firewall filter may be needed too, eg:

If you firewall WAN to 'Self' (The FireBrick), then a firewall filter may be needed too, e.g.:

Line 39:

</syntaxhighlight>

You will also want to add firewall rules to allow traffic between the two LANs, eg, this will allow all traffic to and from Reading and will not NAT the traffic:

You will also want to add firewall rules to allow traffic between the two LANs, e.g., this will allow all traffic to and from Reading and will not NAT the traffic:

Line 57:

</syntaxhighlight>

If you firewall WAN to 'Self' (The Firebrick), then a firewall filter may be needed too, eg:

If you firewall WAN to 'Self' (The Firebrick), then a firewall filter may be needed too, e.g.:

Line 63:

</syntaxhighlight>

You will also want to add firewall rules to allow traffic between the two LANs, eg, this will allow all traffic to and from London and will not NAT the traffic:

You will also want to add firewall rules to allow traffic between the two LANs, e.g., this will allow all traffic to and from London and will not NAT the traffic:

Line 73:

This rule actually allows all traffic from all IPSec connections - so do edit to suit your environment.

[[Category:~~FireBrick_IPsec~~|FireBrick]]

[[Category:FireBrick IPsec|FireBrick]]