From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH 2/2] batman-adv: Use broadcast as fallback for gateway replies
Date: Fri, 01 Jul 2016 10:00:25 +0200 [thread overview]
Message-ID: <3538968.M8hm509Ngn@bentobox> (raw)
In-Reply-To: <1465721000-9174-2-git-send-email-sven@narfation.org>
[-- Attachment #1: Type: text/plain, Size: 1536 bytes --]
[....]
> 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?
Right now we have the problem that DHCP requests (broadcasts by the user) are
encapsulated by the gateway code in the wrong type of packet [1,2,3]. These
are the unicast packets (non-4addr) which cannot be used to create temporary
TT entries. This should be addressed by the first patch.
The second patch is currently only my bandaid (because I cannot patch all APs)
and I would be more than happy when this patch is not required. So I would not
object when this patch is rejected because it causes noise on the network.
For example gluon already accepted the first patch [4] and thus will hopefully
not require the second patch anymore with 2016.2.0 for clients doing their
DHCP Discover as broadcast.
Btw. the non-RFC version of the patch is here:
https://patchwork.open-mesh.org/patch/16377/
I have taken the freedom to move the reply to this patch.
Kind regards,
Sven
[1] https://patchwork.open-mesh.org/patch/16376/
[2] https://git.open-mesh.org/batman-adv.git/blob/a36b7a3b08f4cc7c41103aa4db176a11e965e068:/net/batman-adv/routing.c#l914
[3] https://git.open-mesh.org/batman-adv.git/blob/a36b7a3b08f4cc7c41103aa4db176a11e965e068:/net/batman-adv/soft-interface.c#l468
[4] https://github.com/freifunk-gluon/gluon/commit/93fe275000b65a4148d6a9713a030b0d30e6a9f1
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-01 8:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 8:43 [B.A.T.M.A.N.] [PATCH 1/2] batman-adv: Fix speedy join in gateway client mode Sven Eckelmann
2016-06-12 8:43 ` [B.A.T.M.A.N.] [PATCH 2/2] batman-adv: Use broadcast as fallback for gateway replies Sven Eckelmann
2016-07-01 8:00 ` Sven Eckelmann [this message]
2016-07-06 13:11 ` [B.A.T.M.A.N.] [PATCH 1/2] batman-adv: Fix speedy join in gateway client mode Antonio Quartulli
2016-07-06 13:17 ` Marek Lindner
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=3538968.M8hm509Ngn@bentobox \
--to=sven@narfation.org \
--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