[strongSwan] [Strongswan5.0.1]Strongswan is not sending phase2 Identification payload in Ikev1 for IPv6, which leads to negotiation failure
martin at strongswan.org
Tue Dec 18 09:29:18 CET 2012
> In response to quick mode message of IKev1, strongswan is sending a
> quick mode message with no identification payload, which results in
> negotiation failure for transport mode.
If no ID payload is sent, the identities are implicitly the same as the
outer address without any port/protocol restrictions. Have a look at 
for the details.
> Router1 is sending Quick mode message with identification data as
> 2007:1234::4/ffff:ffff:ffff:ffff::, but in response to quick mode,
> strongswan is changing identification data as
> 2007:1234::4/2007:1234::ffff:ffff:ffff:ffff, which results in
> negotiation failure(ID mistmatch).
Instead of sending an ID mismatch error, strongSwan tries to narrow
quick mode IDs, as it is done with IKEv2. This probably won't work with
other implementations, but should not harm as the ID payload wouldn't
These don't look like valid subnet definitions. You can't configure IPv6
prefixes here, but networks in CIDR notation.
More information about the Users