Re: [manet] AODVv2 implementation

Henning Rogge <> Mon, 27 November 2023 07:11 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 990E9C14CE22 for <>; Sun, 26 Nov 2023 23:11:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Status: No, score=-7.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id yrauKC84nlwo for <>; Sun, 26 Nov 2023 23:11:24 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::62f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by (Postfix) with ESMTPS id C5003C14CF1D for <>; Sun, 26 Nov 2023 23:11:24 -0800 (PST)
Received: by with SMTP id a640c23a62f3a-a00a9c6f1e9so548152466b.3 for <>; Sun, 26 Nov 2023 23:11:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20230601; t=1701069083; x=1701673883;; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=93KL8LFvd7S+Mb9IXZpgqS+6NyOast7bC21bQJXX7qU=; b=VvZevj/g59c0F+T3FOfxtMUIS9xJbGidNtALpTmgIF/IniC37iod+O+2wrR/Poz6wJ CJitsf4akqzJelySWqy7ZNjuup2mbG3h3pOAK7aXd9anmTX9/0F+zEkaqFTVzcPt3w02 6F0iPHtatlRWYNaEonYNgYgOV6Y4PxMI2NGDmqdT25y/pldhofV5/M+/jbQK1dnr3GSk m5NOfMmkd3Gf2B9h2iEmZK0g7mqKd3TsZ/GqWVi0KmHHT211ua998ndML+82x2vPcPcT 5BINS2qnwUJmzAuE1JDmFqmWsoZmiOerRGAaNic5FjgDMxGvuxbJzGeF0W+4hBJe/4Rl b16Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20230601; t=1701069083; x=1701673883; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=93KL8LFvd7S+Mb9IXZpgqS+6NyOast7bC21bQJXX7qU=; b=IR49S7qR2NGkFE2XjRqrFL+jnYTStrlso9xYJEJFSAR7SRhCozHucymh2r+qom44Z8 NfW3I9eFbChF5c9Hzfwiar4xeAmK+MpmPdFIrEr8Ktv5RJKCgG+oEeN6iAKfmA2Y7cGc HAIMOpwkXFpPhM+pedPVCSEMsXN8KhSxGZwfEsW9zG2t27JwNsDxxOVotsUC+Yqs3Gal b3WxGvyKw+fq822OLLZK0hfYy9BZvLtHSBvz7y/8A7IdUvexJPl+Ex4K8TxaKhEIg0u0 e3pLLqrxersiWoIRlVNYr0pcuVjUPNGBijDjAZORnRj9r5LiWVeMwRO2QZNv5uRUNAeZ WJeg==
X-Gm-Message-State: AOJu0YwViqJvwl6xtZWxQig2pkQZlHRQvsoMfCJV9pSLwikwAFWZDhn0 xmfOpjGINNf9aNrYGoGtfWGdnIpFqYEhNAc5Sk0=
X-Google-Smtp-Source: AGHT+IFKkkuMKyRSqJjUO6jOfPsGQvdXseSSCyHL7JWoJnZaUA6NX8UatVoFQjcZbaU2zUPuT3FmREg/fZ+vaLW0/aQ=
X-Received: by 2002:a17:906:9e0a:b0:9f5:994c:7d15 with SMTP id fp10-20020a1709069e0a00b009f5994c7d15mr5408694ejc.77.1701069082757; Sun, 26 Nov 2023 23:11:22 -0800 (PST)
MIME-Version: 1.0
References: <> <> <> <> <>
In-Reply-To: <>
From: Henning Rogge <>
Date: Mon, 27 Nov 2023 08:10:56 +0100
Message-ID: <>
To: Juliusz Chroboczek <>
Cc: Charlie Perkins <>, "" <>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
Subject: Re: [manet] AODVv2 implementation
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Mobile Ad-hoc Networks <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 27 Nov 2023 07:11:26 -0000

On Sat, Nov 25, 2023 at 3:32 PM Juliusz Chroboczek <> wrote:
> Hi Charlie,
> > I do not have an implementation.
> It is my understanding that Henning has concerns about the implementability
> of AODVv2.  Given Henning's track record, I recommend that we should not
> dismiss his concerns.

Hi Juliusz, hi Charlie,

I would not say that AODV (v1 or v2) is impossible to implement (some
people have done it), but it's much harder to do on most general
purpose operation systems than OLSR(v1 or v2) because of its necessary
interaction with the forwarding plane.

I think I have seen three AODV (v1) implementations in my life, two of
them NS-2 emulator patches (I don't trust NS-2 code at all, most
routing implementations take a lot of liberties that cannot be done on
real software/hardware)  and one of them Linux... the Linux one was a
mess, completely with a Linux Kernel module for a kernel 5+ years old
(which made it in fact unsable).

It seems no one ever took the time to seem if there is a good way to
write the "ICMP-trickery/route-status-monitoring" in a clean way,
which is most likely also the reason why I never heard about an IPv6
AODV implementation, which would need a different ICMPv6 based hack.

That's why I would like to see a running implementation of AODVv2...
it's the only way to validate that you can build interoperable
implementations from the current draft. It's also the only way to test
if the metric integration in AODVv2 is working reasonably well,
because I don't think ANY routing protocol will do us good with
hop-count metric on any wireless radio that supports multiple data

Henning Rogge