<div>it may work nearly immediatley if u properly shut down the router instead of switching off, or unplugging power.<br><br>and if u have 0.5.6-r8 (newest release), as these send (and completely understand) farewell messages (= some empty hello and tc messages), olsrd sends when it shuts down,..<br>
</div><div><br></div><div>if u just unplug the power, it will never work instantly, as the neighbours must decide that this node is dead, which means they wait for the link to time out,..</div><div><br></div><div>reducing hello interval may speed up things, but it will imho nearly never reach a level that make sense for voip,...</div>
<div><br></div><div>regards Markus</div><div><br></div><div>p.s. your ascii? topology drawing was not readible/viewable for me,.. </div><br><div class="gmail_quote">On Mon, Jan 11, 2010 at 6:14 PM, VbaT S. <span dir="ltr"><<a href="mailto:v_bat@hotmail.com">v_bat@hotmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div>
<span>I installed olsrd on my wrt 54gl
routers from linksys... they are working well... i have 5 of these
routers... they are working in a multihop configuration in a fashion
shown below
<br>
<br>
..............................- router2 -............................................................
<br>
.............................-...............-...........................................................
<br>
...........................-................. -........................................................
<br>
machine1----router1-................- router4 - - - - router5-----machine2
<br>
...........................-..................- ........................................................
<br>
.............................-...............-...........................................................
<br>
..............................- router3 -............................................................
<br>
<br>
- - - - - - wireless connection
<br>
............. Nothing
<br>
<br>now i m doing VoIP communication between machine 1 & 2 ... it
is working well... now one path is selected router 1-2-4-5 or from
routers 1-3-4-5... if a switch off router 2 ... the path should
immediately be selected as 1-3-4-5 but it takes a delay of almost 30
seconds which is bad for VoIP communication... <br>
Now can anybody please tell me how to reduce this delay??<br><br>This is my olsrd.conf<br><br>#<br># <a href="http://olsr.org" target="_blank">olsr.org</a> OLSR daemon config file<br>#<br># Lines starting with a # are discarded<br>
#<br># This file was shipped with the debian olsrd package<br>#<br><br># This file is an example of a typical<br># configuration for a mostly static<br># network(regarding mobility) using<br># the LQ extention<br><br># Debug level(0-9)<br>
# If set to 0 the daemon runs in the background<br><br>DebugLevel 1<br><br><br># Interfaces and their rules<br># Omitted options will be set to the<br># default values. Multiple interfaces<br># can be specified in the same block<br>
# and multiple blocks can be set.<br><br># !!CHANGE THE INTERFACE LABEL(s) TO MATCH YOUR INTERFACE(s)!!<br># (eg. wlan0 or eth1):<br># <br># this is (in most cases) the only configuration you need to change<br><br>#Interface "eth1" "eth0" "wlan0" "wlan1" "ath0" "ath1"<br>
Interface "wlan0" <br>{<br><br> # IPv4 broadcast address to use. The<br> # one usefull example would be 255.255.255.255<br> # If not defined the broadcastaddress<br> # every card is configured with is used<br>
<br> # Ip4Broadcast 255.255.255.255<br><br> # IPv6 address scope to use.<br> # Must be 'site-local' or 'global'<br><br> # Ip6AddrType site-local<br><br> # IPv6 multicast address to use when<br>
# using site-local addresses.<br> # If not defined, ff05::15 is used<br><br> # Ip6MulticastSite ff05::11<br><br> # IPv6 multicast address to use when<br> # using global addresses<br> # If not defined, ff0e::1 is used<br>
<br> # Ip6MulticastGlobal ff0e::1<br><br><br> # Emission intervals.<br> # If not defined, RFC proposed values will<br> # be used in most cases.<br><br> # Hello interval in seconds(float)<br> HelloInterval 6.0<br>
<br> # HELLO validity time<br> HelloValidityTime 600.0<br><br> # TC interval in seconds(float)<br> TcInterval 0.5<br><br> # TC validity time<br> TcValidityTime 300.0<br><br> # MID interval in seconds(float)<br>
MidInterval 10.0<br><br> # MID validity time<br> MidValidityTime 300.0<br><br> # HNA interval in seconds(float)<br> HnaInterval 10.0<br><br> # HNA validity time<br> HnaValidityTime 300.0<br>
<br> # When multiple links exist between hosts<br> # the weight of interface is used to determine<br> # the link to use. Normally the weight is<br> # automatically calculated by olsrd based<br> # on the characteristics of the interface,<br>
# but here you can specify a fixed value.<br> # Olsrd will choose links with the lowest value.<br><br> # Weight 0<br><br><br> # If a certain route should be preferred <br> # or ignored by the mesh, the Link Quality <br>
# value of a node can be multiplied with a factor <br> # entered here. In the example the route <br> # using 192.168.0.1 would rather be ignored.<br> # A multiplier of 0.5 will result in a small<br> # (bad) LinkQuality value and a high (bad)<br>
# ETX value.<br><br> # LinkQualityMult 192.168.0.1 0.5<br><br> # This multiplier applies to all other nodes <br> # LinkQualityMult default 0.8<br> <br><br><br>}<br><br># Fisheye mechanism for TC messages 0=off, 1=on<br>
<br>LinkQualityFishEye 1<br><br><br># ignore topology information from nodes further than 3 hops away<br>#<br># update topology information every 3.0 seconds<br># (on slower embedded hardware with more than 100 nodes use something like 9 sec)<br>
# <br>LinkQualityDijkstraLimit 3 3.0<br><br># IP version to use (4 or 6)<br><br>IpVersion 4<br><br># Clear the screen each time the internal state changes<br><br>#ClearScreen yes<br><br># HNA IPv4 routes<br># syntax: netaddr netmask<br>
# Example Internet gateway:<br># 0.0.0.0 0.0.0.0<br><br>Hna4<br>{<br># Internet gateway:<br># 0.0.0.0 0.0.0.0<br># more entries can be added:<br># 192.168.1.0 255.255.255.0<br>}<br><br># HNA IPv6 routes<br># syntax: netaddr prefix<br>
# Example Internet gateway:<br>Hna6<br>{<br># Internet gateway:<br># :: 0<br># more entries can be added:<br># fec0:2200:106:: 48<br>}<br><br><br># Should olsrd keep on running even if there are<br># no interfaces available? This is a good idea<br>
# for a PCMCIA/USB hotswap environment.<br># "yes" OR "no"<br><br>#AllowNoInt yes<br><br># TOS(type of service) value for<br># the IP header of control traffic.<br># If not set it will default to 16<br>
<br>#TosValue 16<br><br># The fixed willingness to use(0-7)<br># If not set willingness will be calculated<br># dynamically based on battery/power status<br># if such information is available<br><br>Willingness 7<br>
<br># Allow processes like the GUI front-end<br># to connect to the daemon.<br><br>IpcConnect<br>{<br> # Determines how many simultaneously<br> # IPC connections that will be allowed<br> # Setting this to 0 disables IPC<br>
<br> MaxConnections 0<br><br> # By default only 127.0.0.1 is allowed<br> # to connect. Here allowed hosts can<br> # be added<br><br> Host 127.0.0.1<br> #Host 10.0.0.5<br><br>
# You can also specify entire net-ranges <br> # that are allowed to connect. Multiple<br> # entries are allowed<br><br> #Net 192.168.1.0 255.255.255.0 <br>}<br><br># Wether to use hysteresis or not<br>
# Hysteresis adds more robustness to the<br># link sensing but delays neighbor registration.<br># Used by default. 'yes' or 'no'<br># Do not use hysteresis with ETX!<br><br>UseHysteresis no<br><br># Hysteresis parameters<br>
# Do not alter these unless you know <br># what you are doing!<br># Set to auto by default. Allowed<br># values are floating point values<br># in the interval 0,1<br># THR_LOW must always be lower than<br># THR_HIGH.<br><br>
#HystScaling 0.50<br>#HystThrHigh 0.80<br>#HystThrLow 0.30<br><br><br># Link quality level<br># 0 = do not use link quality<br># 1 = use link quality for MPR selection<br># 2 = use link quality for MPR selection and routing<br>
# Defaults to 0<br><br>LinkQualityLevel 2<br><br># Link quality window size<br># Defaults to 10<br><br>LinkQualityWinSize 100<br><br># Polling rate in seconds(float). <br># Default value 0.05 sec<br><br>Pollrate 0.1<br>
<br><br># TC redundancy<br># Specifies how much neighbor info should<br># be sent in TC messages<br># Possible values are:<br># 0 - only send MPR selectors<br># 1 - send MPR selectors and MPRs<br># 2 - send all neighbors<br>
#<br># defaults to 0<br><br>TcRedundancy 2<br><br><br>#<br># MPR coverage<br># Specifies how many MPRs a node should<br># try select to reach every 2 hop neighbor<br>#<br># Can be set to any integer >0<br>#<br># defaults to 1<br>
<br>MprCoverage 5<br><br><br># Olsrd plugins to load<br># This must be the absolute path to the file<br># or the loader will use the following scheme:<br># - Try the paths in the LD_LIBRARY_PATH <br># environment variable.<br>
# - The list of libraries cached in /etc/ld.so.cache<br># - /lib, followed by /usr/lib<br><br># Configuration examples for plugins:<br># see /usr/share/doc/olsrd-plugins/ for some for documentation<br><br>LoadPlugin "olsrd_httpinfo.so.0.1"<br>
{<br> # defaults to 1978<br> PlParam "Port" "1978"<br> # if you dont set these, the default is to listen only on the loopback device<br> PlParam "Host" "127.0.0.1"<br>
#PlParam "Net" "127.0.0.0 255.0.0.0"<br> #PlParam "Net" "0.0.0.0 0.0.0.0"<br>}<br><br># useful if your machine has an uplink<br>#LoadPlugin "olsrd_dyn_gw.so.0.4"<br>
#{<br> # Here parameters are set to be sent to the<br> # plugin. Theese are on the form "key" "value".<br> # Parameters ofcause, differs from plugin to plugin.<br> # Consult the documentation of your plugin for details.<br>
<br> # Example: dyn_gw params<br><br> # how often to check for Internet connectivity<br> # defaults to 5 secs<br># PlParam "Interval" "40"<br> <br> # if one or more IPv4 addresses are given, do a ping on these in<br>
# descending order to validate that there is not only an entry in<br> # routing table, but also a real internet connection. If any of<br> # these addresses could be pinged successfully, the test was<br> # succesful, i.e. if the ping on the 1st address was successful,the<br>
# 2nd won't be pinged<br># PlParam "Ping" "141.1.1.1"<br># PlParam "Ping" "194.25.2.129"<br>#}<br><br>#LoadPlugin "olsrd_nameservice.so.0.2"<br>
#{<br> #PlParam "name" "xxx"<br> #PlParam "a.b.c.d" "xxx-eth"<br> #PlParam "a.b.c.e" "xxx-bbb"<br> #PlParam "a.b.c.f" "xxx-olsr"<br>
#PlParam "suffix" ".olsr"<br>#}<br><br>LoadPlugin "olsrd_dot_draw.so.0.3"<br>{<br> # accept connection from IP:<br> # default 127.0.0.1 (localhost) <br> PlParam "accept" "127.0.0.1"<br>
PlParam "port" "2004"<br>}<br>LoadPlugin "olsrd_txtinfo.so.0.1"<br>{<br> PlParam "accept" "127.0.0.1"<br>}<br><br>Regards<br>Vichao Saenghiranwathana<br><div class="hm">
<br><br></div></span><div class="hm"> <br><hr>Hotmail: Free, trusted and rich email service. <a href="http://clk.atdmt.com/GBL/go/196390708/direct/01/" target="_blank">Get it now.</a></div></div>
<br>--<br>
Olsr-users mailing list<br>
<a href="mailto:Olsr-users@lists.olsr.org">Olsr-users@lists.olsr.org</a><br>
<a href="http://lists.olsr.org/mailman/listinfo/olsr-users" target="_blank">http://lists.olsr.org/mailman/listinfo/olsr-users</a><br></blockquote></div><br>