Re: [manet] RFC7181 (OLSRv2) trouble with ANSN and router restart

Christopher Dearlove <> Fri, 23 July 2021 14:04 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 52D813A0A73 for <>; Fri, 23 Jul 2021 07:04:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 x9UBGuoPHcst for <>; Fri, 23 Jul 2021 07:04:48 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::331]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 713BE3A09D7 for <>; Fri, 23 Jul 2021 07:04:46 -0700 (PDT)
Received: by with SMTP id h24-20020a1ccc180000b029022e0571d1a0so1670055wmb.5 for <>; Fri, 23 Jul 2021 07:04:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Q3hoCiazDMFhOgjZMExdeKPBcewSyW6ZWS3+zoMgFww=; b=h+OOj/UHMeoYQcCeLgo3rrTiGfFOpgjMpCRlE7g/rmysTsqnNSWm8yBr+08IkNiHlv oBwd9K8cny8dYEoquPdZmKxTO4W2YpJACe8STMhIx+79BLp0qSAzo6RDZCUi8fcMJJFD uQB1emxEYlspOuW2UgiD4ctQx+ejU6e49Io0KSRpdYwOko3rSds0lx8jGVOr4fqd+mYp iJk9PP3mYFrsTNlUMJIGj0LLgCSI6oxOUHQ1beCnBmkzx3aHSJUMoIgeV6NO4OOjafSx K/px7RyfYaeYaZnjt531urPJx9xiexSDayPRhluOkDMBAQONiFn3YMGLJp5ZerrhSmhM sFIA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=Q3hoCiazDMFhOgjZMExdeKPBcewSyW6ZWS3+zoMgFww=; b=bbDcMbzsFJkVEQ9P1U/mZzSBU6s6qvNg9xs3fibIQRh01WmzfhsPKE64dfF/9Zvay9 Qj1xB4F1dX1ny8m4FybJ59J6vBwqvNdYwfgkieuELEZYIWkNaUooOt98iioZqEeL+jT0 Ljz4od7e8HFa/j+/tnsoGFKqx1a6Th5gs/+7O2pFHxOG26JrYgdfcd+sXL83ED8hYszE yiSel/WI7ANpl/0QIh+pAcWyfKPuGoQ0wq+X2yKewcoBFwreewARi2uOyOYl1RPrHr8c EJdw9aFx/yWXhOd5i8Tv6OiXVWq3PkN+Egq1Mq10YiihQga8pk55x/1be3u8L7A5VYqN X02w==
X-Gm-Message-State: AOAM531K/kYowoBQ/QG2DH3IQhoiqeqeQjPV6t06EKHKaQ5Zt5LpTdwh Fo7f997D0yZ2xJHwWZaYnlr/dLQDNPI=
X-Google-Smtp-Source: ABdhPJyotB5I7SE6Z1tIQDD+VLz4xcqCtLOJFa58uo46xk+klykklEJ3JL/OkIKy/G20K1BlPRlirw==
X-Received: by 2002:a1c:4b0a:: with SMTP id y10mr4696312wma.178.1627049083597; Fri, 23 Jul 2021 07:04:43 -0700 (PDT)
Received: from [] ( []) by with ESMTPSA id o5sm5018032wms.43.2021. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 23 Jul 2021 07:04:42 -0700 (PDT)
From: Christopher Dearlove <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_CB68A1F9-FB16-4E25-A322-2004E718A7E6"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.\))
Date: Fri, 23 Jul 2021 15:04:41 +0100
In-Reply-To: <>
References: <> <> <>
X-Mailer: Apple Mail (2.3654.
Archived-At: <>
Subject: Re: [manet] RFC7181 (OLSRv2) trouble with ANSN and router restart
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mobile Ad-hoc Networks <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 23 Jul 2021 14:05:02 -0000

I didn’t addresss this.

> On 23 Jul 2021, at 07:11, Rogge, Henning <> wrote:
> The problem is easy to solve on the "sender" side, but if we manage I would like to solve it on the receiver side (of TCs).

First, I don’t think you have the receiver side issue you note. The information will eventually timeout unless the sender sends incomplete messages with valid MSN and latest ANSN. But that’s something it could do anyway.

There are heuristics you might add to say “ignore this message as it fails a smell test”. You can’t stop a router doing that, nor should you. There are various heuristics you could try. Some relevant to this situation, others not. One such is that if you see a message where MSN and ANSN show opposite behaviour, that’s a sign that router is misbehaving. If you interpret misbehaving as “probably reset, I should wipe all its data” that’s drastic but possible. But doing so on the basis of one message is a bit much. And I don’t think you’ll ever get a set of rules applicable to all situations. Which is why I used the term heuristics.

Either in an informational RFC on router reset behaviour, or in a non-normative annex to a standards track RFC, you could include advice on behaviour to look out for that suggests a misbehaving/reset router and that you MAY (no stronger) discard messages or even wipe the database if you see that, probably more than once.

In short, I don’t think this is a soluble, here are rules that always work, problem. But if you find a real problem in a real network you could include code that makes a tradeoff of handling that case while possibly making other cases behave less well. (For example the multiple MSNs/ANSNs I suggest in my last email might trigger some heuristics.) Information might help a network operator. If you are supplying an OLSRv2 implementation and have a heuristic you think is often useful, you could include it as an option. But it would be very easy to think up heuristics that in reality aren’t much use.