> On a fragmented packet 6lowpan calls dev_hard_header once, then many > times lowpan_fragment_xmit, depending on the number of fragments which > is needed.
To me, the obvious answer would be "just don't do that". Each fragment is a distinct packet, so it should not reuse a header that was created for another packet in the first place. > Each call of lowpan_fragment_xmit will have the same DSN value. Maybe > we should put the increment of DSN in "mac802154/tx.c" before calling > xmit callback from driver (Just an idea). What do you think about > that? That would work. Crypto will have to set it's own frame counter there anyway, since reordering in the wpan queue would otherwise cause unexpected packet drops. I don't see that need for the DSN though. ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ Linux-zigbee-devel mailing list Linux-zigbee-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel