FireBrick Road Warrior strongSwan: Difference between revisions

(23 intermediate revisions by 3 users not shown)

Line 1:

<indicator name="RoadW">[[File:Menu-Road-Warrior.svg|link=:Category:~~FireBrick_IPsec_Road_Warrior~~|30px|Back up to the FireBrick Road Warrior Category Page]]</indicator>

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

'''FireBrick acting as the ipsec 'server', and configuring a strongSwan/Debian client.'''

⚫

This example uses strongSwan on Debian, but the config would suit other ~~flavors~~ once you've installed the package(s).

⚫

This example uses strongSwan on Debian, but the config would suit other flavours once you've installed the package(s).

See also: [[FireBrick to Openswan Strongswan IPsec (Howto)]]

==Install Packages==

$ sudo apt-get install strongswan libcharon-extra-plugins

You may also want <tt>libstrongswan-extra-plugins</tt> if you need the curl plugin for strongswan to fetch CA certificates (eg from Let's Encrypt).

⚫

libcharon-extra-plugins is needed for the eap-identity plugin which is required to connect to the FireBrick. The plugin is loaded automatically, so you don't need to change any config files (normally you'd have to change the "load =" statement in strongswan.conf).

⚫

<tt>libcharon-extra-plugins</tt> is needed for the eap-identity plugin which is required to connect to the FireBrick. The plugin is loaded automatically, so you don't need to change any config files (normally you'd have to change the "load =" statement in strongswan.conf).

⚫

==Certificate==

⚫

==CA Certificate==

⚫

Download your CA certificate, and copy to /etc/ipsec.d/cacerts/ on your client box. Strongswan shouldn't mind if PEM or DER.

Usually you can use ACME and Letsencrypt to assign a certificate to the FireBrick, so skip the next step if you're doing this.

⚫

If using a manually creates certificate, Download your CA certificate from the FireBrick, and copy to <tt>/etc/ipsec.d/cacerts/</tt> on your client box. Strongswan shouldn't mind if PEM or DER.

If you're using a Let's Encrypt cert on the FireBrick (which is easy) - you'll need to symlink the system CA:

ln -s /etc/ssl/certs/ISRGRootX1.pem /etc/ipsec.d/cacerts/ISRGRootX1.pem

==strongSwan Config==

Line 20:

Line 31:

Add your connection to /etc/ipsec.conf:

conn ~~username~~ # Arbitrary name - doesn't have to be ~~username~~

conn firebrick # Arbitrary name - doesn't have to be 'firebrick'

left=%defaultroute # Use your default route to the internet

leftfirewall=yes # Yes as you may be behind firewall/NAT

leftauth=eap-mschapv2 # Match the EAP method defined on FireBrick

leftid=@peer-ID # Peer ID as defined in FB IPsec IKE setting

leftsourceip=%config # Ask for an IP from the roaming pool

eap_identity=username # Username as in ipsec.secrets and FB config

right=hostname.example.com # Hostname/IP of FireBrick

rightauth=pubkey # FireBrick should be set to auth-method Certificate

rightid=@hostname.example.com # ID of FireBrick

auto=~~start~~ # Try to connect ~~immediately~~ on startup

auto=route # Try to connect on startup

</syntaxhighlight>

If the FireBrick is configured to give an IPv6 address in the Roaming pool, then tell strongSwan to request IPv6 too:

leftsourceip=%config4,%config6

</syntaxhighlight>

Line 46:

Line 62:

Here's some StrongSwan info on split tunnelling: https://wiki.strongswan.org/projects/strongswan/wiki/ForwardingAndSplitTunneling

You use leftsubnet on the strongSwan roadwarrior to determine whether to use the tunnel as default gateway - you'd need leftsubnet=0.0.0.0/0 to ensure all traffic used the tunnel, and leftsubnet=<serverLAN> for split tunnelling.

You use <tt>leftsubnet</tt> on the strongSwan roadwarrior to determine whether to use the tunnel as default gateway - you'd need <tt>leftsubnet=0.0.0.0/0</tt> to ensure all traffic used the tunnel, and <tt>leftsubnet=<serverLAN></tt> for split tunnelling.

For example:

leftsourceip=%config4,%config6

rightsubnet=0.0.0.0/0,::/0

</syntaxhighlight>

If you want to route additional blocks via the tunnel, use rightsubnet, eg:

⚫

[[Category:~~FireBrick_IPsec_Road_Warrior~~|Debian]]

rightsubnet=10.1.0.0/24,10.2.0.0/24,fd00:1::/64,fd00:1::/64 # IPs to route down tunnel

</syntaxhighlight>

== Further help==

ipsec up <username> # manually attempt to bring up the connection - look for errors

ipsec listcacerts # check if your cert is loaded

ipsec statusall

⚫

[[Category:FireBrick IPsec Road Warrior|Debian]]