Re: [B.A.T.M.A.N.] Migration to Batman

Mitar
2012-04-16T12:32:09Z

Hi!

On Mon, Apr 16, 2012 at 12:58 PM, Marek Lindner <lindner_marek@yahoo.de> wrote:
> If you already have a shell script uevent definitely is the way to go. It is
> far easier to script than netlink.

Yes, but are there uevent events for node reachable/unreachable?

> How does your logic handle network splits / join ? Do you have the source
> somewhere ?

Our current logic is very simple: if route to 0.0.0.0 disappears,
display to the user error message through splash screen ("sorry, node
is separated from the rest of the mesh" message) when user tries to
access external IPs. When it comes back, return to normal behavior.

I am not sure what you mean by splits / joins. Yes, source is
available. But I am not sure if this is what you had in mind?

I was just saying that route flapping (on/off) can be dealt with some
aggregation of events on a consumer side. (But I am now unsure, maybe
we are doing this already on the plugin side.)

For olsrd plugin:

http://dev.wlan-si.net/browser/firmware/packages/opkg/net/olsrd/plugins/actions

> You could even connect your routing daemon to the uevents mentioned
> above.

Are those uevents already available? Do we know of any existing
routing protocol being capable of using them?

Mitar