sending a link characterization request results in peer being brought down about ll-dlep

[davidpwiggins]

This line is the key:

11:35:40.733 INFO: .../LL-DLEP/ProtocolMessage.cpp:629:parse(): at index=4 data item id=1 length=72 Status 130;Link_Characteristics_Response exactly one of Status required, but got 0

This is using the example client. By default, the "linkchar-autoreply" configuration parameter is set to 1 (enabled). This tells the example client to automatically reply to any linkchar request with exactly the same data items that it received in the request, giving the appearance that the request was honored. The problem is that the Link Characteristics Response message requires a Status data item (just like the error message above says), but the example client doesn't add one when it sends the reply. It just echos the same data items it got. The fix is to add the Status data item before sending the reply.