From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: "Linus Lüssing" <linus.luessing@c0d3.blue>, a@unstable.cc
Subject: Re: [B.A.T.M.A.N.] [PATCH v4 0/2] batman-adv: increase DAT DHT timeout
Date: Mon, 08 Apr 2019 11:14:30 +0200 [thread overview]
Message-ID: <2333514.yPfxEEDAa4@bentobox> (raw)
In-Reply-To: <20190407112320.32021-1-linus.luessing@c0d3.blue>
[-- Attachment #1: Type: text/plain, Size: 681 bytes --]
On Sunday, 7 April 2019 13:23:18 CEST Linus Lüssing wrote:
> To increase the timeout only for DAT DHT entries added via DHT-PUT but
> not for any other entry in the DAT cache the DAT cache and DAT DHT
> concepts are first split into two separate hash tables (PATCH 1/2).
>
> PATCH 2/2 then increases the timeout for DAT DHT entries from 5 to
> 30 minutes.
>
>
> The motivation for this patchset is based on the observations made here:
> https://www.open-mesh.org/projects/batman-adv/wiki/DAT_DHCP_Snooping
Antonio, please check whether this approach is to your liking. Also that there
are now two ways to retrieve the DAT data via netlink.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-04-08 9:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-07 11:23 [B.A.T.M.A.N.] [PATCH v4 0/2] batman-adv: increase DAT DHT timeout Linus Lüssing
2019-04-07 11:23 ` [B.A.T.M.A.N.] [PATCH v4 1/2] batman-adv: split DAT cache into DAT cache and DAT DHT Linus Lüssing
2019-04-07 11:23 ` [B.A.T.M.A.N.] [PATCH v4 2/2] batman-adv: increase DAT DHT timeout Linus Lüssing
2019-04-08 9:14 ` Sven Eckelmann [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=2333514.yPfxEEDAa4@bentobox \
--to=sven@narfation.org \
--cc=a@unstable.cc \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=linus.luessing@c0d3.blue \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.