(racoon 895) RE: "DOI value of CONNECTED Notify Message has problem"

["Haoda" <haoda@64translator.com>]

Hi!

Thanks for your reply!
I have applied your patch. After then the expected DOI value has been
received.

I run the test again, the environment is same as previous one.
At first, we assume the "TN" means tester node, the "NUT" means FreeBSD, and
the "N/D" means Notify payload.

Here is the result I expected based RFC,
* PHASE II
 	                     QUICK MODE

#   Initiator(TN)   Direction      Responder(NUT)
(1)  HDR*, HASH(1), 
	    SA, Ni     ========>                       <---Commit Bit = 0
(2)                <========     HDR*, HASH(2), SA, Nr
(3)  HDR*, HASH(3) ========>                        <---Commit Bit = 1
(4)  HDR*; HASH(1),
          N/D      ========>                        <---Commit Bit = 1

But this actual result is like this,
* PHASE II
 	                     QUICK MODE

#   Initiator(TN)   Direction      Responder(NUT)
(1)  HDR*, HASH(1), 
	    SA, Ni     ========>                       <---Commit Bit = 0
(2)                <========     HDR*, HASH(2), SA, Nr
(3)  HDR*, HASH(3) ========>                        <---Commit Bit = 1
(4)  	          <========     HDR*, HASH(1),N/D   ????
(5)  HDR*; HASH(1),
          N/D       ========>                        <---Commit Bit = 1


I think the 4th message sent from responder to initiator is not correct.
Because according to RFC, when the responder receive the 3rd message, it
will wait for the next Notify payload from initiator and don't send any 
packet. I think maybe racoon sent the improperly packet after it received
the 3rd message.

How about you think about this?


Regard yours,
Haoda <haoda@ysh.com.cn>