Henning Rogge | 1 Apr 09:01 2014
Picon

OLSRd2 v0.4.0 release

Hi,

after a lot of large and small changes I released version 0.4.0 of
OLSRd2, the OONF-API (and DLEP).

The reason for the new version is a major bugfix in the RFC5444
address compression that took two attempts (each of them a week of
work) to track down. I would advise everyone to upgrade to v0.4.0.

There is still an issue with the nl80211_listener plugin on MIPS
architecture on OpenWRT (e.g. Ubiquiti Bullet). The plugin have worked
on this architecture in the past and it works on x86 OpenWRT, so I am
still searching for the specific problem. I will inform you when this
problem is resolved.

As always you get the new version through the git repositories on
http://olsr.org/git

Henning Rogge

--

-- 
Olsr-dev mailing list
Olsr-dev <at> lists.olsr.org
https://lists.olsr.org/mailman/listinfo/olsr-dev

Ferry Huberts | 24 Mar 17:10 2014

Re: [Olsr-users] Route on repeater nodes sometimes break when gateway node reboots

forgot the include the list...

As a quick reply,

You're on an old version of olsrd. Can you please try to reproduce with 
the latest from master?

Second, on your version it takes at least a minute (with default config) 
before a new gateway is chosen.

The extra features for sgw in master also include some under-the-hood 
bugfixes that I discovered during engineering of the extra features.

If the problem still persists on master, then we really need to look at it.

I'll read through your entire message later this week.

On 24/03/14 16:44, Ben West wrote:
> Hi Ferry,
>
> Thanks for responding.  I am including at the bottom the
> network/firewall/olsrd configs for the nodes in question.  Note that the
> nodes each broadcast 3 wireless virtual interfaces, an adhoc I/F and two
> APs (public and private).
>
> The symptom observed is that the repeater node described below, after
> rebooting the gateway node, becomes unable to ping anything beyond the
> gateway node's WAN IP.  Restarting olsrd on the repeater node usually
> resolves the problem, although in this instance I'm writing about, I had
> to restart olsrd on both nodes.  Also, rebooting the gateway node
(Continue reading)

Syed Salman Haider Rizvi | 19 Mar 11:22 2014
Picon

Which metric is currently running on OLSRd2

Hi All ,

      Just let u guys know the scenario . I m running 14 hops testbed for performance evaluation of (ETT vs ETX vs HC) on  olsrd2 . Last time i tried both ett and etx on my testbed but my route was not changing and even getting the same throughput on both ETT and ETX . So is there anyways to see which metric is currently on and for HC i will surely use olsrd1 but i think there will be a lot difference in the throughput maybe the size of olsrd1 and olsrd2 packets are different ?

Salman
--

-- 
Olsr-dev mailing list
Olsr-dev <at> lists.olsr.org
https://lists.olsr.org/mailman/listinfo/olsr-dev
Saverio Proto | 21 Feb 23:12 2014
Picon

possible bug on olsrd IPv6 inserting route

Hello,

a Ninux user see this stuff in his log file everysecond:

Feb 21 19:23:58 Edge-Laiatico olsrd[1403]: . error: add route to
2001:760:://32 via 2001:4c00:893b:1:135::10 dev eth2.1382 onlink
(Resource temporarily unavailable 11)
Feb 21 19:23:58 Edge-Laiatico olsrd[1403]: . auto-deleting similar
routes to resolve 'File exists' (17) while adding route!
Feb 21 19:23:58 Edge-Laiatico olsrd[1403]: . error: del route to
2001:760:://32 via 2001:760:: dev void onlink (Resource temporarily
unavailable 11)
Feb 21 19:23:58 Edge-Laiatico olsrd[1403]: . failed (3)
Feb 21 19:23:58 Edge-Laiatico olsrd[1403]: Add route 2001:760::/32
from 2001:4c00:893b:a:e5ac:1914:e38:8e2b via 2001:4c00:893b:1:135::10,
cost 12.683, metric 12, v 664812: Resource temporarily unavailable

the hardware is the Ubiquiti Edgerouter. Here is the exact version of olsrd.

admin <at> Edge-Laiatico:~$ sudo /config/olsrd/olsrd.mips64r2

 *** olsr.org - pre-0.6.7-git_c2c420b-hash_ca10d83ddde9806265724e55c9f067f5 ***
 Build date: 2013-08-02 18:02:08 on HAL-Linux
 http://www.olsr.org

however the route is correctly installed:

admin <at> Edge-Laiatico:~$ ip -f inet6 r s | grep 760
2001:760::/32 via 2001:4c00:893b:1:135::10 dev eth2.1382  metric 2
mtu 1500 advmss 1440 hoplimit 0
admin <at> Edge-Laiatico:~$

configuration is attached.

any idea how to debug further ?
now we are going to try to reproduce the bug with the current
release-0.6.6 branch

Saverio
Attachment (olsrd6.conf): application/octet-stream, 356 bytes
--

-- 
Olsr-dev mailing list
Olsr-dev <at> lists.olsr.org
https://lists.olsr.org/mailman/listinfo/olsr-dev
Karoly Szabo | 21 Jan 20:16 2014
Picon

OLSRv1 telnet plugin on Android

Hi all,
I'm having some troubles with telnet plugin when I try to use some foreign commands.
If I compile my commands (I put them in main.c to make it easier) and run on Linux everything is working fine, my foreign commands are listed when I type help in telnet and they do their job.

When I compile for Android all the default commands are running but I can't make work the foreign commands, and neither see them with the help command in telnet.
(I double checked on the configuration file and they should be active, also because the configuration is imported from the same machine where they are working)

I found only this difference just for Linux in telnet library
#ifdef __linux__
#include <fcntl.h>
#endif /* __linux__ */

And I tried to workaround that just by adding:
#ifdef __ANDROID__
#include <fcntl.h>
#endif /*__ANDROID__ */

But the result seems to be unchanged at all.

Does anyone have an idea how to solve it?
Thanks for your help.
Karoly
--

-- 
Olsr-dev mailing list
Olsr-dev <at> lists.olsr.org
https://lists.olsr.org/mailman/listinfo/olsr-dev
Karoly Szabo | 7 Jan 17:05 2014
Picon

OLSRv2 cross compilation or Android

Hi all,
I'm trying to compile Olsrv2 for Android using
Andorid-ndk-r8e
and following the example found in cmake/cross/android_on_linux.cmake
The make command usually stop at 1%
Only after adding those paths I was able to reach (just) 4%

export PATH=$PATH:/locale/ANDROID/bin:~/adt-bundle-linux-x86/sdk/platform-tools/:/locale/ANDROID/android-ndk-r8e:/locale/ANDROID/android-ndk-r8e/toolchains/arm-linux-androideabi-4.7/prebuilt/linux-x86_64/bin:/locale/ANDROID/android-ndk-r8e/platforms/android-14/arch-arm/usr/include:/locale/ANDROID/android-ndk-r8e/platforms/android-14/arch-arm/usr/lib:

export C_INCLUDE_PATH=C_INCLUDE_PATH:/locale/ANDROID/android-ndk-r8e/platforms/android-14/arch-arm/usr/include:/locale/ANDROID/android-ndk-r8e/platforms/android-14/arch-arm/usr/lib:

Does anyone had a similar problem?
Here is the result of the last make (usually was .o files instead of .obj, but with same results):

Scanning dependencies of target oonf_common
[  1%] Building C object src-api/common/CMakeFiles/oonf_common.dir/autobuf.c.obj
[  1%] Building C object src-api/common/CMakeFiles/oonf_common.dir/avl_comp.c.obj
[  2%] Building C object src-api/common/CMakeFiles/oonf_common.dir/avl.c.obj
[  2%] Building C object src-api/common/CMakeFiles/oonf_common.dir/daemonize.c.obj
[  3%] Building C object src-api/common/CMakeFiles/oonf_common.dir/netaddr.c.obj
[  3%] Building C object src-api/common/CMakeFiles/oonf_common.dir/netaddr_acl.c.obj
[  4%] Building C object src-api/common/CMakeFiles/oonf_common.dir/string.c.obj
[  4%] Building C object src-api/common/CMakeFiles/oonf_common.dir/template.c.obj
Linking C shared library ../../liboonf_common.so
/locale/ANDROID/android-ndk-r8e/toolchains/arm-linux-androideabi-4.7/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.7/../../../../arm-linux-androideabi/bin/ld: error: CMakeFiles/oonf_common.dir/autobuf.c.obj: incompatible target
/locale/ANDROID/android-ndk-r8e/toolchains/arm-linux-androideabi-4.7/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.7/../../../../arm-linux-androideabi/bin/ld: error: CMakeFiles/oonf_common.dir/avl_comp.c.obj: incompatible target
/locale/ANDROID/android-ndk-r8e/toolchains/arm-linux-androideabi-4.7/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.7/../../../../arm-linux-androideabi/bin/ld: error: CMakeFiles/oonf_common.dir/avl.c.obj: incompatible target
/locale/ANDROID/android-ndk-r8e/toolchains/arm-linux-androideabi-4.7/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.7/../../../../arm-linux-androideabi/bin/ld: error: CMakeFiles/oonf_common.dir/daemonize.c.obj: incompatible target
/locale/ANDROID/android-ndk-r8e/toolchains/arm-linux-androideabi-4.7/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.7/../../../../arm-linux-androideabi/bin/ld: error: CMakeFiles/oonf_common.dir/netaddr.c.obj: incompatible target
/locale/ANDROID/android-ndk-r8e/toolchains/arm-linux-androideabi-4.7/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.7/../../../../arm-linux-androideabi/bin/ld: error: CMakeFiles/oonf_common.dir/netaddr_acl.c.obj: incompatible target
/locale/ANDROID/android-ndk-r8e/toolchains/arm-linux-androideabi-4.7/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.7/../../../../arm-linux-androideabi/bin/ld: error: CMakeFiles/oonf_common.dir/string.c.obj: incompatible target
/locale/ANDROID/android-ndk-r8e/toolchains/arm-linux-androideabi-4.7/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.7/../../../../arm-linux-androideabi/bin/ld: error: CMakeFiles/oonf_common.dir/template.c.obj: incompatible target
/locale/ANDROID/android-ndk-r8e/toolchains/arm-linux-androideabi-4.7/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.7/../../../../arm-linux-androideabi/bin/ld: error: cannot find -lc
/locale/ANDROID/android-ndk-r8e/toolchains/arm-linux-androideabi-4.7/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.7/../../../../arm-linux-androideabi/bin/ld: error: cannot find -ldl
collect2: error: ld returned 1 exit status
make[2]: *** [liboonf_common.so] Error 1
make[1]: *** [src-api/common/CMakeFiles/oonf_common.dir/all] Error 2
make: *** [all] Error 2


Thanks in advance,
Karoly
--

-- 
Olsr-dev mailing list
Olsr-dev <at> lists.olsr.org
https://lists.olsr.org/mailman/listinfo/olsr-dev
Henning Rogge | 7 Jan 11:05 2014
Picon

Fix problems with current MinGW builds

Hi,

the attached patch should fix the problems with the current MinGW
builds. MinGW is improving, which broke our compatibility layer for the
old bugs of MinGW...

This patch will most likely break some outdated MinGW builds, anyone who
want to fix this too is free to do so.

Henning Rogge
-- 
Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
Kommunikation, Informationsverarbeitung und Ergonomie FKIE
Kommunikationssysteme (KOM)
Fraunhofer Straße 20, 53343 Wachtberg, Germany
Telefon +49 228 9435-961,   Fax +49 228 9435 685
mailto:henning.rogge <at> fkie.fraunhofer.de http://www.fkie.fraunhofer.de
Attachment (mingw.patch): text/x-patch, 5253 bytes
Attachment (smime.p7s): application/pkcs7-signature, 8 KiB
--

-- 
Olsr-dev mailing list
Olsr-dev <at> lists.olsr.org
https://lists.olsr.org/mailman/listinfo/olsr-dev
Ferry Huberts | 6 Jan 09:03 2014

commits

Dear Bernhard,

Please send your patch to the mailing list first, and wait for review 
before committing them.

-- 
Ferry Huberts

--

-- 
Olsr-dev mailing list
Olsr-dev <at> lists.olsr.org
https://lists.olsr.org/mailman/listinfo/olsr-dev

Vigneswaran R | 27 Dec 11:10 2013

OLSRv2 Segfault

Hello,

I am running olsrd2 on a few (qemu) virtual machines. On one of the 
virtual machines, olsrd2 segfaults within a few seconds. I am invoking 
OLSRd2 in the following manner,

     ./olsrd2 --set interface[eth0].bindto=10.0.0.0/8 --set 
interface[eth1].bindto=10.0.0.0/8 --set interface[eth2].bindto=10.0.0.0/8

Traced the error using gdb to some extent. Please see the following 
patch for context.

In general, addr_start->_block_end becomes NULL just before exiting from 
the do..while loop. However, in some cases, addr_start->_block_end 
becomes NULL before the do..while loop meeting the exit criteria 
(addr_end == last_addr). So, the loop continues and trying to 
de-reference NULL pointer causing segfault.

--- a/oonf_api/src-api/rfc5444/rfc5444_msg_generator.c    2013-12-19 
18:27:48.471467295 +0530
+++ b/oonf_api/src-api/rfc5444/rfc5444_msg_generator.c    2013-12-27 
14:15:14.000000000 +0530
 <at>  <at>  -1180,7 +1180,7  <at>  <at> 
      tlvblock_length[0] = (ptr - tlvblock_length - 2) >> 8;
      tlvblock_length[1] = (ptr - tlvblock_length - 2) & 255;
      addr_start = list_next_element(addr_end, _addr_node);
-  } while (addr_end != last_addr);
+  } while (addr_end != last_addr && addr_start->_block_end != NULL);

    /* store size of address(tlv) data */
    msg->_bin_addr_size = ptr - start;

I am using the latest oonf_api (last commit: 
2355db6a460abe10cc7096842b3b10686c68012c) and olsrd2 (last commit: 
23051120419372a175ddb08fa8a3bb8d7d709f1e) repositories.

The Interface details are,

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
     inet 127.0.0.1/8 scope host lo
     inet6 ::1/128 scope host
        valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast 
state UP qlen 1000
     link/ether de:ad:be:ef:5a:38 brd ff:ff:ff:ff:ff:ff
     inet 10.5.11.1/8 brd 10.255.255.255 scope global eth0
     inet6 fe80::dcad:beff:feef:5a38/64 scope link
        valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast 
state UP qlen 1000
     link/ether de:ad:be:ef:0d:2f brd ff:ff:ff:ff:ff:ff
     inet 10.5.11.2/8 brd 10.255.255.255 scope global eth1
     inet6 fe80::dcad:beff:feef:d2f/64 scope link
        valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast 
state UP qlen 1000
     link/ether de:ad:be:ef:5a:39 brd ff:ff:ff:ff:ff:ff
     inet 10.5.11.3/8 brd 10.255.255.255 scope global eth2
     inet6 fe80::dcad:beff:feef:5a39/64 scope link
        valid_lft forever preferred_lft forever

Regards,
Vignesh

--

-- 
Olsr-dev mailing list
Olsr-dev <at> lists.olsr.org
https://lists.olsr.org/mailman/listinfo/olsr-dev

Karoly Szabo | 6 Nov 19:56 2013
Picon

OLSRv2 configuration and wlan

Hi all, I swapped from version 1 to version 2.
I found some information about the configuration file and i wandered if exist a complete
list of all the parameters that is possible to set.

Also I have a problem regarding to Wifi devices, after launching:
olsrd wlan1 eth0 lo

In telnet I tried to obtain information about all the interfaces
and I'm missing all wlan informations except default hello interval and vtime (currently connected and pingning a tablet).
> nhdp interface
Interface 'eth0': hello_interval=2   hello_vtime=20 
    Address: 147.162.97.20
    Address: fe80::218:8bff:fe1b:7e59
Interface 'lo': hello_interval=2   hello_vtime=20 
Interface 'wlan1': hello_interval=2   hello_vtime=20 

> Connection closed by foreign host.

the routes command also show me all the eth0 nodes but no one from wlan1.
Somebody had similar problems? Or am I missing something?

Thanks in advance,
Karoly Szabo
--

-- 
Olsr-dev mailing list
Olsr-dev <at> lists.olsr.org
https://lists.olsr.org/mailman/listinfo/olsr-dev
Will Hawkins | 21 Oct 19:53 2013

iOS Makefile

Hello everyone!

I've spent some time putting together a Makefile (and a few small
patches) to get olsrd to build for iOS. Is the group amenable to looking
over those patches for inclusion? Just thought I'd ask before sending
them along.

Thanks everyone for your work olsrd!

Will

--

-- 
Olsr-dev mailing list
Olsr-dev <at> lists.olsr.org
https://lists.olsr.org/mailman/listinfo/olsr-dev


Gmane