Re: [manet] AODVv2 implementation

Henning Rogge <hrogge@gmail.com> Sat, 03 February 2024 22:25 UTC

Return-Path: <hrogge@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E0CDC14F5EF for <manet@ietfa.amsl.com>; Sat, 3 Feb 2024 14:25:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.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_NONE=-0.0001, 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: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jc8UQrJlyTad for <manet@ietfa.amsl.com>; Sat, 3 Feb 2024 14:25:44 -0800 (PST)
Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com [IPv6:2a00:1450:4864:20::629]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 053F3C14F5E3 for <manet@ietf.org>; Sat, 3 Feb 2024 14:25:44 -0800 (PST)
Received: by mail-ej1-x629.google.com with SMTP id a640c23a62f3a-a37878ac4f4so8935766b.2 for <manet@ietf.org>; Sat, 03 Feb 2024 14:25:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1706999142; x=1707603942; darn=ietf.org; 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=U718rstLsM+wqbQ75rIBd/6XtGzFJaWiNLgOKY/+VaE=; b=i/1gLwB0tmbRYfKEt/TXgCU+a40/VrEJMsQSFD+noJdRYtECf/EM2uixNw5JixhvvR G/6J6TP46dxHNyHbozGua3bxyqidy548B/73kQf3QpoKF/QFQ+Cn7sFit56slGJQArRc XP0iIDf1gfht0bhR8GZnreyveBj9yD0seyMoJJ8k2YjNCK+H3bBaG/bIsMc87QChRMM6 sMTYqn+ZOGiraOlqEB0aD4uYULtamtY53Z+XrvLvOdwNw/nIbrMNSEolArRiogzpvyVf rzT5BQaIygnyW/4+nYNCw5Td+4FZaEKFscVvSfbfuhBAtWPmCvTJJZsYxqgpI8Zf7Pmv 7IeQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706999142; x=1707603942; 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=U718rstLsM+wqbQ75rIBd/6XtGzFJaWiNLgOKY/+VaE=; b=JgaoBdFjoVS408zNDAk+C/CvKsjKLzikvvBUCOa1RwEs7rFt1PBUnjpcywlLfiWM3H +Nc4zs90OQbcEsgx6vj05qtGgUlVeOyH3hBS45CNkcj3Qbq2o73uGNXIfMN/LeJNkcyO ohtQACMszXeNojEZvK5MLz8PNpRx1nzVmKkjkHrI4NVPrvP/3QDHF62/eSDhlhlNHfuv RM3ePrOvTwNFRYg2XyXCPgZIgDn/rlM9encSsstsb/XotFYfSQ58kC8g6gyja43IWjn7 Fy5jugGcGa04IBZKT0nDhp/ZF7WLflJsDd4YD8DVt7qmhbX9g99E7bXP7ab03KgMONMJ r7pQ==
X-Gm-Message-State: AOJu0YyKzGx/GQlfKIYjxmT4jDcYtOXPRcGXeMw0O8oJsY+UyO9Y3M5c 2iTMCuHVqVaTkex2OtIHD6oz8aOU3AN9Ob4ViuKVd2D74Q7I45SK//8VCLGDzZjbrKNUSTywp0h IQDQ+U+hMJ+ffhUQIVUBFbjV/lg8=
X-Google-Smtp-Source: AGHT+IHLf/1w9AJVhfdAo9Nvl33ffuVyd8Y0lyhVZo+vSHifxteWnnew7TsKomm9gfeDeGRU//5amjD2OOPV4SG42os=
X-Received: by 2002:a17:906:cc47:b0:a37:20be:edaf with SMTP id mm7-20020a170906cc4700b00a3720beedafmr3247018ejb.62.1706999142205; Sat, 03 Feb 2024 14:25:42 -0800 (PST)
MIME-Version: 1.0
References: <PH7PR14MB5368D3F677021CAFA04831F4BBB1A@PH7PR14MB5368.namprd14.prod.outlook.com> <740cf920-605d-4376-9db5-4409794bedb0@computer.org> <CAGnRvur98cmOqrB6b7Q=VsfvrBEY9goWn-zrXWM49mCj-+7zPw@mail.gmail.com> <7334e18e-d2aa-4f99-b79c-869b7ee1c836@computer.org> <87h6l9oqdk.wl-jch@irif.fr> <CAGnRvur17OvFogQnJspv=2ezuE41LQkgj5fEv5mJRGG9iYxZDw@mail.gmail.com> <CAL95ndJoFOay1Spin5vMfZV5KMHO5DkG7KhyHNo6KuAC3vm74w@mail.gmail.com> <875y1mgc9g.wl-jch@irif.fr> <CAGnRvurA7rg1R74-S4OgmFBE-3dqtgurF2=dGqYo69WMn6ynyA@mail.gmail.com> <c8fb9dfe-59d7-49b5-9d4d-33470a79dee8@earthlink.net> <CAGnRvuqKGm6XVLkOOMG28EXuBRXkvTqGVEf-du8q220S3H2aiA@mail.gmail.com> <875xz5mu2d.wl-jch@irif.fr> <CAGnRvuqPPvZWhO9O4q5kuJQg5Sf=nRtR-3F6wpABXnH+bdiQNg@mail.gmail.com> <871q9tme3g.wl-jch@irif.fr>
In-Reply-To: <871q9tme3g.wl-jch@irif.fr>
From: Henning Rogge <hrogge@gmail.com>
Date: Sat, 03 Feb 2024 23:25:16 +0100
Message-ID: <CAGnRvuqZbOBGS111eutfic50g7S0_QM+LpFQ7MAf7JWqK5STwg@mail.gmail.com>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: Charlie Perkins <charles.perkins@earthlink.net>, "manet@ietf.org" <manet@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/FGjvKmGfChwnB3PCbn7R8Wy1UCs>
Subject: Re: [manet] AODVv2 implementation
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Feb 2024 22:25:44 -0000

Most AODV implementations I got a hint on had a custom kernel
module... for something like Kernel 2.4.x.

Henning Rogge

On Sat, Feb 3, 2024 at 10:29 PM Juliusz Chroboczek <jch@irif.fr> wrote:
>
> >>> For detecting a route request for a non-existing route my idea always
> >>> was to use a TUN device and point a route to the whole MANET (or even
> >>> the default route) into it.
>
> > > That's going to work, but it pushes every packet through two kernel-user
> > > transitions, which makes it unsuitable for production use.
>
> > As soon as you set a more specific route, the traffic will not go into
> > the TUN anymore.
>
> Ah, so instead of pushing all traffic through userspace, as I envisioned,
> you use the TUN hack for unknown destinations, but establish normal kernel
> routes or known destinations.  I see, that's why you need a way to monitor
> which routes are being actively used.
>
> Charlie, could you please tell us which of these two techniques is the one
> that you envision, and tell us what's the bit that we're still missing?
>
> -- Juliusz