public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <mareklindner@neomailbox.ch>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [RFC PATCH] batman-adv: Increase DHCP snooped DAT entry purge timeout in DHT
Date: Fri, 20 Jul 2018 12:06:14 +0800	[thread overview]
Message-ID: <1778848.TvDNe92q0N@rousseau> (raw)
In-Reply-To: <20180625172919.GA2433@otheros>

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

On Tuesday, 26 June 2018 01:29:19 HKT Linus Lüssing wrote:
> 1) Host (A) joins the network and has the IP_X / MAC_a
>    statically assigned.
> 2) Some ARP Requests reaches this host, it issues an ARP Reply
>    which populates the DHT.
> 3) The host leaves the network.
> 3) Another host (B) joins the network with IP_X / MAC_b
>    statically assigned.

Let's distinguish the problems we're trying to solve:

 * Cache consistency during updates: A local DAT cache which is not updated 
during a cache update event, thus needs to time out faster and a global DAT 
cache receiving regular updates with less need to update.

 * Timely cache update: The global cache shall be updated as soon as the 
information is available.

My previous email focused on the former while your response is about the 
latter. Is that your assessment too ?

Both problems require solving to fully support this dynamic environment you 
are describing whilst reducing ARP traffic overhead.

Would you mind commenting on the cache consistency issue ? Antonio will 
respond to your 'snoop outgoing ARP Requests' question separately.

Cheers,
Marek

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

  parent reply	other threads:[~2018-07-20  4:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 23:48 [B.A.T.M.A.N.] [RFC PATCH] batman-adv: Increase DHCP snooped DAT entry purge timeout in DHT Linus Lüssing
2018-06-03 11:53 ` Marek Lindner
2018-06-25 17:29   ` Linus Lüssing
2018-07-10 20:23     ` Linus Lüssing
2018-07-20  4:47       ` Antonio Quartulli
2019-01-05 21:02         ` Linus Lüssing
2018-07-20  4:06     ` Marek Lindner [this message]
2019-01-05 20:41       ` 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=1778848.TvDNe92q0N@rousseau \
    --to=mareklindner@neomailbox.ch \
    --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