I want to accomplish a mesh under routing.
Mesh under routing is currently not supported in RIOT (no mesh addressing in the 6LoWPAN header), am I right?
My idea is to modify outgoing traffic (e.g UDP traffic) and add originator and final address to the 6LoWPAN header.
So I would register for GNRC_NETTYPE_SIXLOWPAN messages and when getting a GNRC_NETAPI_MSG_TYPE_SND event,
I add a custom mesh addressing to the header.
Is this the right way or do you have any suggestions on this?
I want to accomplish a mesh under routing.
Mesh under routing is currently not supported in RIOT (no mesh addressing in the 6LoWPAN header), am I right?
This is true.
My idea is to modify outgoing traffic (e.g UDP traffic) and add originator and final address to the 6LoWPAN header.
So I would register for GNRC_NETTYPE_SIXLOWPAN messages and when getting a GNRC_NETAPI_MSG_TYPE_SND event,
I add a custom mesh addressing to the header.
Is this the right way or do you have any suggestions on this?
Better do it within the 6Lo module gnrc_sixlowpan as IPHC and Fragmentation are done. The external NETAPI is mostly used for interaction with other layers. I included Mesh under routing into my considerations when I overhault 6Lo’s internal API [1] and was actually planning to finally add this to the documentation this week (due to other plans within gnrc_sixlowpan). But in short: Just provide a submodule for gnrc_sixlowpan with send/recv functions that have the same prototype as defined in [1]. The recv/send function of the “neighboring” modules should be called from that module according to the dispatch after the mesh-under dispatch.