<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16609" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=742512113-20022008><FONT face=Arial
color=#0000ff size=2>See also my previous e-mail.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=742512113-20022008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=742512113-20022008><FONT face=Arial
color=#0000ff size=2>If you know a way to retrieve the actual per-neighbor
auto-rate as chosen by the radio, I would like to feed that in OSLR-LC .
I'm unsure whether current ad-hoc mode drivers keep that information and can
deliver the information at that detail level (e.g. via /proc ) to external
processes.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=742512113-20022008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=742512113-20022008><FONT face=Arial
color=#0000ff size=2>The current OLSR-LC provisions in taking into account
the per-link speed in its link cost calculation. By default it is set,
for each link on a certain network interface, to the pre-configured
speed value for that interface (parameter "MediumSpeed").</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=742512113-20022008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=742512113-20022008><FONT face=Arial
color=#0000ff size=2>The current OLSR-LC does not provision in asymmetric link
costs; that would be a nice extension for a next
releast.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=742512113-20022008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV><FONT face=Arial color=#0000ff
size=2></FONT><FONT face=Arial color=#0000ff size=2></FONT><BR>
<DIV class=OutlookMessageHeader lang=nl dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>Van:</B> markus.kittenberger@gmail.com
[mailto:markus.kittenberger@gmail.com] <B>Namens </B>Markus
Kittenberger<BR><B>Verzonden:</B> woensdag 20 februari 2008 14:19<BR><B>Aan:</B>
Erik Tromp<BR><B>CC:</B> Henning Rogge;
olsr-dev@lists.olsr.org<BR><B>Onderwerp:</B> Re: [Olsr-dev] OLSRd 0.5.4 and
0.5.5 with ETT available<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #cccccc 1px solid"><BR>>
Don't you think the subject of your mail is a little bit misleading
?<BR><BR>If you choose a fixed (pre-configured) bit speed value for each
network<BR>interface (e.g. 11 or 54 MBit/s) the link cost is effectively the
ETT as it<BR>would be with that bit speed.</BLOCKQUOTE>
<DIV><BR>fixed values will only work with fixed wireless rates, <BR>(using the
same value) on both senders and receiver side!!<BR></DIV><BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #cccccc 1px solid">If
you have a mechanism to read the actual speed of each available
network<BR>interface that would be a good improvement. In that way we could
use the<BR>radio-layer ARF mechanism as indication of link speed.</BLOCKQUOTE>
<DIV><BR>are you keeping in mind, that in auto rate mode the link speed may/will
differ to different neighbours<BR><BR>so there is no actual speed per interface,
on a wireless network device, just per link.<BR><BR>even if you set a fixed
transmission rate, receiving rate is determined by the neighbours transmission
rate<BR></DIV><BR>Markus
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #cccccc 1px solid"><BR></BLOCKQUOTE></DIV><BR></BODY></HTML>