public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <sw@simonwunderlich.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Antonio Quartulli <a@unstable.cc>
Subject: Re: [B.A.T.M.A.N.] [PATCH 3/4] batman-adv: prevent duplication of ARP replies in BLA setups when DAT does address resolution
Date: Mon, 15 Feb 2016 09:27:02 +0100	[thread overview]
Message-ID: <10278318.qWhkaFWykG@prime> (raw)
In-Reply-To: <OFB1894E97.63E32850-ONC1257F57.004C41B6-C1257F57.004C4F9E@phoenixcontact.com>

[-- Attachment #1: Type: text/plain, Size: 1300 bytes --]

On Friday 12 February 2016 14:53:31 Andreas Pape wrote:
> From 2cc1e9eb153d0c2d64cb0fb0747063ba63472925 Mon Sep 17 00:00:00 2001
> From: Andreas Pape <apape@phoenixcontact.com>
> Date: Fri, 12 Feb 2016 13:19:25 +0100
> Subject: [PATCH 3/4] batman-adv: prevent duplication of ARP replies in BLA
> setups when DAT does address resolution
> 
> This patch covers the case of a bla setup with enabled dat if none of the
> common gateways of the
> same backbone has already knowledge of the searched ip address and
> therefore has to ask via DAT some
> of the other mesh nodes. A broadcast arp request is coming
> from the backbone and each backbone gateway starts an address resolution
> via other DAT mesh nodes.
> In this case it should be prevented, that multiple answers from DAT
> enabled mesh nodes reach the
> backbone gateways leading to multiple replies in a common backbone again.

I think this approach and its methods as implented are good. However I think 
we should generalize this case and forbid UNICAST/UNICAST4ADDR between 
backbone gateways, as discussed in the other thread. 

What do you think, or does anyone else have opinions?

@Antonio, in what way would be the DHT in DAT be affected? Basically, we would 
exclude some orginators who are on the same backbone.

Cheers,
     Simon

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-02-15  8:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-12 13:53 [B.A.T.M.A.N.] [PATCH 3/4] batman-adv: prevent duplication of ARP replies in BLA setups when DAT does address resolution Andreas Pape
2016-02-15  8:27 ` Simon Wunderlich [this message]
2016-02-16  8:46   ` [B.A.T.M.A.N.] Antwort: " Andreas Pape

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=10278318.qWhkaFWykG@prime \
    --to=sw@simonwunderlich.de \
    --cc=a@unstable.cc \
    --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