[Olsr-users] Help with layer2info plugin
Thu Mar 3 02:52:10 CET 2016
Yes, it's more clear now.
So, if nl80211_plugin doesn't fill up data into layer2 database (because it
isn't work correctly) the DLEP_Radio will transmit null data to DLEP_Router
(because there is no data in layer2 database), this interpretation are
DLEP_Router puts the data received from DLEP_Radio into layer2 database?
These data were taken from there, so don't make sense put the data there
Thank you for yours explanation.
I need this information because on my mesh network i want to apply some QoS
policies, so i need to have some knowledge from state "ambient" (ambient =
available bandwidth, SNR, delay, packet lost and etc). I guess that this
plugin (nl80211) provides these information.
2016-03-02 21:18 GMT+00:00 Ferry Huberts <(spam-protected)>:
> On 02/03/16 21:43, Henning Rogge wrote:
>> On Wed, Mar 2, 2016 at 6:23 PM, Fábio Carvalho
>> <(spam-protected)> wrote:
>>> So, if nl80211_plugin doesn't work the DLEP_router will work correctly?
>>> DLEP_pugin doesn't depend the nl80211_plugin, right?
>> There are TWO DLEP Plugins... DLEP-Radio and DLEP-Router.
>> Both of these plugins AND nl80211_plugin interact with the layer2
>> NL80211 fills up data into the layer2 database by querying the Linux
>> Kernel about Wifi.
>> DLEP-Radio TAKES data from the layer2 database and transmit it over a
>> local LAN connection.
>> DLEP-Router receives this data from DLEP-Radio and puts it into the
>> Layer2 database.
> Maybe clearer names would be 'DLEP-Server' and 'DLEP-Client' ?
>> Both Layer2Info-Plugin and the FF-DAT-Metric take data from the layer2
>> I hope this clears up the whole thing a little bit.
> Ferry Huberts
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Olsr-users