[strongSwan] Export XFRM StrongSwan / IPSec routes to Quagga (OSPF)

Noel Kuntze noel.kuntze+strongswan-users-ml at thermi.consulting
Sun Oct 25 21:59:37 CET 2020


Hi Tom,

The routes in table 220 are only used to tell the kernel which source IP to use for sending packets to a remote network.
They aren't part of XFRM and only tangentially pertain IPsec.
Also, routes are only added if they are required, so those routes in table 220 are not necessarily complete.

A better solution for your use case would be to use route based IPsec by using dedicated VTIs or XFRM interfaces and running OSPF/BGP/whatever over those virtual links.

Kind regards

Noel

Am 25.10.20 um 19:05 schrieb TomK:
> Hey All,
> 
> I'm interested in finding out how to import routes from StrongSwan IPSec installed XFRM tables (220) into Quagga (OSPF, 254)?
> 
> The XFRM policy based rules are saved in table 220 while Quagga (OSPF) saves the routes in table 254.  I have an IPSec StrongSwan on-prem GW paired up with one of the Cloud providers.  The connection is established fine however I can't ping the remote VLAN's from any other device on the on-prem network except from the on-prem GW itself.
> 
> I would like to make OSPF aware of table 220 so it can import the rules.  Or at least find another way to export the rules in table 220 and into table 254.  Either import from or export to would work but I haven't been able to find articles on the web addressing this issue.
> 
> Is this possible?
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.strongswan.org/pipermail/users/attachments/20201025/dda468ef/attachment.sig>


More information about the Users mailing list