[Olsr-dev] Which metric is currently running on OLSRd2

[Syed Salman Haider Rizvi]

Hi ,      I just wanted to know that in the previous mails you told me to manually turn off ett which basically takes me into the ETX . But after i ran it in the daemon is there anyway to reconfirm that which metric is really running . 
Thanks 
Salman

> From: (spam-protected)
> Date: Wed, 19 Mar 2014 12:01:56 +0100
> Subject: Re: [Olsr-dev] Which metric is currently running on OLSRd2
> To: (spam-protected)
> CC: (spam-protected)
> 
> Hi,
> 
> Olsrd2 runs an airtime metric as the default implementation, one that
> we are in the process of standardizing:
> 
> https://tools.ietf.org/html/draft-rogge-baccelli-olsrv2-ett-metric-04
> 
> It use a directional measurement of packet loss and link speed from
> the linux wifi kernel to calculate.
> 
> There is also a variant that use a bi-directional packet loss
> measurement as described in the original ETT papers.
> 
> There is no ETX implementation for OLSRd2, but of course if your
> kernel cannot supply the link speed, the airtime metric degrades into
> a packet loss metric.
> 
> Henning Rogge
> 
> On Wed, Mar 19, 2014 at 11:22 AM, Syed Salman Haider Rizvi
> <(spam-protected)> wrote:
> > Hi All ,
> >
> >       Just let u guys know the scenario . I m running 14 hops testbed for
> > performance evaluation of (ETT vs ETX vs HC) on  olsrd2 . Last time i tried
> > both ett and etx on my testbed but my route was not changing and even
> > getting the same throughput on both ETT and ETX . So is there anyways to see
> > which metric is currently on and for HC i will surely use olsrd1 but i think
> > there will be a lot difference in the throughput maybe the size of olsrd1
> > and olsrd2 packets are different ?
> >
> > Salman
> >
> > --
> > Olsr-dev mailing list
> > (spam-protected)
> > https://lists.olsr.org/mailman/listinfo/olsr-dev
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20140319/55c1663c/attachment.html>