Closed
Conversation
OlegHahm
added
Area: network
Implement link metrics and differentiate between flooding and routing MPRs
other targets lack <assert.h> or have no radio
Member
|
are there plans to remove the RFC5444 code from this PR and use the NHDP implementation from @fnack instead? |
Member
Author
|
Might make sense indeed. Will try to check with @fnack. |
This adds a simple single linked list which allocates and deallocates memory for it's elements on it's own. It also provides functions to search for and iterate over elements.
This was referenced Jan 13, 2015
Member
There was a problem hiding this comment.
the diff of this file could be completely moved to its own PR. seems unrelated to OLSR to me.
OlegHahm
force-pushed
the
master
branch
3 times, most recently
from
9f184dd to
45554bf
Compare
Member
|
Is this still planned for 2015.12 ? |
Member
Author
|
Definitely not - most likely a mishap while retagging some PRs and issues. |
OlegHahm
added
the
State: archived
Member
Author
|
I have to admit: I was not very successful adopting this PR... |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In consultation with @benpicco I take over PR #765. Original description:
This adds an implementation of the OLSRv2 routing protocol (without metrics), based on oonf_api.
The interface offered to applications currently consists of only a olsr_init function which will set up and start a sender and receiver thread for RFC5444 based (UDP on port 269) HELLO and Topology Control messages.
That means that every HELLO_REFRESH_INTERVAL (2s + random jitter) a non-forwarded HELLO message is send for neighborhood discovery. Every TC_REFRESH_INTERVAL (5s + random jitter) a topology control message is broadcast (only by selected flooding MPRs) through the network.
This happens transparent to the application, IP packets are now routed to known hosts within the MANET once a path has been established.
print_topology_set will output the forwarding table with all known mesh nodes.
Does work well on native with #680, but still crashes on the testbed after some time.
Each known MANET router requires 72 byte of memory + 12 bytes for each alternative route to the node.
Depends on #630