[Olsr-users] Accessing OLSR parameters [Contd..]
Mon Sep 30 09:16:13 CEST 2013
ETX isn't using L2 feedback. ETX measures loss at L3 and calculates a link metric.
I would say L2 feedback reads out some data from NIC driver and calculates the link metric from that. It could also use the ETX data and merge (as the NL80211 plugin does).
First, try what you can do with ETX, using shorter timers for hello, TC and the ETX calculation mechanism. You may need to recompile.
When you need faster adoption of changes, start using RSSI. This would need the NL80211 plugin.
Please report progress.
Op 28 sep. 2013, om 17:51 heeft Shyam B <(spam-protected)> het volgende geschreven:
> Hi Hening, Teco,
> Thanks for your time and apologies for the delayed reply.
> Yes, I already have OLSR up and running (with build v 0.6.6) on Ubuntu(x86), RPi(Arm) and TP-Link router(Mips). So far so good!
> This is what I wish to do:
> 1) Read the ETX parameter "to determine link quality between nodes" (I got info on ETX from here: http://www.inf.ufrgs.br/~wlccordeiro/resources/olsr/README.html)
> 2) If it is above a certain threshold, I need to perform a job and if below the threshold, I change the position of my flying vehicle so as to improve the ETX link quality to perform the same job.
> I will get the L2 info into olsr by Monday.
> @Teco: I do have the time to get it up and running and your instructions on how to get the ETX info (say from python) would be very helpful. Probably, if I can query to send a message to a TCP socket of olsr supports, I can get the ETX info back from olsr. But, I am not sure, if this is how it was programmed.
> Best Regards,
> Olsr-users mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Olsr-users