OpenWrt Forum Archive

Topic: OLSR: Link Quality Level

The content of this topic has been archived on 22 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi all,

I'm doing some performance test on my small (4 nodes) mesh networking using OLSR.
My mesh network is made up of four Pronghorn Metro boards with Kamikaze 7.09 and olsrd 0.5.3.

Everything is working when when I set (in olsrd.conf of every card) LinkQualityLevel to 0 (i.e. hysteresis will be used) or to 1 (link quality is used only when calculating MPRs).

Something very strange happens when using LinkQualityLevel 2 (routes will also be calculated based on distributed link quality information): I can get working at the same time only two boards. On the other two boards the olsr daemons crash with a segmentation fault. If I try to restart olsrd the daemon crashs again after few seconds. I wasn't able to get any usefull info from strace. 

I'm not using any plug-in apart from httpinfo.

Any suggestion please?

bump...

Anyone managed to setup a mesh network (with more than two nodes) with olsrd 0.5.3 using "LinkQualityLevel 2"?

Thank you,

Francesco

Quick update to this...
(olsrd 0.5.3 - Kamikaze 7.09 on Pronghorn metro board)

Scenario 1.a (4 mesh nodes: N1, N2, N3, N4)

N1 LinkQuality 1
N2 LinkQuality 1
N3 LinkQuality 1
N4 LinkQuality 1

Everything is ok

Scenario 1.b

N1 LinkQuality 2
N2 LinkQuality 2
N3 LinkQuality 2
N4 LinkQuality 2

olsrd crashs on N3 and on N4

Scenario 1.c

N1 LinkQuality 2
N2 LinkQuality 2
N3 LinkQuality 1
N4 LinkQuality 1

Everything seems to be ok...


It seems you can't get more than 2 nodes with LinkQuality 2 :-(

Let's hope 0.5.4 will fix this issue

Cheers,

Francesco

(Last edited by Francesco on 17 Nov 2007, 13:02)

Hi WIll you able to do a ping test to check the speed?
I have a test comparing a ad-hoc mode and ap/sta mode. ad-hoc mode is much slower than ap/sta.

Thanks



Francesco wrote:

Hi all,

I'm doing some performance test on my small (4 nodes) mesh networking using OLSR.
My mesh network is made up of four Pronghorn Metro boards with Kamikaze 7.09 and olsrd 0.5.3.

Everything is working when when I set (in olsrd.conf of every card) LinkQualityLevel to 0 (i.e. hysteresis will be used) or to 1 (link quality is used only when calculating MPRs).

Something very strange happens when using LinkQualityLevel 2 (routes will also be calculated based on distributed link quality information): I can get working at the same time only two boards. On the other two boards the olsr daemons crash with a segmentation fault. If I try to restart olsrd the daemon crashs again after few seconds. I wasn't able to get any usefull info from strace. 

I'm not using any plug-in apart from httpinfo.

Any suggestion please?

I fixed this issue by updating to olsrd 0.5.4

Let me know if you are interested in olsrd 0.5.4 packages (for ixp4xx).


Cheers,

Francesco

Does olsrd 0.5.4 work with Kamikaze 7.07? I just don't know how to upgrade current Kamiklaze 7.07 to kamikaze 7.09.

Would like to have a try on olsrd 0.5.4.

Please help me.

Thanks.


Francesco wrote:

I fixed this issue by updating to olsrd 0.5.4

Let me know if you are interested in olsrd 0.5.4 packages (for ixp4xx).


Cheers,

Francesco

Hi.
I have some basic quetions.
1) When I install olsrd in the board, does it will be there after a reboot?
2) If not, I have to re-compile the kernel with olsrd modules?
3) To do that, i.e. re-compiling the kernel with olsrd support, there is some pointer?
Thank you

@phuang

Olsrd 0.5.5 was released, the compiled packages for ipx4xx are available here

@giusepped

To install olsrd, just copy the packages to your board and then use the ipkg tool to install whatever you need

To compile kernel with olsrd (buit-in or package):

make menuconfig

and then Network --> olsrd


Francesco

(Last edited by Francesco on 19 Feb 2008, 09:00)

I did it, but when I reboot all is gone away.
Anyway, I think my problem is in the bootloader script.
At the first i put the following intructions

fis unlock -f 0x50060000 -l 0xF80000
load -r -v -b 0x01600000 -m disk hda1:pronghornmetro-zImage
fis create kernel
load -r -v -b 0x800000 -m disk hda1:squashfs.img
fis create -b 0x800000 rootfs
go -n 0x01600000

After a reboot, the RedBoot load this script and executes the instructions. doesn't it?
G

The discussion might have continued from here.