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