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: [B.A.T.M.A.N.] Enhancements for Unsolicited Neigh. Adv. / grat ARP Reply
Date: Sat,  2 Aug 2014 21:18:49 +0200	[thread overview]
Message-ID: <1407007130-23077-1-git-send-email-linus.luessing@web.de> (raw)

Hi there,

Here's a little, rough patch to illustrate the idea we discussed a little
at the last Wireless Battle Mesh, that is forwarding the noisy IPv6
Unsolicited Neighbor Advertisements and gratuitous ARP Replies via unicast.

Currently these ugly unsol. NAs cause about 40% of ICMPv6 multicast
overhead in our networks here.

A little more detailed explanation with some pictures can be found here:

https://www.open-mesh.org/projects/batman-adv/wiki/Unicasting-unsolicited-neighbor-advertisements

In the few, simple scenarios with bridged-in hosts in VMs, the patch
seemed to do what it was supposed to do uppon roaming. Unsol. NAs did only
appear on the node the host roamed away from.

If I remember correctly, there were also some worries about how this
might work together with BLA-II. I gave it a little more thought and
had a look at the BLA-II source code, but couldn't find any issues.

The only BLA-II related non-ideal thing I could think of so far is
noted in the code of this patch at the according place (but I think
that might not matter much in practice).

Looking forward to hear about what you think about it, especially
conceptually.

Cheers, Linus



             reply	other threads:[~2014-08-02 19:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-02 19:18 Linus Lüssing [this message]
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

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=1407007130-23077-1-git-send-email-linus.luessing@web.de \
    --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