03-20-2025 02:57 PM
We have noticed on the ASA that the IKE parameters are declared in a Global list.
I'm assuming during phase one, each setting would be tested for "best fit", selected, then move into phase 2.
Is there a way to hard code the Phase one settings (encryption, hash etc...) instead of it having to go through the list of different options?
Solved! Go to Solution.
03-21-2025 01:11 AM
@Youreateapot418 it doesn't need to match lifetime.
"A match exists when both policies from the two peers contain the same encryption, hash, authentication, and Diffie-Hellman parameter values. For IKEv1, the remote peer policy must also specify a lifetime less than or equal to the lifetime in the policy the initiator sent. If the lifetimes are not identical, the ASA uses the shorter lifetime. For IKEv2 the lifetime is not negotiated but managed locally between each peer, making it possible to configure lifetime independently on each peer."
03-21-2025 12:08 AM
@Youreateapot418 no you cannot, you define IKE policies (IKEv1/IKEv2) with the setting and a priority. The ASA/FTD checks the policy with the lowest priority number first. If there is no match, it checks the policy with the next highest priority number, and so on until all policies have been evaluated.
03-21-2025 01:04 AM
That's what I thought... however, if you have say for:
priority 1 = sha512 , aes 256 gcm, timeout 86400 seconds
priority 2 = sha512 , aes 256 gcm, timeout 28800 seconds
The far end say they have only the option for:
sha512 , aes 256 gcm, timeout 28800 seconds...
But when the tunnel comes up, it has passed phase1 and brought up phase 2 using our priority 1 option.
Do timers have to be the same when used in the negotiation?
Or is it something on the far end which (i.e. they are accepting the timeout of 86400 and it's not even attempting to check our priority 2 setting?)
03-21-2025 01:11 AM
@Youreateapot418 it doesn't need to match lifetime.
"A match exists when both policies from the two peers contain the same encryption, hash, authentication, and Diffie-Hellman parameter values. For IKEv1, the remote peer policy must also specify a lifetime less than or equal to the lifetime in the policy the initiator sent. If the lifetimes are not identical, the ASA uses the shorter lifetime. For IKEv2 the lifetime is not negotiated but managed locally between each peer, making it possible to configure lifetime independently on each peer."
03-21-2025 02:30 AM
This is exactly the info I was looking for, thank you Rob!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide