Proposals & NO_PROPOSAL_CHOSEN

Both sides must offer the same thing

Lesson 3 of 20 · 11 min · Module 1: A private path over a public network

The most common reason a new tunnel does not come up is also the most boring one: the two administrators typed different algorithms.

Start this lesson →

Free. No installation: you write and run the code in your browser, and it is checked automatically.

By the end, you’ll be able to…

  • Explain how a proposal is chosen
  • Recognise NO_PROPOSAL_CHOSEN and the stage it comes from
  • Correct a proposal to match the agreed parameters

The idea

A proposal is an offer. The other gateway compares it with its own list and answers with the first one both sides have. If there is none, it answers NO_PROPOSAL_CHOSEN and the negotiation ends. All three parts of an IKE proposal have to match at once.

# this side                      # other side
ike proposal aes256 sha256 dh14    # aes256 sha256 dh19   -> NO_PROPOSAL_CHOSEN
ike proposal aes256 sha256 dh19    # aes256 sha256 dh19   -> ok

01One difference is enough

aes256 sha256 dh14 and aes256 sha256 dh19 agree on two parts out of three, and that is not a match. The gateways do not mix and match parts from different proposals, and they do not fall back to something weaker on their own.

02The stage tells you which proposal is wrong

NO_PROPOSAL_CHOSEN during IKE_SA_INIT is about the IKE proposal. The same error during CHILD_SA is about the IPsec proposal, and it appears only after authentication has succeeded. Read the stage before you change anything.

03See the proposals on real devices

When a tunnel fails like this, compare what each side has configured; the debug output shows the offer that was rejected.

# FortiGate
diagnose vpn ike gateway list
diagnose debug application ike -1
diagnose debug enable

# Huawei USG
display ike proposal
display ike sa

# Cisco IOS
show crypto ikev2 proposal
show crypto ikev2 sa
debug crypto ikev2

Your turn

The branch upgraded its gateway and changed its settings (see the panel). The tunnel no longer comes up. Update the IKE proposal and the IPsec proposal so that both negotiations succeed. Offer exactly what was agreed, one proposal each.

What the checks look for

  • IKE_SA_INIT succeeds with the new IKE proposal
  • The child SA uses aes256
  • The tunnel carries the traffic between the offices
  • Exactly one proposal of each kind is offered
Try it in the editor →

Take this with you

Each proposal must match on every part. The stage that reports NO_PROPOSAL_CHOSEN tells you which of the two proposals to compare.

Go a little further

Put the old IKE proposal back as a second ike proposal line under the new one and run the lab: the tunnel still comes up. Think about why that is rarely a good idea.

Learn VPN & IPsec Foundations for free

20 short lessons with real code and instant checks.

See the whole course →