public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: "Magosányi Árpád" <mag@magwas.rulez.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Mesh with access from wifi and lan. Which is the Only True Way?
Date: Wed, 29 Sep 2010 21:41:29 +0200	[thread overview]
Message-ID: <4CA39669.50402@magwas.rulez.org> (raw)
In-Reply-To: <201009291228.55003.lindner_marek@yahoo.de>

  On 2010-09-29 12:28, Marek Lindner wrote:
> On Tuesday 28 September 2010 21:08:53 Magosányi Árpád wrote:
>> But with three nodes in a linear topology user-A-B-C, the reject
>> firewall chain (basically the FORWARD chain) eats up the packets user->A
>> This is the same rule which rejects batman packets A->C which go through
>> B, and there are the gate interface which I do not understand, so while
>> the following rules seem to solve the problem at least for three nodes,
>> I have a feeling that I am not on the right path, and maybe on a way to
>> cause packet storms.
>> iptables -A forwarding_rule -d 10.42.0.0/24 ! -s 10.42.0.0/24 -i ath0 -o
>> ath0 -j ACCEPT
>> iptables -A forwarding_rule -s 10.42.0.0/24 ! -d 10.42.0.0/24 -o ath0 -i
>> ath0 -j ACCEPT
> Could you explain what kind of traffic you actually want to block ? I also don't
> understand what packet storm you are afraid of.
>
I actually want to _enable_ traffic. Any traffic from any node in the mesh.
Regarding packet storm: I thought that the reject in the default 
iptables config might be there to stop propagation of some packets which 
would otherwise propagate and thus multiply in multiple routes. I am 
seeing batman packets rejected there.
As you can see, working of batmand is somewhat a black magic for me, 
esp. wrt. the role of the gate interface.
 From the fact that I had to touch the default firewall config to make 
it work has suggested that I either do some nonstandard thing, or I am 
doing it in the wrong way.
This is why I try to figure out whether my config is sound enough before 
I give it to my village (some 8 thousand people).



  reply	other threads:[~2010-09-29 19:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-28 19:08 [B.A.T.M.A.N.] Mesh with access from wifi and lan. Which is the Only True Way? Magosányi Árpád
2010-09-29 10:28 ` Marek Lindner
2010-09-29 19:41   ` Magosányi Árpád [this message]
2010-09-29 20:20     ` Marek Lindner
2010-09-29 20:44       ` Magosányi Árpád
2010-09-29 21:40         ` Marek Lindner
2010-09-30 11:50           ` Magosányi Árpád
2010-09-30 14:15             ` 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=4CA39669.50402@magwas.rulez.org \
    --to=mag@magwas.rulez.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /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