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>
Cc: a@unstable.cc
Subject: Re: [B.A.T.M.A.N.] [RFC 2/2] batman-adv: Use broadcast as fallback for gateway replies
Date: Fri, 1 Jul 2016 09:30:31 +0200 [thread overview]
Message-ID: <20160701073031.GJ4309@otheros> (raw)
In-Reply-To: <1465676873-21545-2-git-send-email-sven@narfation.org>
On Sat, Jun 11, 2016 at 10:27:53PM +0200, Sven Eckelmann wrote:
> The replies from gateway server to gateway client are usually sent via
> unicast packets. This only works when the destination address for the reply
> is already known to the translation table. But usually the gateway replies
> are in response to the first known contact from a device to the gateway
> server. So it can happen that the TT entry was not yet created.
>
> The gateway server has therefore use broadcast as fallback when the entry
> is not yet known. This makes the first responses from a DHCP server to a
> DHCP client more robost.
>
> Signed-off-by: Sven Eckelmann <sven@narfation.org>
> ---
> This is completely untested. The RFC was submitted to better explain a
> problem to Antonio. This problems was noticed in real world setups but
> these patches were not yet tested in these setups.
Hm, I'm wondering what kind of overhead implications this could
have in larger mesh networks.
Didn't TT support temporary entries? Could the gateway server
inject them into its global translation table after parsing an
incoming DHCP packet?
prev parent reply other threads:[~2016-07-01 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-11 20:27 [B.A.T.M.A.N.] [RFC 1/2] batman-adv: Fix speedy join in gateway client mode Sven Eckelmann
2016-06-11 20:27 ` [B.A.T.M.A.N.] [RFC 2/2] batman-adv: Use broadcast as fallback for gateway replies Sven Eckelmann
2016-07-01 7:30 ` 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=20160701073031.GJ4309@otheros \
--to=linus.luessing@c0d3.blue \
--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