OLSR dynamic gateway plugin

[knolan]

[QUOTE=tog;52209]The dyngw plugin announces 0.0.0.0/0 via Hna4 based on whether or not there is a response from what you told it to ping.
QUOTE]

I think I saw a post about this on the forums, but can't find it.

When I implemented the plugin, the CPU on the WRAP went upto 85%

Anyone know how to fix this?

Thanks
Keith

[tog]

What version please?

I've never used the dyn_gw plugin myself so I don't know firsthand how well or how badly it behaves...

The version you're talking about is especially important, there have been constant updates to the OLSR software.

[DrLove73]

rebel2234 also reported in this post (http://forums.star-os.com/showpost.php?p=52249&postcount=3). No fix for now I guess.

Try OLSR site and dyngw site for info.

[tog]

Ugh. So the dyn_gw plugin is probably not written very well...

If anybody knows C and wants to fix it.. I bet it's not a very big program.

For now using the code we've got, though... the unnecessarily high load presents another compelling reason to put your dyn_gw plugin OLSR system on a completely separate dedicated "Internet gateway" system board that is not the StarV3 radio backbone/AP system.

I described another scenario during the course in Lucaya where one would want to run the dyn_gw plugin on a separate system that's there just to be an Internet gateway and not run dyn_gw on the actual StarV3 backbone/AP system.

In order to provide Internet access at the "border" of your network you have to set a default static route to somewhere which means that system itself doesn't get to benefit from OLSR's changeover of the default route. If the "Internet gateway" system board with the default static route is there to do nothing but be the Internet gateway then who cares if that particular system can't reach The Internet via the other gateway. As long as the StarV3 system sitting next to it with all the radios and all the actual important traffic has no static default route and will benefit from the "new" default route from OLSR.