From: Antonio Quartulli <ordex@autistici.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCHv2 4/4] batman-adv: enable nodes to detect not yet announced clients
Date: Fri, 6 Apr 2012 12:13:36 +0200 [thread overview]
Message-ID: <20120406101335.GB10310@ritirata.org> (raw)
In-Reply-To: <1333543332-26942-5-git-send-email-ordex@autistici.org>
[-- Attachment #1: Type: text/plain, Size: 1982 bytes --]
On Wed, Apr 04, 2012 at 02:42:12PM +0200, Antonio Quartulli wrote:
> A client that connects to the mesh network is not visible to any node until it
> has been announced by its serving node in the next TT diff sent out by means of
> the next OGM.
>
> During this period the client is not able to communicate to anyone because no
> node has a route towards it yet. This is usually acceptable in networks with
> short OGM interval (=the maximum waiting time before the next announcement), but
> it is definitely problematic in networks where the OGM interval has been set to
> an higher value (e.g. 5 seconds). The client, that probably issued an ARP or
> DHCP request upon connection will suffer from several timeouts before being able
> to communicate with the rest of the network.
>
> This patch enable nodes to detect such "new born" clients and to add a temporary
> route towards them in order to be able to communicate. If the client is not
> claimed by any node within a certain amount of time, it will then be deleted.
>
> Roaming operations have been adapted accordingly in order to be let clients
> switch serving node even during the first OGM interval (when they have not been
> announced yet)
>
> Signed-off-by: Antonio Quartulli <ordex@autistici.org>
> ---
> main.h | 2 +
> packet.h | 15 +++----
> routing.c | 26 +++++++++---
> soft-interface.c | 6 ++-
> soft-interface.h | 2 +-
> translation-table.c | 111 +++++++++++++++++++++++++++++++++++++++++----------
> translation-table.h | 4 +-
> types.h | 1 +
> 8 files changed, 130 insertions(+), 37 deletions(-)
We definitely need to keep TEMP entries away from global CRC computation and full
table response! So please, drop this patchset. I'll send a new one later.
Cheers,
/me acting as schizophrenic
--
Antonio Quartulli
..each of us alone is worth nothing..
Ernesto "Che" Guevara
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
prev parent reply other threads:[~2012-04-06 10:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 12:42 [B.A.T.M.A.N.] [PATCH 0/4] batman-adv: tt code fixes and temporary client detection Antonio Quartulli
2012-04-04 12:42 ` [B.A.T.M.A.N.] [PATCHv2 1/4] batman-adv: clear ADD+DEL (and viceversa) events in the same orig-interval Antonio Quartulli
2012-04-04 12:42 ` [B.A.T.M.A.N.] [PATCHv2 2/4] batman-adv: beautify tt_global_add() argument list Antonio Quartulli
2012-04-04 12:42 ` [B.A.T.M.A.N.] [PATCHv2 3/4] batman-adv: let tt_global_entry_has_orig() return the orig_entry or NULL instead of 1 or 0 only Antonio Quartulli
2012-04-09 16:55 ` Martin Hundebøll
2012-04-10 18:17 ` Antonio Quartulli
2012-04-04 12:42 ` [B.A.T.M.A.N.] [PATCHv2 4/4] batman-adv: enable nodes to detect not yet announced clients Antonio Quartulli
2012-04-06 10:13 ` Antonio Quartulli [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=20120406101335.GB10310@ritirata.org \
--to=ordex@autistici.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