[RFC] add olsr2 routing algorithm #765
Conversation
|
What is necessary to make the example application work with |
|
I thought you would just need to fill out the whitelist/blacklist .. you can take a look at the other examples/buildtest output for reference. But looking at the output, it appears that the application does not build at all.. Therefore I'd say you need to fix the bugs ;-) |
|
|
|
#1142 should fix |
I thought it failed the first time I built it, now this does not happen anymore even if I delete everything ... not sure what I did there.. |
|
I get errors when building for msba2: |
|
Now this is strange, Why did this previously work and why is it still working for native? |
|
Different toolchains.. |
|
It's the same version of gcc vs |
|
I meant architectures.. I mean - it's a shot in the dark anyway.. still - gcc has different code for different architectures, right? |
examples/olsr2/main.c
Outdated
There was a problem hiding this comment.
I don't know what this comment is about, but #854 was merged.
There was a problem hiding this comment.
Ok, but currently it's only implemented for native, stm32f1 and nrf51822. I'll drop the getpid() bit and replace it with cpuid_get(), but keep the sysconfig.id for the msba2.
|
After #1210 it should build on the msba2 again |
|
A lot of warnings. |
|
And fails for MSP based platforms. Please fix or blacklist. |
|
Is there some way to find out why the build fails in travis? |
|
@Kijewski, you had a hint for that, but I cannot remember. Can you provide some information and maybe put it also in the wiki? |
|
Prepend .travis.yml's section script with the test that you actually want to run: |
|
@benpicco, Can you fix the cppcheck warnings and add the extern C to the headers? |
|
@benpicco, ping. |
|
@benpicco, please rebase. |
|
Superseeded by #2294. |
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_initfunction 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. EveryTC_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_setwill 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