The current fragmentation handling isn't rfc compatible and have several issues.
On receiving side the fragmentation use a own implemented api which have issues like: - Race conditions in fragmentation list handling - Match on fragmentation tag id only This patch series add support for fragmentation handling with the inet_frag api. I am still unsure about checksum calculation in patch. "6lowpan: handling 6lowpan fragmentation via inet_frag api" Maybe somebody can give some advice if it's ok or not? Alexander Aring (5): 6lowpan: add frag information struct 6lowpan: fix fragmentation on sending side net: add ieee802154_6lowpan namespace 6lowpan: handling 6lowpan fragmentation via inet_frag api 6lowpan: handle return value on lowpan_process_data include/net/ieee802154_netdev.h | 7 + include/net/net_namespace.h | 4 + include/net/netns/ieee802154_6lowpan.h | 14 ++ net/ieee802154/6lowpan.c | 261 +++++-------------- net/ieee802154/6lowpan.h | 109 ++++++++ net/ieee802154/Makefile | 2 +- net/ieee802154/reassembly.c | 440 +++++++++++++++++++++++++++++++++ net/ieee802154/reassembly.h | 64 +++++ 8 files changed, 706 insertions(+), 195 deletions(-) create mode 100644 include/net/netns/ieee802154_6lowpan.h create mode 100644 net/ieee802154/reassembly.c create mode 100644 net/ieee802154/reassembly.h -- 1.8.4.2 ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ Linux-zigbee-devel mailing list Linux-zigbee-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
