<div dir="ltr">Hi Henning, <div><br></div><div>Thanks for your valuable help. </div><div><br></div><div>I have tested with just <span style="font-size:12.8000001907349px"><i>olsrd2_static eth1</i> and everything worked fine. </span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px">In my first trials, I disabled plugin which uses libnl to compile it. Since I don't use wifi, I thought that I don't need it. But it didn't work with this simple command (</span><i style="font-size:12.8000001907349px">olsrd2_static eth1</i><span style="font-size:12.8000001907349px">) than I added the other parameters. However it didn't work. Than, I thought that it would be because of libnl. Than I compiled with libnl, but I didn't test again with that simple command (</span><i style="font-size:12.8000001907349px">olsrd2_static eth1</i><span style="font-size:12.8000001907349px">). After your advise, I checked and it worked. Thanks again. </span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px">After working the first scenario, I tried my real need which is about choosing the best link in terms of bandwidth and reliability. </span></div><div><span style="font-size:12.8000001907349px">Here is my real need, which is choosing the best route, and dynamically change when the conditions change. I believe OLSRv2 can handle my need.</span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px">10.0.1.1 < - 2 Mbps - > 10.0.1.2 10.0.2.2 </span><span style="font-size:12.8000001907349px">< - 2 Mbps - > 10.0.2.3</span></div><div><span style="font-size:xx-large"> A B C</span><br></div><div><span style="font-size:12.8000001907349px">10.0.3.1 </span><span style="font-size:12.8000001907349px">< - 128 kbps %5 loss - > 10.0.3.3</span><br></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px">After, using olsrv2 I would like to reach C from A via B. But it chooses direct link which is 128 kbps.</span></div><div><br></div><div><span style="font-size:12.8000001907349px">But, when I run the scenario, it didn't worked in the way I want. Could you help me about configuring the olsrd2 to make my scenario work. </span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px">By the way, there is an other strange behavior about routing table. Such that OLSR adds its own IP addres into the routing table with a next hop destined to other machine. </span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px"> Destination Gateway Dev </span></div><div><span style="font-size:12.8000001907349px">At machine A, it added </span><span style="font-size:12.8000001907349px">10.0.3.1 10.0.1.2 eth1</span></div><div><span style="font-size:12.8000001907349px">At mach</span><span style="font-size:12.8000001907349px">ine B, it added </span><span style="font-size:12.8000001907349px">10.0.2.2 10.0.2.3 eth4</span></div><div><span style="font-size:12.8000001907349px">At mach</span><span style="font-size:12.8000001907349px">ine C, it added </span><span style="font-size:12.8000001907349px">10.0.3.3 10.0.2.2 eth2</span><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div>you can note that Destination addresses are actually their own addresses. In practice there is no problem because operating system doesn't use those routing table entries. I think, it would be nice to not add them into the routing table.</div><div><br></div><div><span style="font-size:12.8000001907349px">You can find my testing environment and results as attached. Name of virtual machine indicates the location at topology. </span><br></div><div><br></div><div>Regards,</div><div><br></div><div>Note: I am using 64 bit CentOS 6.5.</div><div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 4, 2015 at 8:04 AM, Henning Rogge <span dir="ltr"><<a href="mailto:hrogge@gmail.com" target="_blank">hrogge@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Tue, Mar 3, 2015 at 8:33 PM, Taner Kurtulus <<a href="mailto:tkurtulus@gmail.com">tkurtulus@gmail.com</a>> wrote:<br>
> Thanks Henning, for very fast reply.<br>
><br>
> Now, I am out the office. I could only provide address information. But if<br>
> those are not sufficient, I will send the output of "ip addr" tomorrow.<br>
><br>
> Here is the address configurations.<br>
> A: 172.1.16.151 <-> B1:172.1.16.162 B2:192.168.1.128 <-> 192.168.1.129<br>
><br>
> What kind of parameters I should see from the output of ip addr?<br>
><br>
> By the way, I couldn't find any example configuration file. Is there any?<br>
<br>
</span>The default configuration is "no" configuration.<br>
<br>
Start with just adding all relevant interfaces to the parameter list.<br>
<br>
> olsrd2_static eth1<br>
<br>
To make your debugging easier you could just skip the third VM and the<br>
second interface on the second VM. Olsrd2 should still produce an IPv4<br>
routing entry to each one-hop neighbor.<br>
<span class="HOEnZb"><font color="#888888"><br>
Henning Rogge<br>
</font></span></blockquote></div><br></div></div>