Hi Jan, > Why does charon suddently pick a different address than the requested > one? Above all, 1.0.0.9 is already assigned.
The in-memory pool did not handle multiple leases for the same identity correctly. This might result in somewhat undefined behavior if the same identity connected twice. > What I would really like is that (x509_name, source_ip_address, > source_port) creates the unique tuple, and not just the x509_name. I recently have reimplemented the in-memory pool to handle multiple leases correctly. Two peers with the same identity behind NAT should get their own address now. You may pick up the patch at [1]. Regards Martin [1]http://git.strongswan.org/?p=strongswan.git;a=commitdiff;h=e82186fb5acf796c9a3a387f918e734e9611be76 _______________________________________________ Users mailing list [email protected] https://lists.strongswan.org/mailman/listinfo/users
