From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [PATCHv2 2/2] batman-adv: Snoop DHCPACKs for DAT
Date: Thu, 7 Jul 2016 15:40:52 +0200 [thread overview]
Message-ID: <20160707134052.GD7076@otheros> (raw)
In-Reply-To: <20160707101442.GC7076@otheros>
On Thu, Jul 07, 2016 at 12:14:42PM +0200, Linus Lüssing wrote:
> Hi Antonio,
>
> > have you tried applying this patch on one of your servers and measure the local
> > effect? (i.e. if the number of BRD ARP req is reduced or not?)
>
> I had queried Martin Weinelt just yesterday, they will test it on
> a 500 nodes compat-v15 setup soon :).
Unfortunately, looks like this patch has no effect regarding the
ARP Request overhead. According to batctl log, DHCPACKs are
snooped, but still 84.3% of all ARP Requests come from the three
DHCP servers / gateways.
These ARP Requests come encapsulated in a batman-adv broadcast
packet type.
Hm, anyone having another idea what might still be causing these
ARP Requests?
Cheers, Linus
next prev parent reply other threads:[~2016-07-07 13:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 18:01 [B.A.T.M.A.N.] [PATCHv2 1/2] batman-adv: Add wrapper for ARP reply creation Linus Lüssing
2016-07-05 18:01 ` [B.A.T.M.A.N.] [PATCHv2 2/2] batman-adv: Snoop DHCPACKs for DAT Linus Lüssing
2016-07-07 9:24 ` Antonio Quartulli
2016-07-07 9:43 ` Sven Eckelmann
2016-07-07 10:14 ` Linus Lüssing
2016-07-07 13:40 ` Linus Lüssing [this message]
2016-07-08 0:33 ` Antonio Quartulli
2016-07-10 11:42 ` Sven Eckelmann
2016-08-23 1:31 ` Linus Lüssing
2016-07-10 11:18 ` [B.A.T.M.A.N.] [PATCHv2 1/2] batman-adv: Add wrapper for ARP reply creation Sven Eckelmann
2016-10-18 13:01 ` [B.A.T.M.A.N.] [v2, " 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=20160707134052.GD7076@otheros \
--to=linus.luessing@c0d3.blue \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.