[B.A.T.M.A.N.] Where can i see, sequence number, eq, rq for an originator?

[B.A.T.M.A.N.] Where can i see, sequence number, eq, rq for an originator?

[Eugenio Carocci]

Hello everybody,

first of all, i want to excuse myself, if i write something wrong for
my horrible english. I am writing my thesis of Information Engineering
about your protocol. So, as i wrote in the object of the
message, i want to see where BATMAN-adv save the last sequence number
saved for a generic originator, and also
where it puts all the information act to evaluate the TQ toward each
originator of the mesh.

Thanks you for attenction

-- 
Eugenio Carocci

Re: [B.A.T.M.A.N.] Where can i see, sequence number, eq, rq for an originator?

[Antonio Quartulli]

[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]

Hello Eugenio,

On Wed, Sep 18, 2013 at 12:55:27AM +0200, Eugenio Carocci wrote:
> Hello everybody,
> 
> first of all, i want to excuse myself, if i write something wrong for
> my horrible english. I am writing my thesis of Information Engineering
> about your protocol.

It's not only ours, but it's everybody's protocol ;-)

> So, as i wrote in the object of the
> message, i want to see where BATMAN-adv save the last sequence number
> saved for a generic originator, and also
> where it puts all the information act to evaluate the TQ toward each
> originator of the mesh.
>

The information exported to the user are visible through the originator table
(batctl can help you getting that), but most of the things you were asking for
(I'm reading the subject of the email..)are not exported at all.

This means you can't see those values from a user prospective.
You would need to patch the code and print them manually (if you are really
interested in that..).
For this you may want to have a look at the "neigh_node" structure.




Cheers,

-- 
Antonio Quartulli

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: [B.A.T.M.A.N.] Where can i see, sequence number, eq, rq for an originator?

[Eugenio Carocci]

Thanks you for the reply, just one last question. Is there some paper
online that explain, how the protocol
avoid routing loop, may with some examples? :)

2013/9/18 Antonio Quartulli <antonio@meshcoding.com>:
> Hello Eugenio,
>
> On Wed, Sep 18, 2013 at 12:55:27AM +0200, Eugenio Carocci wrote:
>> Hello everybody,
>>
>> first of all, i want to excuse myself, if i write something wrong for
>> my horrible english. I am writing my thesis of Information Engineering
>> about your protocol.
>
> It's not only ours, but it's everybody's protocol ;-)
>
>> So, as i wrote in the object of the
>> message, i want to see where BATMAN-adv save the last sequence number
>> saved for a generic originator, and also
>> where it puts all the information act to evaluate the TQ toward each
>> originator of the mesh.
>>
>
> The information exported to the user are visible through the originator table
> (batctl can help you getting that), but most of the things you were asking for
> (I'm reading the subject of the email..)are not exported at all.
>
> This means you can't see those values from a user prospective.
> You would need to patch the code and print them manually (if you are really
> interested in that..).
> For this you may want to have a look at the "neigh_node" structure.
>
>
>
>
> Cheers,
>
> --
> Antonio Quartulli



-- 
Eugenio Carocci

Re: [B.A.T.M.A.N.] Where can i see, sequence number, eq, rq for an originator?

[Antonio Quartulli]

[-- Attachment #1: Type: text/plain, Size: 889 bytes --]

On Wed, Sep 18, 2013 at 10:16:51AM +0200, Eugenio Carocci wrote:
> Thanks you for the reply, just one last question. Is there some paper
> online that explain, how the protocol
> avoid routing loop, may with some examples? :)

The document explaining something closer to what you want can be found on the
wiki: http://www.open-mesh.org/projects/batman-adv/wiki/OGM

However, the current implementation of the protocol is the result of a sort of
"evolution" and for this reason what you read in the document may not reflect
the current implementation 100% (but we always try to keep the two in sync).

Here[1] you also have an explanation of the former protocol, and some of the
things written there are still valid, but I'd use it only to get the flavour
of what is going on (not as a real reference).


Regards,


p.s. don't top-post please

-- 
Antonio Quartulli

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]