public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Axel Neumann <axel@open-mesh.net>
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.] batmand terminates silently
Date: Sun, 7 Oct 2007 22:26:41 +0200	[thread overview]
Message-ID: <200710072226.41589.axel@open-mesh.net> (raw)
In-Reply-To: <200709251200.21204.axel@open-mesh.net>

Hi Stephan,


you can use rv 687 with
--resist-blocking-send 
which lets daemon survive if firewall blocks outgoing OGMs

regards
axel


> > few weeks agoe I had sometimes the problem that batmand (experimental)
> > exits silently. Today I found maybe one reason for this.
> > When you have batman running and insert the iptable rule
> >
> > iptables -I OUTPUT -o eth1 -j DROP
> >
> >
> > batmand exits. This also happen for additional interfaces controlled
> > by batmand.
>
> Ah sure,
> its not a bug, its a feature :-)
> Batman checks if packets generated on its behaf are blocked by a firewall
> and exits if this is the case.
> The assumption when implementing this was, that usually the firewall is
> configured before batmand is started and not touched later on.
>
> In the assumed case the immediate exit helps to directly indicate the
> problem to the maintainer of the node. Actually debuglevel 3 should report
> this.
>
> Of course in your fancy setups this might be undesirable and having an
> option to disable this feature is a good idea. Put this on the todo list.
>
> ciao,
> axel

  reply	other threads:[~2007-10-07 20:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-25  7:17 [B.A.T.M.A.N.] batmand terminates silently Freifunk Dresden
2007-09-25 10:00 ` Axel Neumann
2007-10-07 20:26   ` Axel Neumann [this message]
2007-09-25 10:26 ` Marek Lindner

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=200710072226.41589.axel@open-mesh.net \
    --to=axel@open-mesh.net \
    --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