-
Notifications
You must be signed in to change notification settings - Fork 2.1k
transceiver buffer too small #1747
Copy link
Copy link
Closed
Labels
Area: networkArea: NetworkingArea: NetworkingPlatform: nativePlatform: This PR/issue effects the native platformPlatform: This PR/issue effects the native platformType: cleanupThe issue proposes a clean-up / The PR cleans-up parts of the codebase / documentationThe issue proposes a clean-up / The PR cleans-up parts of the codebase / documentation
Milestone
Description
Would it be possible to enlarge the transceiver buffer a bit (or provide different options, depending on the platform)? With AODVv2 and the current buffer size of nativenet, I am running into the following problem:
While Route Requests (RREQ) are broadcasted, they are answered with Route Replies (RREP), which are unicast. Because they are up against so many broadcasted RREQ (and other RREPs), about 2/3 of my RREQ are dropped because the transceiver buffer is full somewhere along the way towards the originating node, making route discoveries fail even in perfect environments (desvirt grid with 0% lossrate).
This happened with each node of a 4x4 grid starting a route discovery every 1-180 seconds.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Area: networkArea: NetworkingArea: NetworkingPlatform: nativePlatform: This PR/issue effects the native platformPlatform: This PR/issue effects the native platformType: cleanupThe issue proposes a clean-up / The PR cleans-up parts of the codebase / documentationThe issue proposes a clean-up / The PR cleans-up parts of the codebase / documentation