headers
Fábio Almeida | 5 May 2011 17:15
Picon

Android Development - Samsung Galaxy

Hello,


My name is Fábio Almeida and I'm trying to implement and ad-hoc network in android and I want to use OLSR protocol. I'm new in this area so I have some doubts that I think that should be very simple to you. 

I want to create this network in order to create a real time network between some Android devices and share information. I'm using Samsung Galaxy GT-i5500 devices to do this.

I already found a custom wpa_supplicant in xda-developers (link to the thread) that ables this device to find ad-hoc networks. I already tested it creating an ad-hoc network with my laptop and it seems to work ok.

I already downloaded the pre compiled samsung android version of olsrd and put it on the device. 

Now i want to know how can I test if this is working fine. It would be very helpful if you can give me a simple tutorial of how to download and change the source code and compile it to make it run on Samsung galaxy. What are the main changes?

After all this is working, there is any way that I create and ad-hoc network with all the devices (5) and then just exchange some kind of data through the network?


Thanks for the help.

Regards,
Fábio Almeida
--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
Permalink | Reply | 15 comments |
headers
Markus Kittenberger | 5 May 2011 17:40
Picon
Picon

Re: Android Development - Samsung Galaxy

if u have stable working adhoc connectivity than you are mostly done *G
(does this wpa_supplicant (and your wifi dirver) allow to set a fixed bssid aswell?)

regarding olsrd:
pls take/create a new version, not the old precompiled binary,..

some weeks ago someone built olsrd for galayx s, i think he wrote some short howto onthis mailinslist aswell,..
(its afair mostly just setup android sdk and compile it,..)

Markus

2011/5/5 Fábio Almeida <fabio.andre.almeida <at> gmail.com>
Hello,

My name is Fábio Almeida and I'm trying to implement and ad-hoc network in android and I want to use OLSR protocol. I'm new in this area so I have some doubts that I think that should be very simple to you. 

I want to create this network in order to create a real time network between some Android devices and share information. I'm using Samsung Galaxy GT-i5500 devices to do this.

I already found a custom wpa_supplicant in xda-developers (link to the thread) that ables this device to find ad-hoc networks. I already tested it creating an ad-hoc network with my laptop and it seems to work ok.

I already downloaded the pre compiled samsung android version of olsrd and put it on the device. 

Now i want to know how can I test if this is working fine. It would be very helpful if you can give me a simple tutorial of how to download and change the source code and compile it to make it run on Samsung galaxy. What are the main changes?

After all this is working, there is any way that I create and ad-hoc network with all the devices (5) and then just exchange some kind of data through the network?


Thanks for the help.

Regards,
Fábio Almeida

--
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
Permalink | Reply | 13 comments |
headers
Damien Miliche | 9 May 2011 11:37
Favicon

Problems with the quagga plugin

Hi all,

I am currently busy with experimenting MANET routing, and especially olsrd.
Except for some quality wireless link problem, it performs quite good for
my tests.

Now I would like to connect my MANET to a fixed network running OSPF.
As I understood, the route redistribution between OLSR and OSPF is possible
via the combination of quagga and the corresponding plugin for olsrd.
After patching and recompiling quagga and loading the quagga plugin into
olsrd, I can see the olsrd routes in quagga ("show ip route").
I have some problems however:
 - a specific "show ip route olsr" makes the zebra daemon crash (connection
   closed for the telnet, and the daemon is stopped);
 - the olsr routes are marked as "inactive" in quagga;
 - these routes are not redistributed to the kernel;
 - these routes are not redistributed to other OSPF nodes.

I don't see however where is the problem. Has anyone of you experimented
such problems or in the contrary no problem while experimenting the same
setup?

The olsrd version I am using is 0.6.0 and the quagga version is 0.99.18.

I am using the default config files for quagga, with just the following
added to the ospfd.conf files:
    router ospf
     redistribute olsr
     network 192.168.20.0/24 area 0.0.0.0

For olsrd, the quagga plugin is loaded with the following parameters:
    LoadPlugin "olsrd_quagga.so.0.2.2"
    {
        PlParam "Redistribute" "ospf"
        PlParam "ExportRoutes" "only"
        PlParam "Distance" "125"
        PlParam "LocalPref" "false"
        PlParam "SockPath" "/var/run/zserv.api"
        PlParam "Version" "1"
    }

Thanks in advance for your help.

Best regards,

-- 
Damien Miliche

--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
Permalink | Reply | 13 comments |
headers
RC Loh | 10 May 2011 06:08
Picon
Favicon

Cannot communicate 2 hops away

Hi,

 

I have 3 MacBook Pro running OLSRD 0.6.0 with their IP addresses as shown below:

 

 

10.10.10.13/24                10.10.10.12/24            10.10.10.15/24

(macbook13)                    (macbook12)                (macbook15)

 

 

When I placed all the 3 MacBooks close together, all of them can PING to each other.

 

When I placed macbook13 far away from macbook15 such that the routing table of macbook13 did not have the DIRECT route to macbook15 but only had the route to macbook12. The PING started to fail.

 

Below are 2 questions:

 

1) When I did a PING from macbook13 to macbook15, I did not received a response from macbook15. Why?

 

2) When I brought all the 3 MacBooks back to close together, they still cannot PING to each other. Why?

 

Anything that I configured wrongly?

 

Any advise is appreciated.

 

Thanks in advance.

 

Rdgs,

Paul

 

--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
Permalink | Reply | 6 comments |
headers
Henning Rogge | 10 May 2011 07:57
Picon
Favicon

Re: Cannot communicate 2 hops away

On Tue May 10 2011 06:08:48 RC Loh wrote:
> Hi,
>  
> I have 3 MacBook Pro running OLSRD 0.6.0 with their IP addresses as shown
> below: 
>  
> 10.10.10.13/24                10.10.10.12/24            10.10.10.15/24
> (macbook13)                    (macbook12)                (macbook15)
>  
>  
> When I placed all the 3 MacBooks close together, all of them can PING to
> each other.
>  
> When I placed macbook13 far away from macbook15 such that the routing table
> of macbook13 did not have the DIRECT route to macbook15 but only had the
> route to macbook12. The PING started to fail.
>  
> Below are 2 questions:
>  
> 1) When I did a PING from macbook13 to macbook15, I did not received a
> response from macbook15. Why?
>  
> 2) When I brought all the 3 MacBooks back to close together, they still
> cannot PING to each other. Why?
>  
> Anything that I configured wrongly?
>  
> Any advise is appreciated.
A few standard questions first... *G*

1.) what version of olsrd did you use ? (run "olsrd -v")
2.) what was the routing table when mac 13 and mac 15 could not hear each 
other ?
3) did you receive OLSR packets on all three nodes (check with "tcpdump -i 
<interface> -s 0 -vv port 698")

Henning Rogge
-- 
Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
Kommunikation, Informationsverarbeitung und Ergonomie FKIE
Kommunikationssysteme (KOM)
Neuenahrer 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
GPG: E1C6 0914 490B 3909 D944 F80D 4487 C67C 55EC CFE0

--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
Permalink | Reply | 0 comments |
headers
Markus Kittenberger | 10 May 2011 11:50
Picon
Picon

Re: Cannot communicate 2 hops away



On Tue, May 10, 2011 at 6:08 AM, RC Loh <rc_loh <at> yahoo.com.sg> wrote:

Hi,

 

I have 3 MacBook Pro running OLSRD 0.6.0 with their IP addresses as shown below:

1. use a newer olsr version,..
(0.6.1 or stable tip)

it will not necessarily help, but we might be more interested in the bug,.. 

 

 

10.10.10.13/24                10.10.10.12/24            10.10.10.15/24

(macbook13)                    (macbook12)                (macbook15)

 

 

When I placed all the 3 MacBooks close together, all of them can PING to each other.

ok at least the wifi connection is configured, .. (-;

 

When I placed macbook13 far away from macbook15 such that the routing table of macbook13 did not have the DIRECT route to macbook15 but only had the route to macbook12. The PING started to fail.

maybe try same scenario without olsrd, and static routing ,..

 

Below are 2 questions:

 

1) When I did a PING from macbook13 to macbook15, I did not received a response from macbook15. Why?

hmm hoenstly, answer for this you have to answer yourself,

as it just might be an olsrd problem,.. 

 

2) When I brought all the 3 MacBooks back to close together, they still cannot PING to each other. Why?

anything is possible *G 

 

Anything that I configured wrongly?

very likely,.. 

 

Any advise is appreciated.

ok as my above answers, where for sure not very helpful,.. (but your bugreport wasn`t aswell (-;)

check with txtinfo on each olsrd node, if it sees the neighbours u think it should see
and which routes it calculated,..

afterwards check if this routes are in kernel aswell 

for your setup where 13 could not see 15, but both see 14

it should look like this

13:
direct route to 14
15 reachable via 14

14:
direct route to 13
direct route to 15

15:
direct route to 14
13 reachable over 14

if you have this routes in kernel (as olsrd wrote them , or cause you configured them manually) and you still can not ping between 13 and 15, you have no routing/olsrd problem but something else is broken,..

e.g. u did not eneable forwarding on 14 (and/or bsd olsrd version failed to do this for you)
or you still have firewall rules, or spoof filter stuff enabled, or ...

Markus

 

Thanks in advance.

 

Rdgs,

Paul

 


--
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
Permalink | Reply | 0 comments |
headers
RC Loh | 12 May 2011 02:53
Picon
Favicon

Re: Cannot communicate 2 hops away

Hi Henning, Markus,
 
I did the same experiment with 3 LINUX machines and realised that the 2 furthest LINUX machines are able to communicate via the middle LINUX machine.
 
I begin to suspect it is the MacBook Pro OSX that was causing the problems that I had previously.
 
May I know what version of OSX that the OLSRD 0.6.0 has been tested on?
 
Thank you.
 
Rdgs,
Paul

 

From: RC Loh <rc_loh <at> yahoo.com.sg>
To: Henning Rogge <henning.rogge <at> fkie.fraunhofer.de>
Cc: olsr-users <at> lists.olsr.org
Sent: Wednesday, 11 May 2011 11:51:48
Subject: Re: [Olsr-users] Cannot communicate 2 hops away

Hi Henning and all,
 
Thank you very much for all your advise.
 
Attached is the screen capture for "olsrd -v" and "tcpdump" taken from 10.10.10.15.
 
I have also attached the routing tables of Mac12 and Mac13 when 10.10.10.13 cannot PING to 10.10.10.15 via 10.10.10.12.
 
I have checked the following:
1) Set all the "firewall"s on all the 3 MacBook to OFF.
 
2) The ip forwarding is ON for all the 3 MacBook by using the command "sysctl -a | grep forwarding" and it gave net.inet.ip.forwarding=1
 
Hi Markus,
 
From what I checked from the OLRDS web site, the version 0.6.0 is the latest stable version.
 
 
Rdgs,
Paul
 
 

 
From: Henning Rogge <henning.rogge <at> fkie.fraunhofer.de>
To: olsr-users <at> lists.olsr.org
Cc: RC Loh <rc_loh <at> yahoo.com.sg>
Sent: Tuesday, 10 May 2011 13:57:07
Subject: Re: [Olsr-users] Cannot communicate 2 hops away

On Tue May 10 2011 06:08:48 RC Loh wrote:
> Hi,
> 
> I have 3 MacBook Pro running OLSRD 0.6.0 with their IP addresses as shown
> below:
> 
> 10.10.10.13/24                10.10.10.12/24            10.10.10.15/24
> (macbook13)                    (macbook12)                (macbook15)
> 
> 
> When I placed all the 3 MacBooks close together, all of them can PING to
> each other.
> 
> When I placed macbook13 far away from macbook15 such that the routing table
> of macbook13 did not have the DIRECT route to macbook15 but only had the
> route to macbook12. The PING started to fail.
> 
> Below are 2 questions:
> 
> 1) When I did a PING from macbook13 to macbook15, I did not received a
> response from macbook15. Why?
> 
> 2) When I brought all the 3 MacBooks back to close together, they still
> cannot PING to each other. Why?
> 
> Anything that I configured wrongly?
> 
> Any advise is appreciated.
A few standard questions first... *G*

1.) what version of olsrd did you use ? (run "olsrd -v")
2.) what was the routing table when mac 13 and mac 15 could not hear each
other ?
3) did you receive OLSR packets on all three nodes (check with "tcpdump -i
<interface> -s 0 -vv port 698")

Henning Rogge
--
Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
Kommunikation, Informationsverarbeitung und Ergonomie FKIE
Kommunikationssysteme (KOM)
Neuenahrer 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
GPG: E1C6 0914 490B 3909 D944 F80D 4487 C67C 55EC CFE0
--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
Permalink | Reply | 3 comments |
headers
RC Loh | 13 May 2011 02:48
Picon
Favicon

Re: Cannot communicate 2 hops away

Hi Henning, Markus,
 
I have upgraded the OLSRD to version 0.6.1. I have also changed the intermediate MacBook Pro. But the problem is still the same -- the OLSRD is still not able to route message via the intermediate MacBook Pro.
 
 
10.10.10.13                       10.10.10.11                            10.10.10.15
(Mac13)                               (Mac11)                                   (Mac15)
 
However, with the same setup but using LINUX, the OLSRD works.
 
I am beginning to suspect the problem is caused by the OSX of the MacBook Pro.
 
May I know which version of OSX is proven to work with the OLSRD?
 
Thanks in advance.
 
Rdgs,
Paul

From: Markus Kittenberger <Markus.Kittenberger <at> gmx.at>
To: RC Loh <rc_loh <at> yahoo.com.sg>
Cc: Henning Rogge <henning.rogge <at> fkie.fraunhofer.de>; olsr-users <at> lists.olsr.org
Sent: Thursday, 12 May 2011 14:35:41
Subject: Re: [Olsr-users] Cannot communicate 2 hops away



On Thu, May 12, 2011 at 2:53 AM, RC Loh <rc_loh <at> yahoo.com.sg> wrote:
Attached is the screen capture for "olsrd -v" and "tcpdump" taken from 10.10.10.15.

i did not see any attachments,..
(but probably the list server removed them due to size restrictions)

(btw noone needs images, just copy the text of the consoles into your mail)
 
Hi Markus,
 
From what I checked from the OLRDS web site,
hmm i love to  know what on the olsr.org site should be different, to recognise that 0.6.0 is not the newest,..

as i found no real difference between those 2 announcements on olsr.org


 
the version 0.6.0 is the latest stable version.
  
hmm this is the latest stable release:

and first line of this list is the latest stable version:
 
Markus
 
 
Rdgs,
Paul
 
 

 
From: Henning Rogge <henning.rogge <at> fkie.fraunhofer.de>
To: olsr-users <at> lists.olsr.org
Cc: RC Loh <rc_loh <at> yahoo.com.sg>
Sent: Tuesday, 10 May 2011 13:57:07
Subject: Re: [Olsr-users] Cannot communicate 2 hops away

On Tue May 10 2011 06:08:48 RC Loh wrote:
> Hi,
> 
> I have 3 MacBook Pro running OLSRD 0.6.0 with their IP addresses as shown
> below:
> 
> 10.10.10.13/24                10.10.10.12/24            10.10.10.15/24
> (macbook13)                    (macbook12)                (macbook15)
> 
> 
> When I placed all the 3 MacBooks close together, all of them can PING to
> each other.
> 
> When I placed macbook13 far away from macbook15 such that the routing table
> of macbook13 did not have the DIRECT route to macbook15 but only had the
> route to macbook12. The PING started to fail.
> 
> Below are 2 questions:
> 
> 1) When I did a PING from macbook13 to macbook15, I did not received a
> response from macbook15. Why?
> 
> 2) When I brought all the 3 MacBooks back to close together, they still
> cannot PING to each other. Why?
> 
> Anything that I configured wrongly?
> 
> Any advise is appreciated.
A few standard questions first... *G*

1.) what version of olsrd did you use ? (run "olsrd -v")
2.) what was the routing table when mac 13 and mac 15 could not hear each
other ?
3) did you receive OLSR packets on all three nodes (check with "tcpdump -i
<interface> -s 0 -vv port 698")

Henning Rogge
--
Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
Kommunikation, Informationsverarbeitung und Ergonomie FKIE
Kommunikationssysteme (KOM)
Neuenahrer 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
GPG: E1C6 0914 490B 3909 D944 F80D 4487 C67C 55EC CFE0

--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
Permalink | Reply | 1 comment |
headers
Damien Miliche | 12 May 2011 11:09
Favicon

bug in the quagga plugin

Hi,

I kept on with my investigations:

>  - a specific "show ip route olsr" makes the zebra daemon crash
>    (connection closed for the telnet, and the daemon is stopped); 

The crash also occurs for other protocols/codes (ospf, connected, ...);
it seems it happens only when zebra contains routes for the
corresponding protocol/code. However, this is then not related to the
quagga plugin. So forget about this problem.

Anyway:

>  - the olsr routes are marked as "inactive" in quagga;
>  - these routes are not redistributed to the kernel;
>  - these routes are not redistributed to other OSPF nodes. 

It seems that these problems are linked and have a common cause.
As I realized, while reading the post on
http://www.gossamer-threads.com/lists/quagga/dev/17522, the olsr routes
that are marked as inactive actually miss a valid route for the "via
field" (gateway/nexthop): "When the nexthop is not reachable (from zebra
point of view), the route stays inactive".

In my case, the missing routes should be directly reachable olsr nodes,
that is to say that in the kernel routing table, they would appear as
host entries with a /32-mask, without the G-flag and with a gateway
(normally not used) of 0.0.0.0.
However, the httpinfo or txtinfo plugins of olrd show these entries
with a gateway IP corresponding to the /32-IP of the node. Though, while
searching a bit, I found out that there would be a "bug" in Quagga,
which would not accept the routes where the destination is the same than
the gateway.
This bug is obvioulsy known, as we can read somewhere in the source code
of the quagga plugin (quagga.c):
/* Quagga BUG workaround: don't add routes with destination = gateway
   see http://lists.olsr.org/pipermail/olsr-users/2006-June/001726.html
*/
The workaround is indeed to return from the function before adding the
corresponding route.

A question, then: as the problem comes from the fact that destination =
gateway, and that in the case of a host-entry the gateway should not be
used, why does olsrd use the destination IP as gateway, and not 0.0.0.0
as the kernel does for the /32 entries?
I don't know if this gateway field is used somewhere else by olsrd, but
it could solve the problem and replace the workaround.

Given all that, I was wondering: has anyone ever had a successful
experience with this quagga plugin?
because as olsrd always creates /32 entries, the problem should have
appear everytime, at any try of the plugin.
Have I missed/misunderstood something?

Thanks in advance for your reactions and for your help.

Best regards,

-- 
Damien Miliche

--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
Permalink | Reply | 0 comments |
headers
Damien Miliche | 12 May 2011 11:04
Favicon

Problems with the quagga plugin

Hi,

I kept on with my investigations:

>  - a specific "show ip route olsr" makes the zebra daemon crash
>    (connection closed for the telnet, and the daemon is stopped); 

The crash also occurs for other protocols/codes (ospf, connected, ...);
it seems it happens only when zebra contains routes for the
corresponding protocol/code. However, this is then not related to the
quagga plugin. So forget about this problem.

Anyway:

>  - the olsr routes are marked as "inactive" in quagga;
>  - these routes are not redistributed to the kernel;
>  - these routes are not redistributed to other OSPF nodes. 

It seems that these problems are linked and have a common cause.
As I realized, while reading the post on
http://www.gossamer-threads.com/lists/quagga/dev/17522, the olsr routes
that are marked as inactive actually miss a valid route for the "via
field" (gateway/nexthop): "When the nexthop is not reachable (from zebra
point of view), the route stays inactive".

In my case, the missing routes should be directly reachable olsr nodes,
that is to say that in the kernel routing table, they would appear as
host entries with a /32-mask, without the G-flag and with a gateway
(normally not used) of 0.0.0.0.
However, the httpinfo or txtinfo plugins of olrd show these entries
with a gateway IP corresponding to the /32-IP of the node. Though, while
searching a bit, I found out that there would be a "bug" in Quagga,
which would not accept the routes where the destination is the same than
the gateway.
This bug is obvioulsy known, as we can read somewhere in the source code
of the quagga plugin (quagga.c):
/* Quagga BUG workaround: don't add routes with destination = gateway
   see http://lists.olsr.org/pipermail/olsr-users/2006-June/001726.html
*/
The workaround is indeed to return from the function before adding the
corresponding route.

A question, then: as the problem comes from the fact that destination =
gateway, and that in the case of a host-entry the gateway should not be
used, why does olsrd use the destination IP as gateway, and not 0.0.0.0
as the kernel does for the /32 entries?
I don't know if this gateway field is used somewhere else by olsrd, but
it could solve the problem and replace the workaround.

Given all that, I was wondering: has anyone ever had a successful
experience with this quagga plugin?
because as olsrd always creates /32 entries, the problem should have
appear everytime, at any try of the plugin.
Have I missed/misunderstood something?

Thanks in advance for your reactions and for your help.

Best regards,

-- 
Damien Miliche

--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
Permalink | Reply | 0 comments |

Gmane