public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
* [B.A.T.M.A.N.] batmand terminates silently
@ 2007-09-25  7:17 Freifunk Dresden
  2007-09-25 10:00 ` Axel Neumann
  2007-09-25 10:26 ` Marek Lindner
  0 siblings, 2 replies; 4+ messages in thread
From: Freifunk Dresden @ 2007-09-25  7:17 UTC (permalink / raw)
  To: Open-Mesh, Mailinglist

Hello 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.

Maybe it helps you a little.

Regards, Stephan

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [B.A.T.M.A.N.] batmand terminates silently
  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
  2007-09-25 10:26 ` Marek Lindner
  1 sibling, 1 reply; 4+ messages in thread
From: Axel Neumann @ 2007-09-25 10:00 UTC (permalink / raw)
  To: The list for a Better Approach To Mobile Ad-hoc Networking

Hello,

On Dienstag 25 September 2007, Freifunk Dresden wrote:
> Hello 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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [B.A.T.M.A.N.] batmand terminates silently
  2007-09-25  7:17 [B.A.T.M.A.N.] batmand terminates silently Freifunk Dresden
  2007-09-25 10:00 ` Axel Neumann
@ 2007-09-25 10:26 ` Marek Lindner
  1 sibling, 0 replies; 4+ messages in thread
From: Marek Lindner @ 2007-09-25 10:26 UTC (permalink / raw)
  To: The list for a Better Approach To Mobile Ad-hoc Networking


Hi,

> 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.

actually this is logged to syslog and debug level 4. A "logread -f" on OpenWRT 
systems should show something like that: 

Error - can't send udp packet: Permission denied.
Does your firewall allow outgoing packets on port 4306 ?

Regards,
Marek

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [B.A.T.M.A.N.] batmand terminates silently
  2007-09-25 10:00 ` Axel Neumann
@ 2007-10-07 20:26   ` Axel Neumann
  0 siblings, 0 replies; 4+ messages in thread
From: Axel Neumann @ 2007-10-07 20:26 UTC (permalink / raw)
  To: The list for a Better Approach To Mobile Ad-hoc Networking

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2007-10-07 20:26 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2007-09-25 10:26 ` Marek Lindner

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox