[Olsr-dev] BMF in 0.5.6-R8
Sven-Ola Tuecke
(spam-protected)
Wed Feb 3 13:49:15 CET 2010
Hey,
as I repeatedly emphasized on: dyn_gw is only usable on edge-nodes (that is:
no other mesh user behind). If you have a GW node in the middle and the GW's
local inet does not work, other users will have trouble to use a backup
gateway. Example: if GW fails and does not clear failed default route then:
UserNode -> GW(faulty) -> 2.GW (no inet for user)
For that reason (and for doing the necessary policy routing tricks in a shell
script) the dyn_gw_plain exists which simply links default route in default
routing table to HNA0/0 announcements.
On the other hand: dyn_gw is old and unmaintained and may deserve a bit
cleaning anyhow. Thank you,
// Sven-Ola
Am Mittwoch 03 Februar 2010 12:13:07 schrieb Teco Boot:
> I've seen problems with BMF in 0.5.6-R8.
>
> Feb 1 23:21:20 olsr-rt01 vmunix: [27094.364285] olsrd[5363]: segfault at
> 1a8 ip b7e46578 sp bfb79bb0 error 4 in olsrd_bmf.so.1.5.3[b7e42000+9000]
>
> I upgraded to bmf.1.6.2. This works better.
> http://sourceforge.net/projects/olsr-bmf/
> This plugin needs a patch on main.c, scheduler.c and
> scheduler.h, for the in bmf 1.6.1 introduced mutex.
> I assume Erik Tromp had good reasons for the mutex.
> Is it a problem updating olsrd base code for it?
>
> There are some warnings during compile of bmf.
> I'll come back on this later.
>
>
> I need a tool for P2P peer discovery (e.g. MS Groove DPP).
> Alternatives for BMF?
>
>
> Regards, Teco
More information about the Olsr-dev
mailing list