public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@web.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Enhancements for Unsolicited Neigh. Adv. / grat ARP Reply
Date: Mon, 1 Sep 2014 09:27:46 +0200	[thread overview]
Message-ID: <20140901072746.GG6470@odroid> (raw)
In-Reply-To: <201408081606.01045.sw@simonwunderlich.de>

On Fri, Aug 08, 2014 at 04:06:00PM +0200, Simon Wunderlich wrote:
> > Currently these ugly unsol. NAs cause about 40% of ICMPv6 multicast
> > overhead in our networks here.
> 
> I think it's quite a good idea - to motivate your proposal, I'd suggest to add 
> some information on how many broadcasts you think you can save in your 
> networks - 40% of ICMPv6 traffic is a little vague, since we don't know how 
> much of your traffic is ICMPv6 and what you have already blocked.

Hrmpf, had spend some time to set up some live-monitoring plus
dumping into RRDs. And now figured out, that from day to it varies
a lot, the NA traffic at Freifunk Hamburg for instance is very
"peaky", so only at certain minutes but then quite a lot. Some
days I see 40% again, some days it's maybe just 5-10%.

So at least along half of a day NA overhead is actually marginal.

I'll need to figure out first what's causing these spikes. Whether
it's some broken or malicious client devices, the bus and train
tables or something else causing these extreme spikes. Funnily,
any other multicast traffic is smoothly following the
#number-of-clients curve along the day (max at ~13:00, min at
~04:00)...

Cheers, Linus

      reply	other threads:[~2014-09-01  7:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-02 19:18 [B.A.T.M.A.N.] Enhancements for Unsolicited Neigh. Adv. / grat ARP Reply Linus Lüssing
2014-08-02 19:18 ` [B.A.T.M.A.N.] [PATCH RFC] batman-adv: unicasting grat. ARP Reply / unsol. neigh. Advertisement Linus Lüssing
2014-08-08 14:06 ` [B.A.T.M.A.N.] Enhancements for Unsolicited Neigh. Adv. / grat ARP Reply Simon Wunderlich
2014-09-01  7:27   ` Linus Lüssing [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=20140901072746.GG6470@odroid \
    --to=linus.luessing@web.de \
    --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