Juan Jose Huereca Rodriguez | 12 Jul 2010 16:48
Picon
Favicon

Help Olsrd On ARM Cross Compiler

Hi im trying to use olsr on a ebedded computer (AMR) so i tried to 
compile with a cross compiler and the result was a lot of errors,
  so a made changes to a file (Makefile.linux) and i reduce the erros 
but some errors still remains, and i cant solve this situatios
does anyone know how to solve this errors? any idea? (atatched some 
pictures):
1 Changes maded in Makefile.linux
2 The las errors that display the cross compiler
Note: The AMR computer is based on a red hat distro and the compilation 
was on a fedora 12 distro
Thanks in advance.
--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
Henning Rogge | 12 Jul 2010 16:59

Re: Help Olsrd On ARM Cross Compiler

Am Montag 12 Juli 2010, 16:48:59 schrieb Juan Jose Huereca Rodriguez:
> Hi im trying to use olsr on a ebedded computer (AMR) so i tried to
> compile with a cross compiler and the result was a lot of errors,
>   so a made changes to a file (Makefile.linux) and i reduce the erros
> but some errors still remains, and i cant solve this situatios
> does anyone know how to solve this errors? any idea? (atatched some
> pictures):
> 1 Changes maded in Makefile.linux
> 2 The las errors that display the cross compiler
> Note: The AMR computer is based on a red hat distro and the compilation
> was on a fedora 12 distro
Try to call it without your makefile change, but with the line

CC=arm-linux-gcc make clean_all build_all

I use a similar line on my linux machine to do BSD and Win32 crosscompilation.

Henning Rogge

-- 
1) You can't win.
2) You can't break even.
3) You can't leave the game.
— The Laws of Thermodynamics, summarized
--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
(Continue reading)

Markus Kittenberger | 12 Jul 2010 20:01
Picon
Picon

Re: Help Olsrd On ARM Cross Compiler

which type of arm processor?

the current stable branch should imho compile well for arm926T (as im using it on this plattform)

Markus

On Mon, Jul 12, 2010 at 4:48 PM, Juan Jose Huereca Rodriguez <hrwereka <at> hotmail.com> wrote:
Hi im trying to use olsr on a ebedded computer (AMR) so i tried to compile with a cross compiler and the result was a lot of errors,
 so a made changes to a file (Makefile.linux) and i reduce the erros but some errors still remains, and i cant solve this situatios
does anyone know how to solve this errors? any idea? (atatched some pictures):
1 Changes maded in Makefile.linux
2 The las errors that display the cross compiler
Note: The AMR computer is based on a red hat distro and the compilation was on a fedora 12 distro
Thanks in advance.

--
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users

--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
Adam Wozniak | 12 Jul 2010 20:12

Re: Help Olsrd On ARM Cross Compiler

All those errors are about command line warning options unrecognized by 
the compiler.

You should do three things:

Update your version of the compiler.
Learn more about reading the error messages the compiler gives you.
Learn more about "make".

--Adam

On 07/12/2010 07:48 AM, Juan Jose Huereca Rodriguez wrote:
> Hi im trying to use olsr on a ebedded computer (AMR) so i tried to 
> compile with a cross compiler and the result was a lot of errors,
>  so a made changes to a file (Makefile.linux) and i reduce the erros 
> but some errors still remains, and i cant solve this situatios
> does anyone know how to solve this errors? any idea? (atatched some 
> pictures):
> 1 Changes maded in Makefile.linux
> 2 The las errors that display the cross compiler
> Note: The AMR computer is based on a red hat distro and the 
> compilation was on a fedora 12 distro
> Thanks in advance.

--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users

Magesh mannar | 13 Jul 2010 15:29
Picon
Favicon

olsr dot draw plugin: IPv6 address

Dear all

I understand that dot draw plugin is used to visualise the mesh network topology. Does the dot draw plugin
support IPv6 address 

From the screen shots, I can see the IPv4 address of the nodes displayed. Is it possible to display IPv6
address instead of IPv4 address.

Best regards

Magesh

--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users

Arsham Farshad | 13 Jul 2010 20:38
Picon
Favicon

a problem in traffic forwarding

Hi all,
I am running the olsrd in the multi-interface mesh network, olsrd works fine and routing tables contains the route to all node in the network, the problwm is in passing traffic, when I have a multiple hop traffic, traffic forward to the previous node of destination node but not delivered to the destination node. I checked that there is connection between the destination and previous node in the path.
any suggestion?
Many thanks


--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
Vikram KAUL | 20 Jul 2010 21:33
Favicon

Android: reloc_library[1300] error for olsrd_bmf.so.1.7.0


Folks

  I seem to get a problem with the stable relese from today (20th 
July) with the plugin load for BMF on Android G1 (version 2.1).

  I am loading only the bmf plugin, and have placed the .so* file in 
/system/lib. The file is found, but olsrd errors out on not being able to 
locate 'set_plugin_int'. See error below.

  The config file is pretty simple. I have only removed the txtinfo plugin 
and added bmf to the default.lq config

LoadPlugin "olsrd_bmf.so.1.7.0"
{
}

  Any idea why this is happening ? It works fine on standard linux.

  Any pointers will be greatly appreciated

regards..
Vikram

Here is the full error

# ./olsrd -d 9
./olsrd -d 9

  *** olsr.org - pre-0.6.1 ***
  Build date: 2010-07-20 13:50:31 on vkaul-laptop
  http://www.olsr.org

Parsing file: "/data/local/etc/olsrd.conf"
Link quality fish eye 0
Plugin: olsrd_bmf.so.1.7.0

Interface Defaultssetting ifs_in_curr_cfg = 0
         IPv4 broadcast/multicast : AUTO (d)
         Mode           : mesh (d)
         IPv6 multicast           : ff02::6d
         HELLO emission/validity  : 2.00 (d)/20.00 (d)
         TC emission/validity     : 5.00 (d)/300.00 (d)
         MID emission/validity    : 5.00 (d)/300.00 (d)
         HNA emission/validity    : 5.00 (d)/300.00 (d)
         Autodetect changes       : yes
         IPv4 broadcast/multicast : AUTO
         Mode           : mesh
         IPv6 multicast           : ::
         HELLO emission/validity  : 0.00/0.00
         TC emission/validity     : 0.00/0.00
         MID emission/validity    : 0.00/0.00
         HNA emission/validity    : 0.00/0.00
         Autodetect changes       : no
  *** olsrd configuration ***
Debug Level      : 9
IpVersion        : 4
No interfaces    : ALLOWED
TOS              : 0x10
OlsrPort          : 0x2ba
RtTable          : 254
RtTableDefault   : 254
RtTableTunnel    : 254
Willingness      : 3
IPC connections  : 0
Pollrate         : 0.05
NIC ChangPollrate: 2.50
TC redundancy    : 2
MPR coverage     : 7
LQ level         : 2
LQ fish eye      : 0
LQ aging factor  : 0.050000
LQ algorithm name: default
NAT threshold    : 1.000000
Clear screen     : yes
Use niit         : yes
Smart Gateway    : no
SmGw. Allow NAT  : yes
Smart Gw. Uplink : both
SmGw. Uplink NAT : yes
Smart Gw. speed  : 128 kbit/s up, 1024 kbit/s down
# Smart Gw. prefix : ::/0
  InterfaceDefaults:
         IPv4 broadcast/multicast : AUTO
         Mode           : mesh
         IPv6 multicast           : ff02::6d
         HELLO emission/validity  : 2.00/20.00
         TC emission/validity     : 5.00/300.00
         MID emission/validity    : 5.00/300.00
         HNA emission/validity    : 5.00/300.00
         Autodetect changes       : yes
  dev: "tiwlan0"
         IPv4 broadcast/multicast : AUTO (d)
         Mode           : mesh (d)
         IPv6 multicast           : ff02::6d (d)
         HELLO emission/validity  : 2.00 (d)/20.00 (d)
         TC emission/validity     : 5.00 (d)/300.00 (d)
         MID emission/validity    : 5.00 (d)/300.00 (d)
         HNA emission/validity    : 5.00 (d)/300.00 (d)
         Autodetect changes       : yes (d)
Plugins:
         Name: "olsrd_bmf.so.1.7.0"
Not using hysteresis
Adding OLSR socket entry 5
Initializing parser...
Parser: registering event for type 201
Register parse function: Added function for type 201
Parser: registering event for type 202
Register parse function: Added function for type 202
Parser: registering event for type 3
Register parse function: Added function for type 3
Parser: registering event for type 4
Register parse function: Added function for type 4
Added 0.0.0.0 to IP deny set
Added 127.0.0.1 to IP deny set

  ---- Interface configuration ----

Checking tiwlan0:
         Not a wireless interface
         Metric: 0
         MTU - IPhdr: 1472
         Index 7
         Address:192.168.0.128
         Netmask:255.255.255.0
         Broadcast address:192.168.0.255
Binding socket 11 to device tiwlan0
Binding socket 14 to device tiwlan0
Adding OLSR socket entry 11
Adding OLSR socket entry 14
New main address: 192.168.0.128
TIMER: jitter 25% rel_time 2000ms to 1683ms
TIMER: start Hello Generation timer 0x7cbb0 firing in 00:00:01.683, ctx 
0x7ca80
TIMER: jitter 25% rel_time 5000ms to 4580ms
TIMER: start TC Generation timer 0x7cbe0 firing in 00:00:04.580, ctx 
0x7ca80
TIMER: jitter 25% rel_time 5000ms to 4700ms
TIMER: start MID Generation timer 0x7cc10 firing in 00:00:04.700, ctx 
0x7ca80
TIMER: jitter 25% rel_time 5000ms to 4272ms
TIMER: start HNA Generation timer 0x7cc40 firing in 00:00:04.272, ctx 
0x7ca80
TIMER: jitter 5% rel_time 2000ms to 1978ms
TIMER: start Interface Polling timer 0x7cc70 firing in 00:00:01.978, ctx 
0x0
TIMER: start Default Timer Cookie timer 0x7cca0 firing in 00:00:00.600, 
ctx 0x0
Using 'etx_ff' algorithm for lq calculation.
Parser: registering packetparser
Registered packetparser  function
TIMER: start Default Timer Cookie timer 0x7cda0 firing in 00:00:01.000, 
ctx 0x0
TIMER: jitter 25% rel_time 15000ms to 14933ms
TIMER: start Default Timer Cookie timer 0x7cdd0 firing in 00:00:14.933, 
ctx 0x0
RIB: init routing tree
TC: init topo
TC: add entry 192.168.0.128
RIB: add prefix 192.168.0.128/32 from 192.168.0.128
MPRS: Init
MID: init
TIMER: start Default Timer Cookie timer 0x7d140 firing in 01:00:00.000, 
ctx 0x0
---------- LOADING LIBRARY olsrd_bmf.so.1.7.0 ----------
DL loading failed: "Cannot load library: reloc_library[1300]:  1544 cannot locate 'set_plugin_int'..."!
-- PLUGIN LOADING FAILED! --

--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users

Vikram KAUL | 20 Jul 2010 21:51
Favicon

Re: Android: reloc_library[1300] error for olsrd_bmf.so.1.7.0


>
> I seem to get a problem with the stable relese from today (20th July) with 
> the plugin load for BMF on Android G1 (version 2.1).

Sorry, I meant to say the most "stable" release version from 16th July.

committer	Sven-Ola Tuecke <sven-ola <at> gmx.de>
          	 Fri, 16 Jul 2010 18:29:29 +0000 (20:29 +0200)

with the commit reference starting with 31ec9d6....

Vikram

>
> I am loading only the bmf plugin, and have placed the .so* file in 
> /system/lib. The file is found, but olsrd errors out on not being able to 
> locate 'set_plugin_int'. See error below.
>
> The config file is pretty simple. I have only removed the txtinfo plugin and 
> added bmf to the default.lq config
>
> LoadPlugin "olsrd_bmf.so.1.7.0"
> {
> }
>
> Any idea why this is happening ? It works fine on standard linux.
>
> Any pointers will be greatly appreciated
>
> regards..
> Vikram
>
> Here is the full error
>
> # ./olsrd -d 9
> ./olsrd -d 9
>
> *** olsr.org - pre-0.6.1 ***
> Build date: 2010-07-20 13:50:31 on vkaul-laptop
> http://www.olsr.org
>
> Parsing file: "/data/local/etc/olsrd.conf"
> Link quality fish eye 0
> Plugin: olsrd_bmf.so.1.7.0
>
> Interface Defaultssetting ifs_in_curr_cfg = 0
>        IPv4 broadcast/multicast : AUTO (d)
>        Mode           : mesh (d)
>        IPv6 multicast           : ff02::6d
>        HELLO emission/validity  : 2.00 (d)/20.00 (d)
>        TC emission/validity     : 5.00 (d)/300.00 (d)
>        MID emission/validity    : 5.00 (d)/300.00 (d)
>        HNA emission/validity    : 5.00 (d)/300.00 (d)
>        Autodetect changes       : yes
>        IPv4 broadcast/multicast : AUTO
>        Mode           : mesh
>        IPv6 multicast           : ::
>        HELLO emission/validity  : 0.00/0.00
>        TC emission/validity     : 0.00/0.00
>        MID emission/validity    : 0.00/0.00
>        HNA emission/validity    : 0.00/0.00
>        Autodetect changes       : no
> *** olsrd configuration ***
> Debug Level      : 9
> IpVersion        : 4
> No interfaces    : ALLOWED
> TOS              : 0x10
> OlsrPort          : 0x2ba
> RtTable          : 254
> RtTableDefault   : 254
> RtTableTunnel    : 254
> Willingness      : 3
> IPC connections  : 0
> Pollrate         : 0.05
> NIC ChangPollrate: 2.50
> TC redundancy    : 2
> MPR coverage     : 7
> LQ level         : 2
> LQ fish eye      : 0
> LQ aging factor  : 0.050000
> LQ algorithm name: default
> NAT threshold    : 1.000000
> Clear screen     : yes
> Use niit         : yes
> Smart Gateway    : no
> SmGw. Allow NAT  : yes
> Smart Gw. Uplink : both
> SmGw. Uplink NAT : yes
> Smart Gw. speed  : 128 kbit/s up, 1024 kbit/s down
> # Smart Gw. prefix : ::/0
> InterfaceDefaults:
>        IPv4 broadcast/multicast : AUTO
>        Mode           : mesh
>        IPv6 multicast           : ff02::6d
>        HELLO emission/validity  : 2.00/20.00
>        TC emission/validity     : 5.00/300.00
>        MID emission/validity    : 5.00/300.00
>        HNA emission/validity    : 5.00/300.00
>        Autodetect changes       : yes
> dev: "tiwlan0"
>        IPv4 broadcast/multicast : AUTO (d)
>        Mode           : mesh (d)
>        IPv6 multicast           : ff02::6d (d)
>        HELLO emission/validity  : 2.00 (d)/20.00 (d)
>        TC emission/validity     : 5.00 (d)/300.00 (d)
>        MID emission/validity    : 5.00 (d)/300.00 (d)
>        HNA emission/validity    : 5.00 (d)/300.00 (d)
>        Autodetect changes       : yes (d)
> Plugins:
>        Name: "olsrd_bmf.so.1.7.0"
> Not using hysteresis
> Adding OLSR socket entry 5
> Initializing parser...
> Parser: registering event for type 201
> Register parse function: Added function for type 201
> Parser: registering event for type 202
> Register parse function: Added function for type 202
> Parser: registering event for type 3
> Register parse function: Added function for type 3
> Parser: registering event for type 4
> Register parse function: Added function for type 4
> Added 0.0.0.0 to IP deny set
> Added 127.0.0.1 to IP deny set
>
> ---- Interface configuration ----
>
> Checking tiwlan0:
>        Not a wireless interface
>        Metric: 0
>        MTU - IPhdr: 1472
>        Index 7
>        Address:192.168.0.128
>        Netmask:255.255.255.0
>        Broadcast address:192.168.0.255
> Binding socket 11 to device tiwlan0
> Binding socket 14 to device tiwlan0
> Adding OLSR socket entry 11
> Adding OLSR socket entry 14
> New main address: 192.168.0.128
> TIMER: jitter 25% rel_time 2000ms to 1683ms
> TIMER: start Hello Generation timer 0x7cbb0 firing in 00:00:01.683, ctx 
> 0x7ca80
> TIMER: jitter 25% rel_time 5000ms to 4580ms
> TIMER: start TC Generation timer 0x7cbe0 firing in 00:00:04.580, ctx 0x7ca80
> TIMER: jitter 25% rel_time 5000ms to 4700ms
> TIMER: start MID Generation timer 0x7cc10 firing in 00:00:04.700, ctx 0x7ca80
> TIMER: jitter 25% rel_time 5000ms to 4272ms
> TIMER: start HNA Generation timer 0x7cc40 firing in 00:00:04.272, ctx 0x7ca80
> TIMER: jitter 5% rel_time 2000ms to 1978ms
> TIMER: start Interface Polling timer 0x7cc70 firing in 00:00:01.978, ctx 0x0
> TIMER: start Default Timer Cookie timer 0x7cca0 firing in 00:00:00.600, ctx 
> 0x0
> Using 'etx_ff' algorithm for lq calculation.
> Parser: registering packetparser
> Registered packetparser  function
> TIMER: start Default Timer Cookie timer 0x7cda0 firing in 00:00:01.000, ctx 
> 0x0
> TIMER: jitter 25% rel_time 15000ms to 14933ms
> TIMER: start Default Timer Cookie timer 0x7cdd0 firing in 00:00:14.933, ctx 
> 0x0
> RIB: init routing tree
> TC: init topo
> TC: add entry 192.168.0.128
> RIB: add prefix 192.168.0.128/32 from 192.168.0.128
> MPRS: Init
> MID: init
> TIMER: start Default Timer Cookie timer 0x7d140 firing in 01:00:00.000, ctx 
> 0x0
> ---------- LOADING LIBRARY olsrd_bmf.so.1.7.0 ----------
> DL loading failed: "Cannot load library: reloc_library[1300]:  1544 cannot 
> locate 'set_plugin_int'..."!
> -- PLUGIN LOADING FAILED! --
>
>
>

--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users

Julie Workman | 23 Jul 2010 19:49
Picon

Getting OLSRD to "switch" faster

Hi.

I am using OLSRD 0.5.6-r5-r10.5 for a robotics application.  My problem is that when my robot rounds a corner I need to to switch much more quickly to a better node.  The result using OLSRD unmodified is that I lose communications for 2 minutes and my robot sits there before the new node is switched to and I can communicate again.

The odd thing is that when I have several nodes all in sight of each other, the bot switches quite nicely (~5 seconds) between the closest one at the time.  It is just when I round a corner (and completely lose communication with my current node) where I see the 2 minute switch over time.

I have messed around with the HelloInterval, the LinkQualityWinSize, and HelloValidityTime to where the switch over time is down to 30-45 seconds.  Better, but still not nearly quick enough.

I have several questions.  Can I tweak those parameters further to see better times?  How small can I make my HelloInterval?  Are there different parameters I should be changing?  Does OLSRD always work off of packet loss?  I need about a Mb of throughput for my application.  Are there ways to tweak OLSRD to use throughput instead?

Thank you for any help/suggestions.

-Julie

--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
Markus Kittenberger | 23 Jul 2010 20:24
Picon
Picon

Re: Getting OLSRD to "switch" faster

linkquality winsize is deprecated/unused since quite a while,.. changing it will have no effect

further you must change tc intervals aswell (e.g. to ~ 3x hello interval), and u must change this (and hello intervall) on all nodes, not only on your robot,..

further change the dijkstra intervall/limits also,.. 

this (as long as you are willing to accept the amount of olsrd traffic this will produce (if u use message intervalls > 1hz)) this should enable you to switch in less than 5 hello intervalls

regards Markus

p.s. olsrd uses metric plugins, if u want another metric write another metric-plugin (-;

On Fri, Jul 23, 2010 at 7:49 PM, Julie Workman <climber.julie <at> gmail.com> wrote:
Hi.

The odd thing is that when I have several nodes all in sight of each other, the bot switches quite nicely (~5 seconds) between the closest one at the time.  It is just when I round a corner (and completely lose communication with my current node) where I see the 2 minute switch over time.
omg *G please post your complete configfile,..  and oslr version,..

is there no point where the robot sees both nodes at a corner?

I have messed around with the HelloInterval, the LinkQualityWinSize, and HelloValidityTime to where the switch over time is down to 30-45 seconds.  Better, but still not nearly quick enough.

I have several questions.  Can I tweak those parameters further to see better times?  How small can I make my HelloInterval?  Are there different parameters I should be changing?  Does OLSRD always work off of packet loss?  I need about a Mb of throughput for my application.  Are there ways to tweak OLSRD to use throughput instead?

--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users

Gmane