userdoc:tt_ipsec_vpn_strongswan

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
userdoc:tt_ipsec_vpn_strongswan [2020/12/04 14:05]
abelbeck [IPsec VPN (strongSwan) Configuration] 		userdoc:tt_ipsec_vpn_strongswan [2020/12/09 10:33]
abelbeck [IPsec VPN (strongSwan) Configuration]
Line 15: Line 15:
 How does this apply within AstLinux ... How does this apply within AstLinux ...
  
-  * It is clear to the development team that we can't "switch" to strongSwan, at least for now, we need to understand strongSwan better, plus a point-and-click web interface like our current IPsec Peers / IPsec Mobile would limit strongSwan features.+  * A point-and-click web interface like the deprecated IPsec Peers / IPsec Mobile would limit strongSwan features.
   * strongSwan is needed to support endpoints with changing IP's and dynamic DNS names using IKEv2 MOBIKE, racoon only supports IKEv1.   * strongSwan is needed to support endpoints with changing IP's and dynamic DNS names using IKEv2 MOBIKE, racoon only supports IKEv1.
   * strongSwan is needed to interoperate with [[https://en.avm.de/products/fritzbox/|AVM FRITZ!Box]]((Quality home routers/PBX, used by many ISPs. Good support from the vendor.)) routers, very common in Germany and other parts of Europe.   * strongSwan is needed to interoperate with [[https://en.avm.de/products/fritzbox/|AVM FRITZ!Box]]((Quality home routers/PBX, used by many ISPs. Good support from the vendor.)) routers, very common in Germany and other parts of Europe.
  • userdoc/tt_ipsec_vpn_strongswan.txt
  • Last modified: 2021/03/02 08:11
  • by abelbeck