public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: "Outback Dingo" <outbackdingo@gmail.com>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] BATGAT
Date: Thu, 11 Sep 2008 11:22:42 +0700	[thread overview]
Message-ID: <5635aa0d0809102122s4f528693o3aeb1795ce640d4e@mail.gmail.com> (raw)
In-Reply-To: <200809111101.31420.lindner_marek@yahoo.de>

[-- Attachment #1: Type: text/plain, Size: 1018 bytes --]

http://pastebin.com/m1677070a

batgat crashed out, and unloaded without batgat batman routes never stay

using openwrt trunk, so whats the best solution

On Thu, Sep 11, 2008 at 10:01 AM, Marek Lindner <lindner_marek@yahoo.de>wrote:

> On Thursday, 11. September 2008 05:00:59 Gustavo Lindberg wrote:
> > I am experimenting very frustrating issues with batgat. Currently i am
> > testing the last trunk of kamikaze on ubiquity NS2. Batmand dies quietly
> > with batgat loaded. I will prove the last kamikaze on two NS2 without
> > batgat and inform the bug  if this error happen again.
>
> I think it would be intersting to find out why batmand dies. May be you
> could
> produce a core dump ?
> Indeed, we have a problem if the batman daemon dies without telling the
> module. What about adding a keep alive + timeout in the module ?
>
> Greetings,
> Marek
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
>

[-- Attachment #2: Type: text/html, Size: 1654 bytes --]

  reply	other threads:[~2008-09-11  4:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-10 16:41 [B.A.T.M.A.N.] BATGAT Gustavo Lindberg
2008-09-10 19:38 ` Simon Wunderlich
2008-09-10 21:00   ` Gustavo Lindberg
2008-09-11  3:01     ` Marek Lindner
2008-09-11  4:22       ` Outback Dingo [this message]
2008-09-11  5:47         ` Marek Lindner
2008-09-11 22:18       ` Gustavo Lindberg
2008-09-12  2:41         ` Marek Lindner
2008-09-12 14:49           ` Sven Eckelmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5635aa0d0809102122s4f528693o3aeb1795ce640d4e@mail.gmail.com \
    --to=outbackdingo@gmail.com \
    --cc=b.a.t.m.a.n@open-mesh.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox