public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: "Martin Hundebøll" <martin@hundeboll.net>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [RFCv2] batman-adv: Add blocking of one hop OGM messages
Date: Thu, 16 Feb 2012 11:54:56 +0100	[thread overview]
Message-ID: <4F3CE080.6000409@hundeboll.net> (raw)
In-Reply-To: <20120215192321.GA24703@pandem0nium>

Hi Simon,

On 2012-02-15 20:23, Simon Wunderlich wrote:
> Hey Martin,
>
> On Fri, Feb 10, 2012 at 03:53:11PM +0100, Martin Hundebøll wrote:
>>   13 files changed, 491 insertions(+), 0 deletions(-)
>
> please excuse my superficial review, but do we really need to bloat batman-adv
> by 491 more lines to drop these OGMs? I'm afraid the filter will evolve
> more and more, and eventually the research/debugging code in batman-adv
> is bigger than the routing code. ;)

Actually, I agree with you. The first patch was nice and (too) simple, but quickly grew :) My initial goal with the filtering was not to get it included in batman-adv, but just to make it available to others, who might need it. I use it in my work on the university and will continue to keep it updated on master.

> (sorry for ranting ;] )

We like to rant and bash :)
  
> Have you considered using and/or extending the former ebtables patch
> from Linus[1]? We removed [2] it after some discussions [3], but maybe
> its worth fixing these problems if its just about dropping some neighbors
> packets. The patch has some problems, but it was really short and I guess
> we wouldn't mind accepting the performance overhead by ebtables for
> research/debugging purposes. Plus, we could make this a compile-feature too.

With my approach, we only check OGMs, which is relatively cheap, compared to checking every incoming packet, which is why I didn't chose the netfilter path. At this point I am satisfied with the dropping of OGM's, so I don't think I will spend time looking into netfilter.

-- 
Kind regards,
Martin Hundebøll
Nordborggade 57, 2. 1
8000 Aarhus C

+45 61 65 54 61
martin@hundeboll.net

      reply	other threads:[~2012-02-16 10:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08 19:05 [B.A.T.M.A.N.] [RFC] batman-adv: Add filtering of OGM messages Martin Hundebøll
2012-02-08 19:53 ` Antonio Quartulli
2012-02-09  7:59 ` Marek Lindner
2012-02-10 14:53 ` [B.A.T.M.A.N.] [RFCv2] batman-adv: Add blocking of one hop " Martin Hundebøll
2012-02-10 14:56   ` Martin Hundebøll
2012-02-15 19:23   ` Simon Wunderlich
2012-02-16 10:54     ` Martin Hundebøll [this message]

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=4F3CE080.6000409@hundeboll.net \
    --to=martin@hundeboll.net \
    --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