[Olsr-users] Where to start to build a WMN

kadir yüceer (spam-protected)
Sat Oct 23 12:26:49 CEST 2010


2010/10/23 Henning Rogge <(spam-protected)>

>  On Saturday 23 October 2010 11:58:40 kadir yüceer wrote:
>
> > Thank you for this really informing mail. Pardon my "query flood" but I'm
>
> > coming up with new questions by the time I'm growing my vision on olsrd.
>
> No problem...
>
>  > Did I get this right? : There is an already developed API for C(with
>
> > connection and data exchange methods) and I can develop a mesh network
>
> > application on C easily, but first I have to implement the interface of
>
> > olsrd to make it communicate with and run on windows mobile.
>
> I am not sure you got it right.
>
> The API I was talking about is to write an adaptation layer between the
> OLSRd core and your operation system. Every OS does things differently, so
> they have to be OS specific code in a routing agent.
>
> The routing agent itself does set up IP routing rules for your normal
> traffic and your applications can use them.
>
> Normally your application does not interact with OLSRd directly.
>
> There are some application interfaces in OLSRd, mostly in terms of plugins
> that open a socket so you can query status information from OLSRd. The
> development version of OLSRd contains a telnet and a HTTP server to make it
> easier to write more of this application interfaces.
>
> > Or are you saying that I have to implement them IF I wanna work on C# ?
>
> You have to implement the OS adaptation stuff for windows mobile... in C.
>
> After this it should be possible for all IP capable applications (C, C#,
> ...) to use the unicast routes of OLSRd for communication.
>

Oh now I see. My first question was about Windows Mobile OLSR daemon created
by Moviquity (on sourceforge.net), even the readme file that I was talking
about belongs to it, but I couldn't make it clear because I didn't know that
the thing in that project was to develop these interface implementations
that we've been talking about. My actual problem is to embed this
(Moviquity) daemon to the operating system, and I assume I should look for
that answer elsewhere :)

Thanks for your patience and explanations.
Kind regards
Kadir
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20101023/49c32704/attachment.html>


More information about the Olsr-users mailing list