ikev1: Send NAT-D payloads after HASH payloads in Aggressive Mode requests
Some implementations seem to have problems if the third AM message contains NAT-D payloads before the HASH payload. Fixes #2314.
This commit is contained in:
@@ -554,10 +554,10 @@ static payload_order_t aggressive_i_order[] = {
|
|||||||
{PLV1_CERTREQ, 0},
|
{PLV1_CERTREQ, 0},
|
||||||
{PLV1_NOTIFY, 0},
|
{PLV1_NOTIFY, 0},
|
||||||
{PLV1_VENDOR_ID, 0},
|
{PLV1_VENDOR_ID, 0},
|
||||||
|
{PLV1_HASH, 0},
|
||||||
{PLV1_NAT_D, 0},
|
{PLV1_NAT_D, 0},
|
||||||
{PLV1_NAT_D_DRAFT_00_03, 0},
|
{PLV1_NAT_D_DRAFT_00_03, 0},
|
||||||
{PLV1_SIGNATURE, 0},
|
{PLV1_SIGNATURE, 0},
|
||||||
{PLV1_HASH, 0},
|
|
||||||
{PLV1_FRAGMENT, 0},
|
{PLV1_FRAGMENT, 0},
|
||||||
};
|
};
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user