-
Notifications
You must be signed in to change notification settings - Fork 2.1k
net: eliminate RIOT IPv6 network layer bottleneck #16
Copy link
Copy link
Closed
Labels
State: won't fixState: The issue can not or will not be fixedState: The issue can not or will not be fixedType: bugThe issue reports a bug / The PR fixes a bug (including spelling errors)The issue reports a bug / The PR fixes a bug (including spelling errors)
Description
In the current state, the RIOT network layer tolerates only 1 IPv6 packet going in or out of the device at the same time. Outgoing packets can overwrite incoming packets and the other way around due to the fact that there is only 1 buffer for incoming and outgoing packets (IPv6 Buffer: uint8_t buffer[BUFFER_SIZE]". Find a solution to avoid overwriting of incoming/outgoing packets, especially when using fast transmissions.
The TCP layer (only!) is currently using a dirty HACK for sending packets via a separate output buffer "uint8_t ip_send_buffer[BUFFER_SIZE]" in sys/net/sixlowpan/sixlowip.c
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
State: won't fixState: The issue can not or will not be fixedState: The issue can not or will not be fixedType: bugThe issue reports a bug / The PR fixes a bug (including spelling errors)The issue reports a bug / The PR fixes a bug (including spelling errors)