Re: [strongSwan] IPSec / IKEv2, IP-(Re)assignment problem

2019-05-23 Thread Sven Anders
Am 20.05.19 um 14:59 schrieb Tobias Brunner: > Hi Sven, > > You explicitly disabled handling of INITIAL_CONTACT notifies with > uniqueids=never. So existing IKE_SAs with the same client identity will > not be terminated when a new IKE_SA is created, which also means the > existing virtual IP is n

Re: [strongSwan] IPSec / IKEv2, IP-(Re)assignment problem

2019-05-20 Thread Tobias Brunner
Hi Sven, You explicitly disabled handling of INITIAL_CONTACT notifies with uniqueids=never. So existing IKE_SAs with the same client identity will not be terminated when a new IKE_SA is created, which also means the existing virtual IP is not released. Since the same virtual IP can't be assigned

[strongSwan] IPSec / IKEv2, IP-(Re)assignment problem

2019-05-16 Thread Sven Anders
Hello! We are using strongswan to connect iPhones and iPads via IPSec with IKEv2. The authentication and connection works fine. We configured two IP pools: a dynamic and a static pool. The static pool entries look like: 192.168.220.1=john@domainname.com The (first) assignment of the static