-
- **Date:** 2023-12-07
- **Resolution:** Open
- **Area:** Network
- **OS:** macOS 14.1.2
- **Type:** Incorrect/Unexpected Behavior
- **Keywords:** sonoma ikev2 ipsec vpn
## Description
Ther…
0x-2a updated
6 months ago
-
As the title says
-
I observed the following behavior while going through a Libreswan tutorial (https://libreswan.org/wiki/VPN_server_for_remote_clients_using_IKEv2):
When you insert a certificate into a NSS database,…
-
VPN connection to Fortigate VPN (IPSEC, ike1, psk, xauth, main) worked fine on Libreswan 4.5, but started to only partially work with Libreswan 4.6. I am connecting by only using libreswan network man…
-
CoCo currently has no first-class support for securing the communication between enclaves. This responsibility has been left to the application, but CoCo could provide this optional feature. This RFC …
-
Hi Freinds
I have setup Openswan server on AWS ec2. I have one VPN configured from AWS to GCP and another Openswan to my on-prem site.
I can ping from GCP to Openswan ec2, similar from my on-prem …
-
**What package is missing from Amazon Linux 2022? Please describe and include package name.**
The strongswan package is missing
**Is this an update to existing package or new package request?**
…
-
So the shift to libreswan is breaking connections that were previously working with IKE1 support.
We've deployed a few clients using an IPSEC server that exposes only ports 500 and 4500, and they'r…
-
Raven now use the Subnet-based configuration of Libreswan to create VPN connections, which is strongly rely on the "One-Subnet-One-Node" supposition. This brings troubles when the CNI implimentation d…
-
I am trying to setup Opportunistic IPsec without concentrator.
Ipsec.example.com - 10.3.96.3
Ipsec2.example.com - 10.3.96.4
Configuration : Ipsec.example.com
setting ip under SAN because of n…