From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Dave Taht <dave.taht@gmail.com>
Cc: Andrew McGregor <andrewmcgr@gmail.com>,
"babel-users@lists.alioth.debian.org"
<babel-users@lists.alioth.debian.org>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
Felix Fietkau <nbd@nbd.name>
Subject: Re: [Cerowrt-devel] [Babel-users] more wet paint - babel unicast IHU for short-rtt path optimization
Date: Tue, 07 Apr 2015 22:28:06 +0200 [thread overview]
Message-ID: <87zj6jfzu1.wl-jch@pps.univ-paris-diderot.fr> (raw)
In-Reply-To: <CAA93jw5=L7wjEsBxqnUsoQhgMA69w57BG=wQmVz59tkWmFt82g@mail.gmail.com>
> My understanding of the babeld code is that unicast code is in there
> but not used, and if it were used, it would not work against existing
> babel daemons. ?
You MAY send any Babel TLV over unicast except a Hello. Hellos MUST be
sent over multicast. The receiver doesn't care (except for Hellos).
Look at message.c, function send_ihu. around line 1693. If there's
already a unicast TLV queued, then the IHU is appended to that, and sent
over unicast. Otherwise, the IHU is appended to the multicast buffer.
There would be no problem sending all IHUs over unicast, but it would
probably cause additional NDs. A more productive endeavour would be to
send updates over unicast when there are few neighbours on a given
interface, but I'm afraid it might cause Babel more difficult to debug.
-- Juliusz
next prev parent reply other threads:[~2015-04-07 20:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 18:56 [Cerowrt-devel] " Dave Taht
2015-04-07 20:28 ` Juliusz Chroboczek [this message]
2015-04-07 20:44 ` [Cerowrt-devel] [Babel-users] " Dave Taht
2015-04-07 20:52 ` Juliusz Chroboczek
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zj6jfzu1.wl-jch@pps.univ-paris-diderot.fr \
--to=jch@pps.univ-paris-diderot.fr \
--cc=andrewmcgr@gmail.com \
--cc=babel-users@lists.alioth.debian.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=nbd@nbd.name \
/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