Re: [manet] (DLEP) Relative Link Quality and routing metrics

Teco Boot <> Fri, 20 April 2018 12:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 009E112E87F for <>; Fri, 20 Apr 2018 05:02:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-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 T3pQ4hwjPMMD for <>; Fri, 20 Apr 2018 05:02:11 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:400c:c0c::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EF56312D890 for <>; Fri, 20 Apr 2018 05:02:10 -0700 (PDT)
Received: by with SMTP id u11-v6so22303966wri.12 for <>; Fri, 20 Apr 2018 05:02:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=bXLcwv7xOm8DohGjX8Z2X5dKnPSS6jNBTY/Qy1EJhEQ=; b=OmKUnvd3ZDtlMAgtCDyCwkYNiveC5xO7R6+HPT38Qd/eLFFMRQSHbCtteda4trcA39 mzZnPgZUxA0/R1YS/Q78mkcbXh5YEC9xGnBtQCqiKGwKmfwXG99wlzObRAbE/nY8W8G/ cOv8W0jvOzkRUKe1DmC7cRgCFJRMyZ7lhrq1n18Xca2wixyssCbweDA/Ddg9Lzp/MBJl lD0kTyhpAof9CehSIEUlKsPcZ/KfPLi8a7FBl/p0toaTyCQ1tIOfyTza84Pxwgm0b+kG WG/UMdrzDa5ooVf0tfaIFjjBogOY2SR4n2TPKCC8DeptTCSAGzQ26oCvjBT1gFYEOHBr V35A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=bXLcwv7xOm8DohGjX8Z2X5dKnPSS6jNBTY/Qy1EJhEQ=; b=L9xdE806ngb8hIurHnbA05yXM1QYxq6EnNlN83wdKZHoEq7vcJkrBrhNu7UG25t86U Pdwv71XICHW4MR0Hfkq7Q1sPo1iNfI65El6MCMYd/gHNHRmGm7otMsIYTebDNrJwA9YL 7AkZRtEjMyDsItIRrnZZFJEn9PkhFpJk+VEEGjuUbLykwiuZFDOYIDOeowu5fVXhi//Q l/opR1x/WYxhhAAcoh1d2K+Ygdkm0862YQLFQFPb47vKTWwiDnc6ui1so1njAitjN7TG 8MyUuHZKsTLvEYSEPoQvnbNbx3RqpPKLABkHk/el7TIDdLw8ZJI3E9j8qcpzYOlHggzg 4/sw==
X-Gm-Message-State: ALQs6tAEYWStkwR6lOJSl1Q9IDAmcIDKO2kpDdWpn+nNR5+XXoeN887h 8d9L/UdD5X2QXKvx3UmgN2YSzA==
X-Google-Smtp-Source: AIpwx48a4Xnxp4CV4C4DX6j+LkE1eY/tl5Gd74+vFDZ1lElqW00WoA4AlWDxmitXMGWLaLbE4N2ogg==
X-Received: by with SMTP id b41mr7848192ede.255.1524225729027; Fri, 20 Apr 2018 05:02:09 -0700 (PDT)
Received: from ([2001:1c01:3106:6c00:14a4:7c50:4590:ad22]) by with ESMTPSA id p36sm4368101eda.43.2018. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Apr 2018 05:02:07 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
From: Teco Boot <>
In-Reply-To: <>
Date: Fri, 20 Apr 2018 14:02:06 +0200
Cc: Rick Taylor <>, "" <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <>
To: Henning Rogge <>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <>
Subject: Re: [manet] (DLEP) Relative Link Quality and routing metrics
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mobile Ad-hoc Networks <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 20 Apr 2018 12:02:18 -0000

Assume two types of radio's.

First one is 802.11 type of radio. It has rate adaption and retry statistics. It reports CDR, this is the *good-put* the radio would have taking all the airtime. In this case, utility of RLQ is low.
But when the radio reports only the average or most recent *TX rate*, the RLQ can be of value. At higher rates, RLQ would be 100, because rate adaption takes care of variation in link budget. But at lower rates and high retry ration (and backoff timers... RLQ would provide kind of fast DAT, when RLQ is based on RSSI and/or retry counters.

Second one is more like a legacy data-radio. It has fixed rate, fixed TX power and it is often used for broadcast, i.e. the messages are addressed to all receivers. For the sender, RLQ is always 100, it doesn't mater if there is any receiver. In military, it is called fire and forget. But for receivers, there is a variation in metrics. Nearby nodes would receive all packets, nodes far from the sender would receive nothing. Somewhere between, nodes would receive part of the messages sent by a node. This is called the grey zone. Reported metrics could be loss ratio, RSSI, Eb/No or RLQ. Here, RLQ could be a compound value, based on the mentioned metrics.

Because RLQ would be very specific to the type of radio, you could design some kind of plugin or profile mechanism, where an administrator could select a calculation model.

I did some work using RSSI to RLQ mapping, the router used that to calculate the routing protocol metric. I used a lookup table. Tuning the table is tough, different conditions need different mapping.


> Op 20 apr. 2018, om 13:05 heeft Henning Rogge <> het volgende geschreven:
> Sorry,
> but this does not help...
> lets say I estimate the link cost for a link (based on data-rate) to be 1000...
> if the radio reports RLQ=100, I would keep the 1000... but how do I
> modify it for a RLQ of 80... or 50... or 1?
> If I cannot integrate the value into the cost metric, I have no use
> for the value. Unfortunately it is often the ONLY value the radio
> reports.
> Henning
> On Fri, Apr 20, 2018 at 1:02 PM, Rick Taylor
> <> wrote:
>> I have always suggested that RLQ should be a measure of how hard the
>> modem is working to maintain the link, i.e. the higher the RLQ, the
>> more stable the link is, and a low RLQ indicates that the link may well
>> radically change metrics, or dissapear soon.
>> One can imagine a sophisticated modem maintiaining a link in very
>> adverse conditions, reporting a low RLQ, but otherwise good metrics.
>> Whether RLQ is a good metric to use as a route cost is a more difficult
>> question.  I've always been of the opinion that RLQ and Resources make
>> a good tie-breakers, but CDR and Latency make better 'primary' metrics.
>> Hope that helps a little?
>> Rick
>> On Fri, 2018-04-20 at 10:00 +0200, Henning Rogge wrote:
>>> Hello,
>>> I am currently looking for a good way to integrate the RLQ value of
>>> DLEP into a cost based routing metric, e.g. DAT. But I am not sure
>>> how
>>> to do this...
>>> has anyone here good experience using RLQ and maybe an advise how
>>> "hard" you should penalize a link with a RLQ less than 100?
>>> Henning Rogge
>>> _______________________________________________
>>> manet mailing list
> _______________________________________________
> manet mailing list