[Olsr-dev] rfc5444_reader documentation

[Henning Rogge]

Hi,

I took your example code, cleaned it up a little bit and added it to
the repository in the example section. Hope you will find it easy to
read.

The main issue with your code was that your reader part declared a
"message TVL type 2" as mandatory for your callback, but your writer
added the "message TLV type 0" and "message TLV type 1". Because of
this the callback was never called.

The reader guarantees that the 'mandatory" TLVs are present when the
block_callback() function pointer is called. Otherwise it will call
the block_callback_failed_constraints() function pointer.

Henning

On Thu, Jul 11, 2013 at 11:23 PM, Benjamin Valentin
<(spam-protected)> wrote:
> Am Mon, 8 Jul 2013 07:41:05 +0200
> schrieb Henning Rogge <(spam-protected)>:
>
>> Hi,
>>
>> thank you for your interest in the RFC5444 library. During the
>> implementation of the NHDP and OLSRv2 protocol I fixed a number of
>> bugs and tried to simplify the API structure a bit, so the
>> documentation file is a little bit outdated.
>>
>> I will look through it this week and try to adapt it to the current
>> codebase.
>
> Thank you for your supportive answers!
> I'm still not sure how to properly use the reader/writer so I better
> attach an example. Based on test_rfc5444_reader_blockcb.c I want to
> write a package with a message containing two tlvs and the read
> it with rfc5444_reader_handle_packet to output the two values again
> (and toy around with other parameters while I'm at it).
> However, the package gets 'sent', but the .block_callback function of
> the consumer never gets executed.
>
> What am I missing?
>
> Thank you
> Benjamin
>
> --
> Olsr-dev mailing list
> (spam-protected)
> https://lists.olsr.org/mailman/listinfo/olsr-dev



-- 
We began as wanderers, and we are wanderers still. We have lingered
long enough on the shores of the cosmic ocean. We are ready at last to
set sail for the stars - Carl Sagan