From: Antonio Quartulli <ordex@autistici.org>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Implement DAT for IPv6
Date: Fri, 1 Mar 2013 12:48:03 +0100 [thread overview]
Message-ID: <20130301114803.GF20607@ritirata.org> (raw)
In-Reply-To: <CAP5XTDPApa0OvO-Z3mWRFsvk=aL+No09_Ce2eUxkZp+B_rXC9g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]
On Fri, Mar 01, 2013 at 01:41:28PM +0200, Mihail Costea wrote:
> On 1 March 2013 13:11, Antonio Quartulli <ordex@autistici.org> wrote:
> > On Fri, Mar 01, 2013 at 12:59:18PM +0200, Mihail Costea wrote:
> >> Hi,
> >>
> >> I've started implementing DAT for IPv6 and I have a few questions
> >> regarding the design.
> >> I've already implemented a snooping mechanism for Network Solicitation
> >> package,
> >
> > I forgot to ask here: packets generated by the IPv6 the Neigh Discovery Protocol
> > are sent on a periodic basis, right? so what is the idea behind the snooping
> > mechanism? There is not a request (like for ARP), right? So when should the data
> > in distributed table be used?
>
> From what I understood the Neighbor Solicitation and Neighbor
> Advertisement packets are the ARP equivalents.
> So if we receive a Neighbor Solicitation than we would use the
> distributed table and send the Neighbor Advertisement directly.
Oh ok, It was my fault. I quickly re-read part of the RFC4861: only router
advertisement are sent on a periodic basis, while the neighbour advertisement is
asynchronously sent either on address change or as a reply to a neighbour
solicitation.
Thanks.
Cheers,
--
Antonio Quartulli
..each of us alone is worth nothing..
Ernesto "Che" Guevara
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-03-01 11:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 10:59 [B.A.T.M.A.N.] Implement DAT for IPv6 Mihail Costea
2013-03-01 11:08 ` Antonio Quartulli
2013-03-01 11:38 ` Mihail Costea
2013-03-01 11:43 ` Antonio Quartulli
2013-03-01 11:56 ` Mihail Costea
2013-03-08 9:22 ` Mihail Costea
2013-03-08 9:33 ` Antonio Quartulli
2013-03-08 10:11 ` Mihail Costea
2013-03-08 10:14 ` Antonio Quartulli
2013-03-01 11:11 ` Antonio Quartulli
2013-03-01 11:41 ` Mihail Costea
2013-03-01 11:48 ` Antonio Quartulli [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130301114803.GF20607@ritirata.org \
--to=ordex@autistici.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox