Integrate ARA routing protocol in the INET protocol hierarchy about libara HOT 7 CLOSED

It would be interesting to summarize which changes are required. Have you given some thought on what we would have to change exactly? The most 'complex' task seems to customize the gates, since manet routing has a inout gate in its network layer.

EDIT: Okay, strike that. We have a 'ton' of NED files which somehow are related to the 'core' routing algorithm (even if you remove all the modules for the forwarding and policies):

• ARA.ned (is a simple module which represents the core (?) of the algorithm)
  • simple module
• ARANetworkConfigurator.ned (provides IP address configuration for an ARA node)
  • simple module
• ARANetworkLayer (puts the forwarding, evaporation, etc. together)
  • module
• NetworkNode (seems to do the same thing as the ARANetworkLayer), but with an app
  • module

from libara.

There is probably a good reason why we have our own NetworkConfigurator over the IPv4NetworkConfigurator in INETMANET?

Update: This answers it: "Unlike the INET/MANET NetworkConfigurator classes its does not search for any routes or update any routing tables."

from libara.

No I just did create our own configurator because it was a good opportunity to get to know the INET Manet API a bit better. If you like you can change it to IPv4NetworkConfigurator

from libara.

Using INETMANETs NetworkConfigurator would not cause issues with the routing table and ARA?

from libara.

You are right, The problem with the default implementation was, that routing table entries are setup automagically.
This would prevent the inet framework from asking our routing daemon to discover any route.
As of now I don't see any harm in keeping our own network configurator.

from libara.

Well, the problem right now is that I want to add a traffic generator and I've got the impression so far that it might be a bit tricky to do so (since our protocol stack (meaning the total number of gates) is a bit overwhelming).

from libara.

For documentation: We decided to keep our ned hierarchy as is and do not directly integrate ARA in the INETMANET framework because we do not need the flexibility of this approach.
Instead we just make the Traffic Generator work now and hope we do not have to add to many other INETMANET protocols in the future :)

from libara.