Hi Ralph,
On Wed, Jul 17, 2013 at 05:50:23AM +0000, Ralph Droms (rdroms) wrote:
>
> On Jul 15, 2013, at 9:27 PM 7/15/13, Alexander Aring <alex.ar...@gmail.com>
> wrote:
>
> Some protocolls has a unspecific address as source address like
> "Multicast Listener Report Message v2" or "Neighbor Soliciation"
> decode the SAC bit as :: address.
>
> I read RFC 6282 as specifying unspecified address with SAC == 1, SAM == 00.
>
> Relevant code snippet from my other stack:
>
> switch (ihc1 >> 4 & 7) {
> /* snip */
> case 4: /* SAC == 1, SAM == 0 */
> memset (iptr->net_ipsrc, 0, 16);
> break;
>
> case 5: /* SAC == 1, SAM == 1 */
> /* Context and 64 bits inline */
> #ifdef DEBUG_RADIO
> kprintf("no context-based address compression\n");
> #endif
> bptr += 8;
> break;
> snip
>
Thanks for this hint, I will try to handle that in this case when SAC =
1 and SAM = 00. Also I will check if we set this correctly in
lowpan_header_create function.
Maybe it's good to write test cases for the iphc header, this would be
great.
Alex
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Linux-zigbee-devel mailing list
Linux-zigbee-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
