[Olsr-users] OLSR routing table plugin
Mon Apr 22 10:55:30 CEST 2013
if you want to use a custom metric, you have to write a custom metric
implementation (one example of this is in src/lq_plugin_default_ff.c).
If you just want to put the result of the dijkstra into a different
routing table, you can use a configuration parameter. Look for the
parameters "RtTable", "RtTableDefault" and "RtTableTunnel" in the
documented configuration file in files/olsrd.conf.default.full
The Olsr.org implementation only accepts link costs as a 32 bit unsigned
integer between 1 and 2^24-1. It would require an invasive modification
of the core to change this.
Consider multiplying your metric with a constant value to transform a
fractional number to an integer.
On 04/16/2013 08:02 PM, Masood Alam wrote:
> ok...that means I need to change "distance" to change the dijkstra
> output table. right? ........Now I have two more questions.
> First.... I want to use my custom metric as distance to calculate the
> dijkstra output. What do I need to change? I think Linkset... right?
> Can I change the linkset tuples to have my custom metric fed as input to
> dijkstra algorithm? What else do I need to change if I change linkset
> tuples? Please correct me if wrong concept. My custom metric may be
> considered as a maximized function of RFC 3626 compliant OLSR distance
> and link quality between the neighbour inteterfaces. The link quality is
> assumed to be a function of SNR between the two SYM neighbors.
> 2nd........can dijkstras algorithm calculate routing table if the
> distance is of type double instead of integer?
> Masood Alam
> *From:* Henning Rogge <(spam-protected)>
> *To:* Masood Alam <(spam-protected)>
> *Cc:* "(spam-protected)" <(spam-protected)>
> *Sent:* Tuesday, 16 April 2013, 0:13
> *Subject:* Re: [Olsr-users] OLSR routing table plugin
> The olsr routing daemon of Olsr.org allows to configure the routing
> table for the dijkstras output, you don't need a plugin for this.
> Henning Rogge
> On Mon, Apr 15, 2013 at 5:25 PM, Masood Alam <(spam-protected)
> <mailto:(spam-protected)>> wrote:
> > Hi
> > Thanks for your reply, Actually I am talking about Unik OLSR please
> refr to
> > the following URL's
> > http://www.olsr.org/docs/olsr_plugin_paper.pdf
> > As I understand from these documents there is some plugin available
> that can
> > replace the default routing table with your custom table. I want to
> use this
> > feature in my MS research. Do you know wher I can find a plugib for table
> > replacement. Kindly guide.
> > Masood Alam
> > From: Henning Rogge <(spam-protected)
> > To: Masood Alam <(spam-protected) <mailto:(spam-protected)>>
> > Cc: "(spam-protected) <mailto:(spam-protected)>"
> <(spam-protected) <mailto:(spam-protected)>>
> > Sent: Monday, 15 April 2013, 17:50
> > Subject: Re: [Olsr-users] OLSR routing table plugin
> > I am not sure what you are asking for.
> > Henning Rogge
> > On Mon, Apr 15, 2013 at 11:11 AM, Masood Alam <(spam-protected)
> <mailto:(spam-protected)>> wrote:
> >> I have seen UNIK OLSR that supports plugins to test different
> >> functionality.
> >> can anybody tell me if routing table plugin is available somewhere? Can
> >> somebody help me in writing NS3 script for changing the inserting my
> >> customized routing table into olsr. Please help
> >> Masood
> >> --
> >> Olsr-users mailing list
> >> (spam-protected) <mailto:(spam-protected)>
> >> https://lists.olsr.org/mailman/listinfo/olsr-users
> > --
> > We began as wanderers, and we are wanderers still. We have lingured
> > long enough on the shores of the cosmic ocean. We are ready at last to
> > set sail for the stars - Carl Sagan
> We began as wanderers, and we are wanderers still. We have lingured
> long enough on the shores of the cosmic ocean. We are ready at last to
> set sail for the stars - Carl Sagan
Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
Kommunikation, Informationsverarbeitung und Ergonomie FKIE
Fraunhofer Straße 20, 53343 Wachtberg, Germany
Telefon +49 228 9435-961, Fax +49 228 9435 685
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 6169 bytes
Desc: S/MIME Cryptographic Signature
More information about the Olsr-users