i guess weight never changed the metric, it just gave the final decision between two routes of equal cost/hopcount. (but not toally sure never really used it)<div><br></div><div><div>nearest equivalent is using lqmult, but it affects olsrd routing globally, not just local as the weight likely was doing it,.</div>
<div><br></div><div>Markus</div><div><div><br><div class="gmail_quote">On Thu, Mar 29, 2012 at 8:46 PM, Michael Rack <span dir="ltr"><<a href="mailto:michael.rack@rsm-freilassing.de">michael.rack@rsm-freilassing.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000">
    <tt>Yes it should change the metric for this route. But it does not.<br>
      <br>
      Here is a example how the routing looks like from txt_info-Plugin:<br>
      <br>
    </tt><tt>VIEW IS FROM INTERNET-ROUTER</tt> as specified in my last
    mail in section Network-Design / Schema...<br>
    <br>
    The focus is on <tt><a href="http://172.16.12.160/27" target="_blank">172.16.12.160/27</a> it should be routed via
      "bond0"</tt><br>
    <tt>
      <blockquote type="cite">ROUTE              HOST         
        Metric     Interface<br>
        <a href="http://172.16.12.32/27" target="_blank">172.16.12.32/27</a>    172.16.12.4   1  1.000   bond5   # ROUTER B.1<br>
        <a href="http://172.16.12.96/28" target="_blank">172.16.12.96/28</a>    172.16.12.4   2  2.000   bond5   # ROUTER B.2<br>
            hidden node on metric 3<br>
        <a href="http://172.16.12.128/27" target="_blank">172.16.12.128/27</a>   172.16.12.4   4  4.000   bond5   # ROUTER C<br>
        <a href="http://172.16.12.160/27" target="_blank">172.16.12.160/27</a>   172.16.12.4   5  5.128   bond5   # ROUTER D<br>
        <br>
        <a href="http://172.16.13.160/27" target="_blank">172.16.13.160/27</a>   172.16.12.5   1  1.000   bond0   # <tt>ROUTER
          A.1</tt><br>
        <a href="http://172.16.14.32/27" target="_blank">172.16.14.32/27</a>    172.16.12.5   2  2.000   bond0   # <tt>ROUTER
          A.2</tt><br>
        <a href="http://172.16.13.32/27" target="_blank">172.16.13.32/27</a>    172.16.12.5   3  3.000   bond0   # <tt>ROUTER
          A.3</tt></blockquote>
      This route should only been selected if "bond0" failed.<br>
      <br>
      This is the route as it should be:<br>
      <blockquote type="cite">ROUTE              HOST         
        Metric     Interface<br>
        <a href="http://172.16.12.32/27" target="_blank">172.16.12.32/27</a>    172.16.12.4   1  1.000   bond5   # ROUTER B.1<br>
        <a href="http://172.16.12.96/28" target="_blank">172.16.12.96/28</a>    172.16.12.4   2  2.000   bond5   # ROUTER B.2<br>
        <br>
        <a href="http://172.16.13.160/27" target="_blank">172.16.13.160/27</a>   172.16.12.5   1  1.000   bond0   # ROUTER A.1<br>
        <a href="http://172.16.14.32/27" target="_blank">172.16.14.32/27</a>    172.16.12.5   2  2.000   bond0   # ROUTER A.2<br>
        <a href="http://172.16.13.32/27" target="_blank">172.16.13.32/27</a>    172.16.12.5   3  3.000   bond0   # ROUTER A.3<br>
        <a href="http://172.16.12.128/27" target="_blank">172.16.12.128/27</a>   172.16.12.5   4  4.000   bond0   # ROUTER C<br>
        <a href="http://172.16.12.160/27" target="_blank">172.16.12.160/27</a>   172.16.12.5   5  5.000   bond0   # ROUTER D</blockquote>
      <br>
      So the weight parameter does not apply. Is this a bug in OLSR?<br>
      <br>
      The weight </tt><tt>parameter </tt><tt>is activated on </tt><tt>ROUTER
      C.<br>
    </tt><tt>ROUTER C sees </tt><tt>ROUTER A.3 and </tt><tt>ROUTER
      B.2.<br>
    </tt><tt><br>
      ROUTER C gives </tt><tt>ROUTER A.3 a weight of 5 and </tt><tt>ROUTER
      C weight of 10. </tt>So <tt>ROUTER A.3 should be selected.</tt><div class="im"><br>
    <br>
    <pre cols="72">Liebe Grüße aus Freilassing,

Michael Rack
RSM Freilassing
-- 
RSM Freilassing                 Tel.: <a href="tel:%2B49%208654%20607110" value="+498654607110" target="_blank">+49 8654 607110</a>
Nocksteinstr. 13                Fax.: <a href="tel:%2B49%208654%20670438" value="+498654670438" target="_blank">+49 8654 670438</a>
D-83395 Freilassing            <a href="http://www.rsm-freilassing.de" target="_blank">www.rsm-freilassing.de</a> </pre>
    <br></div><div class="im">
    Am 29.03.2012 17:15, schrieb Markus Kittenberger:
    </div><blockquote type="cite">i guess the weight does/did only with hopcount
      metric,..
      <div><div class="h5"><div><br>
      </div>
      <div>Markus</div>
      <div><br>
      </div>
      <div>p.s. true 0.5.5 is a previous version, but this was very very
        very long ago. (-;<br>
        <br>
        <div class="gmail_quote">On Thu, Mar 29, 2012 at 3:56 PM,
          Michael Rack <span dir="ltr"><<a href="mailto:michael.rack@rsm-freilassing.de" target="_blank">michael.rack@rsm-freilassing.de</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear
            olsr-users!<br>
            <br>
            I have a bad behavior and hope to get some help.<br>
            <br>
            I run only P2P Links (AP & STA) via wireless-lan and
            direct ethernet connections. Every node runs currently olsr
            version 0.6.0.<br>
            <br>
            The Problem:<br>
            I have several upstreams and like to define which upstrem to
            be used via the weight parameter. In previous versions of
            olsr this worked fine (as i can remember v0.5.5). Now it
            dosn't.<br>
            <br>
            My Settings:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
              Willingness             3<br>
              LinkQualityLevel        2<br>
              LinkQualityAlgorithm    "etx_ff"<br>
              UseHysteresis   no<br>
              TcRedundancy    2<br>
              MprCoverage     1<br>
              <br>
              InterfaceDefaults<br>
              {<br>
                     Ip4Broadcast   255.255.255.2555<br>
                     HelloInterval   2.0<br>
                     HelloValidityTime   60.0<br>
                     TcInterval  5.0<br>
                     TcValidityTime  120.0<br>
                     MidInterval 5.0<br>
                     MidValidityTime 120.0<br>
                     HnaInterval 5.0<br>
                     HnaValidityTime 120.0<br>
              }<br>
              <br>
              Interface "wan"<br>
              {<br>
                     Mode "ether"<br>
                     Weight 10<br>
              }<br>
              <br>
              Interface "vlan2"<br>
              {<br>
                     Mode "ether"<br>
                     Weight 2<br>
              }<br>
              <br>
              Interface "vlan4"<br>
              {<br>
                     Mode "ether"<br>
                     Weight 5<br>
              }<br>
            </blockquote>
            <br>
            But currently the wan-interface is selected. While
            everything goes via "wan" the routing change to "vlan4" but
            after a few minutes the routing switch back to "wan" and i
            get a bad packet-loss for 4 seconds while the routing is
            switching back to "wan" - but i don't know why because both
            links are up and running. I don't know where the packets get
            loosed.<br>
            <br>
            Currently Network-Design:<br>
            <br>
            <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">        
               INTERNET-ROUTER<br>
                              |<br>
                   / ------- / \ ------- \<br>
                ROUTER A.1           ROUTER B.1<br>
                   |                     |<br>
                ROUTER A.2           ROUTER B.2<br>
                   |                     |<br>
                ROUTER A.3               |<br>
                   |                     |<br>
                   \ --------\ / ------- /<br>
                     "vlan4"  |   "wan"<br>
                           ROUTER C<br>
                              |<br>
                           ROUTER D<br>
                              |<br>
                            CLIENT<br>
            </blockquote>
            <br>
            <br>
            MTR is done via ROUTER D and the internet. The routing
            decision is made on Router C that is multihomed (A.3 &
            B.2).<br>
            <br>
            So what have i to do, to make WEIGHT working?<br>
            <br>
            Liebe Grüße aus Freilassing,<br>
            <br>
            Michael Rack<br>
            RSM Freilassing<span><font color="#888888"><br>
                -- <br>
                RSM Freilassing                 Tel.: <a href="tel:%2B49%208654%20607110" value="+498654607110" target="_blank">+49 8654 607110</a><br>
                Nocksteinstr. 13                Fax.: <a href="tel:%2B49%208654%20670438" value="+498654670438" target="_blank">+49 8654 670438</a><br>
                D-83395 Freilassing            <a href="http://www.rsm-freilassing.de" target="_blank">www.rsm-freilassing.de</a><br>
                <br>
                <br>
                -- <br>
                Olsr-users mailing list<br>
                <a href="mailto:Olsr-users@lists.olsr.org" target="_blank">Olsr-users@lists.olsr.org</a><br>
                <a href="https://lists.olsr.org/mailman/listinfo/olsr-users" target="_blank">https://lists.olsr.org/mailman/listinfo/olsr-users</a><br>
              </font></span></blockquote>
        </div>
        <br>
      </div>
    </div></div></blockquote>
  </div>

</blockquote></div><br></div></div></div>