Daniel Ruiz López | 2 Feb 11:44 2006
Picon

Problems loading a plugin in an AccessCube/MeshCube of 4G Systeme

Hi,

I've made a plugin based on the famous "powerinfo" plugin.

I compile it with the default Makefile (using gcc) and I put my plugin in the /usr/lib of my computer,  olsrd loads it correctly  after modifying the /etc/olsrd.conf.


The problem is when I want to run my plugin in one AccessCube/MeshCube of 4G Systeme (It runs over Nylon 0.8.).

I crosscompile the plugin with mipsel-linux-gcc and I put it in /usr/lib of my cube, but when I start olsrd it appears the following:

---------- Plugin loader ----------
Library: olsrd_dani.so.0.1
DL loading failed: "olsrd_dani.so.0.1: cannot open shared object file: No such file or directory"!
-- PLUGIN LOADING FAILED! --


I've tried to specify the full path of the plugin in the olsrd.conf, apart from inserting the path /usr/lib in the /etc/ld.so.conf but it does the same.
I'm running the version 0.4.9 of olsrd.

My Makefile starts as the following:

#############################################
# EXAMPLE MAKEFILE TO CREATE A OLSRD PLUGIN #
#############################################

#Alter this file to fit your needs

CC ?= ../mipsel-linux-gcc
STRIP ?= strip
PLUGINFLAGS =  -fPIC -DOLSR_PLUGIN -I/root/Desktop/olsrd-0.4.9/src

ifeq ($(OS), linux)
NAME ?= olsrd_dani.so.0.1
LIBDIR ?= $(INSTALL_PREFIX)/usr/lib
# -fPIC creates position independent code
LIBS ?= -lc -lm
CFLAGS ?= -Wall -g -O2 -Wmissing-prototypes -Wstrict-prototypes
LDFLAGS ?= -fPIC
INSTALL_LIB = install -D -m 755 $(NAME) $(LIBDIR)/$(NAME);\
        /sbin/ldconfig -n $(LIBDIR)
all:    plugin
install:install_olsrd
endif





Thanks in advance,


--
---------------------------------------
Dani

_______________________________________________
olsr-users mailing list
olsr-users <at> olsr.org
https://www.olsr.org/mailman/listinfo/olsr-users
Benjamin Henrion | 3 Feb 19:50 2006

patch to support negative weights in OSLR

Here is a stupid patch to support negative weights in OLSR:

http://www.ffii.org/~zoobab/bh.udev.org/filez/projects/olsr2chan/

I still need to test it with real machines, but with UML-wifi it seems
to work.

--
Benjamin Henrion <bh <at> udev.org>
http://bh.udev.org
<<<                   European Community Patent will bring            >>>
<<<                     Software patents by the backdoor              >>>
<<<                      http://wiki.ffii.org/ComPatEn                >>>
Dan Flett | 4 Feb 03:21 2006
Picon

OLSR Deb packages

Hi Guys,

Could someone please update the Debian packages in the
http://www.skyhub.de/debian/ repository to version 0.4.10?  

Thanks.

Dan
Frank Becker | 4 Feb 10:59 2006
Picon

Re: OLSR Deb packages

Dan Flett [2006-02-04, 03:22 +0100]:
Hi,

> Could someone please update the Debian packages in the
> http://www.skyhub.de/debian/ repository to version 0.4.10?
I promise an update next week.

Bye,

Frank

--

-- 
Frank Becker <fb <at> alien8.de>
GnuPG: 0xADC29ECD | F01B 5E9C 1D09 981B 5B40 50D3 C80F 7459 ADC2 9ECD
SILC-Net: a8 | Home: http://www.alien8.de | <<</>> http://www.c3d2.de
If privacy is outlawed, only outlaws will have privacy. P. Zimmermann
_______________________________________________
olsr-users mailing list
olsr-users <at> olsr.org
https://www.olsr.org/mailman/listinfo/olsr-users
Marc Quinton | 4 Feb 14:44 2006
Picon

OLSR network stability

where am I wrong ?

I'm using OLSR with a rather large network in a small town. Network density is
good to establish connexions between multiples routes.

Network is not stable at all. Route calculation a made every 5 seconds
(HelloInterval). OLSR is working with LinkQuality not hysteresis.

This is not a "mobile" netwrok but a static one. So what can I do ? My network
is made with Linksys Wrt54g, Openwrt, OLSR 0.49. I need to pay attention
to CPU load.

here is my parameters for OLSR :

Main address: 169.254.0.99      IP version: 4             Debug level: 0
Pollrate: 0.05                             TC redundancy: 0     MPR coverage: 1
TOS: 0x0010                              Willingness: 3
Hysteresis: Disabled                  Hyst scaling: 0.50     Hyst
lower/upper: 0.30/0.80
LQ extention: Enabled                LQ level: 2                LQ winsize: 50

below my config file.

#
# olsr.org OLSR daemon config file
#

...

# 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            4

# Wether to use hysteresis or not
# Hysteresis adds more robustness to the
# link sensing but delays neighbor registration.
# Used by default. 'yes' or 'no'

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      50

# Polling rate in seconds(float).
# Default value 0.05 sec

Pollrate        0.05

# 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    0

#
# 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     1

Interface "eth1" "eth2"
{

   # 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    5.0

   # HELLO validity time
   HelloValidityTime   20.0

   # TC interval in seconds(float)
   TcInterval        15.0

   # TC validity time
   TcValidityTime      60.0

   # MID interval in seconds(float)
   MidInterval 15.0

   # MID validity time
   MidValidityTime     60.0

   # HNA interval in seconds(float)
   HnaInterval 15.0

   # HNA validity time
   HnaValidityTime     60.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

}
Mathias Mahnke | 4 Feb 15:35 2006
Picon

Re: OLSR network stability

Marc Quinton wrote:
> where am I wrong ?
> 
> I'm using OLSR with a rather large network in a small town. Network density is
> good to establish connexions between multiples routes.
> 
> Network is not stable at all. 

What does it mean - "not stable at all". Route changes to ofter, 
instability of the daemon, or ...

Try upgrading to olsrd 0.4.10 at first, there are couple of bugs closed 
and a new feature (fisheye) added, which could help in large networks.

Greetings
Mathias (our net is about 140 nodes, a few mobile, most static, wifi and 
ethernet links, openwrt, olsrd 0.4.9 + 0.4.10 + some nodes allready 
under fisheye)
Sven Wagner | 4 Feb 18:30 2006

Re: OLSR network stability

Marc Quinton wrote:
> where am I wrong ?

I don't know, every (physical)networksetup is different, and that is the 
reason that it can't give " the one and only working olsr.conf"

in your network you are working with "TC redundancy: 0" we are working 
with  "TC redundancy: 2"
everybody gets all information, but we also use the fish (0.4.10)

most of the nodes in berlin are static, that is the reasen why we try a 
very slow config
the pollrate is set to 0.1 normal is 0.05, ( some nodes working with the 
faster pollrate) and the LinkQualityWinSize is 100 in our conf , thats 
good for static links, there are not changing...but it makes it also for 
notebook user slower to find the right gw, it is possibble,
that you have to wait up to 5 min.
I don't know if the fisheye is the right way, we can't say it works 
better or not, but it works  ;-)
we have more problems with bat HF connections an people who don't update 
there WRT ... it is "buttom up network" not a "top down" one ;-)

btw
in march, we setup the WirelessCommunityWeekend at c-base/berlin for 
people who have already a running (olsr) community network.

http://www.okfn.org/wsfii/wiki/WirelessCommunityWeekend
more infos asap

greetings
	cven

######berlinbackbone static node conf######
#
# olsr.org OLSR daemon config file
#
# Lines starting with a # are discarded
#
# This file was shipped with olsrd 0.X.X
#

# 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

# Fisheye mechanism for TC messages 0=off, 1=on

LinkQualityFishEye 1

# 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     6

# 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

# Example plugin entry with parameters:

#LoadPlugin "olsrd_dyn_gw.so.0.3"
#{
     # 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_httpinfo.so.0.1"
{
         PlParam "Port" "8080"
         PlParam "Net" "0.0.0.0 0.0.0.0"
}

LoadPlugin "olsrd_dyn_gw_plain.so.0.4"
{
}

LoadPlugin "olsrd_nameservice.so.0.2"
{
         PlParam "name" "hdl-1"
         PlParam "104.0.0.5" "hdl-1-eth"
         PlParam "104.0.0.10" "hdl-1-nd"
         PlParam "104.0.3.1" "hdl-1-bbb"
         PlParam "suffix" ".olsr"
}

#LoadPlugin "olsrd_dot_draw.so.0.3"
#{
         # accept connection from IP:
         # default 127.0.0.1 (localhost)
         #PlParam     "accept" "192.168.0.5"
#}

# 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):

Interface "eth0" "wlan0" "wlan1"
{

     # 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               5.0

     # HELLO validity time
     HelloValidityTime           90.0

     # TC interval in seconds(float)
     TcInterval                  2.0

     # TC validity time
     TcValidityTime              250.0

     # MID interval in seconds(float)
     MidInterval                 15.0

     # MID validity time
     MidValidityTime             90.0

     # HNA interval in seconds(float)
     HnaInterval                 15.0

     # HNA validity time
     HnaValidityTime             90.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         104.0.3.8       0.1
     #LinkQualityMult         104.0.3.13      0.1
     #LinkQualityMult         104.0.3.81      0.1
     #LinkQualityMult         104.0.3.2       0.1
     #LinkQualityMult         104.0.3.48      0.1
     LinkQualityMult         104.66.25.2     0.1

     # This multiplier applies to all other nodes
     # LinkQualityMult default 0.8

}
Marc Quinton | 5 Feb 18:07 2006
Picon

OLSR network stability (reply)

> I don't know, every (physical)networksetup is different, and that is the
> reason that it can't give " the one and only working olsr.conf"
>
> in your network you are working with "TC redundancy: 0" we are working
> with  "TC redundancy: 2"
> everybody gets all information, but we also use the fish (0.4.10)
>
> most of the nodes in berlin are static, that is the reasen why we try a
> very slow config
> the pollrate is set to 0.1 normal is 0.05, ( some nodes working with the
> faster pollrate) and the LinkQualityWinSize is 100 in our conf , thats
> good for static links, there are not changing...but it makes it also for
> notebook user slower to find the right gw, it is possibble,
> that you have to wait up to 5 min.
> I don't know if the fisheye is the right way, we can't say it works
> better or not, but it works  ;-)
> we have more problems with bat HF connections an people who don't update
> there WRT ... it is "buttom up network" not a "top down" one ;-)

thank you Sven for your good advices, now our network works very-very fine.
- I still use olsr 0.49,
- but I have changed some of your configation options, mainly
TcRedundancy, MprCoverage, TcValidityTime
- and now it works fine. No thing more to do.

PS: when I post a message to this list, I don't receive my messages.
So this is why I reply in  new thread. And now my registred adresse is
in gmail.
Bernd Petrovitsch | 6 Feb 11:41 2006
Picon

olsrd with 2 networks

How can I use the olsrd with two distinct IPv4 networks (e.g.
1.2.3.0/24 and 5.6.7.0/24)?
Is it enough to set "Ip4Broadcast" to "255.255.255.255"?

	Bernd
--

-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services
Andreas Tønnesen | 6 Feb 19:19 2006

Re: olsrd with 2 networks


I take it you are running on one interface? Using 255.255.255.255
for broadcast should be sufficient in that case.

- andreas

Bernd Petrovitsch wrote:

>How can I use the olsrd with two distinct IPv4 networks (e.g.
>1.2.3.0/24 and 5.6.7.0/24)?
>Is it enough to set "Ip4Broadcast" to "255.255.255.255"?
>
>	Bernd
>  
>

Gmane