Re: About RSSI using
WANG Liangyou <wangly <at> sari.ac.cn>
2012-01-06 07:55:02 GMT
Hi Henning,
Much appreciated for your great supports!
Best regards,
Leo
-----Original Message-----
From: Henning Rogge [mailto:hrogge <at> googlemail.com]
Sent: Friday, January 06, 2012 3:49 PM
To: WANG Liangyou
Cc: olsr-users <at> lists.olsr.org; olsr-dev <at> lists.olsr.org
Subject: Re: [Olsr-users] About RSSI using
This is the implementation of the "standard" link metric for OLSRd in
stable:
http://olsr.org/git/?p=olsrd.git;a=blob;f=src/lq_plugin_default_ff.c;h=dd4b7
d6037840c5668d4bfffa9edb06c07758368;hb=stable
This one is the older fixed point math based one:
http://olsr.org/git/?p=olsrd.git;a=blob;f=src/lq_plugin_default_fpm.c;h=5ff8
67169cd1eea5520e41fad4631047488d4477;hb=stable
And this one is even older, it use floating point math:
http://olsr.org/git/?p=olsrd.git;a=blob;f=src/lq_plugin_default_float.c;h=ef
395630f725b8aa11877fe1c2b737f822740c36;hb=stable
This one is slightly experimental:
http://olsr.org/git/?p=olsrd.git;a=blob;f=src/lq_plugin_default_ffeth.c;h=48
49a21ab14cebf6dd8084926a75a8aa1344a821;hb=stable
Each link metric has to implement a series of functions and put
pointers to them in a lq_handler struct, which is then registered with
a register_lq_handler() call.
(see
http://olsr.org/git/?p=olsrd.git;a=blob;f=src/lq_plugin.c;h=1814b662f5f4b94a
a564d10588d7cfe3ee96a255;hb=stable#l100
)
I hope this helps.
Henning
On Fri, Jan 6, 2012 at 02:23, WANG Liangyou <wangly <at> sari.ac.cn> wrote:
> Hi Henning,
> Much appreciated for your help!
>
> Would you please tell me how to get some example codes about "link metric"
> plugin for my reference?
>
> Thank you again!
>
> Best regards,
> Leo
>
> -----Original Message-----
> From: Henning Rogge [mailto:hrogge <at> googlemail.com]
> Sent: Thursday, January 05, 2012 6:47 PM
> To: WANG Liangyou
> Cc: olsr-users <at> lists.olsr.org; olsr-dev <at> lists.olsr.org
> Subject: Re: [Olsr-users] About RSSI using
>
> OLSRd contains a "link metric" plugin system, which allows you to plug
> in your own code for generating the LQ/NLQ values and calculate the
> link cost from it without changing the main code. You will find
> multiple examples in the code, maybe you can adapt one of them for
> your purpose.
>
> If you cannot find them, please tell me and I give you some pointers.
>
> Henning
>
> On Wed, Jan 4, 2012 at 07:40, WANG Liangyou <wangly <at> sari.ac.cn> wrote:
>> Dear all olsrd experts,
>>
>> Now I am focus on one project, which will implement fast routing based on
>> WiFi RSSI value.
>>
>> Such as two paramenter will be configured: rssi_low, rssi_high.
>>
>> If rssi on one link is more than rssi_high, then this link is active; if
>> rssi on this link is less than rssi_low,
>>
>> then this link will be inactive and no date will be transfer over this
> link.
>>
>>
>>
>> I know how to get real time rssi from wireless card, but do not know how
> to
>> control olsrd codes to change topology and route tables.
>>
>>
>>
>> Would you please help me investigate how to implement it with olsrd
codes?
>> Which functions are helpful?
>>
>> And is there already some similar solutions for my reference?
>>
>>
>>
>> Your any hints will be great help to me!
>>
>>
>>
>> Much appreciated in advance!
>>
>>
>>
>> Hope to get your answers!!!
>>
>>
>>
>> Best regards,
>>
>> Leo
>>
>>
>>
>>
>> --
>> Olsr-users mailing list
>> Olsr-users <at> lists.olsr.org
>> https://lists.olsr.org/mailman/listinfo/olsr-users
>
>
>
> --
> "Wo kämen wir hin, wenn alle sagten, wo kämem wir hin, und niemand
> ginge, um einmal zu schauen, wohin man käme, wenn man ginge." (Kurt
> Marti)
>
>
--
"Wo kämen wir hin, wenn alle sagten, wo kämem wir hin, und niemand
ginge, um einmal zu schauen, wohin man käme, wenn man ginge." (Kurt
Marti)
--
--
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
https://lists.olsr.org/mailman/listinfo/olsr-users
> and nodes recognize the neighbors and paths but there are no changes in the routing table.
You could send olsrd.conf and ip route show table all output.
> Also, I see lots of errors in /var/log/kern.log telling me 'ath5k phy0: no further txbuf available,
dropping packet.'
So this could be a 2nd problem. Or related to prev one.
I switched to ath5k (from madwifi) with move to kernel 3.0 (voyage-0.8.0). I recommend you give it a
thought. Especially if run ad hoc mode. You could send your network config (debian?)
> I think the problem may have something to do with 
RSS Feed