From: Denis Ovsienko <infrastation@yandex.ru>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Cc: babel-users <babel-users@lists.alioth.debian.org>
Subject: Re: [Cerowrt-devel] [Babel-users] switching cerowrt to quagga-babeld issues
Date: Tue, 03 Jul 2012 12:10:08 +0400 [thread overview]
Message-ID: <458481341303008@web7d.yandex.ru> (raw)
In-Reply-To: <206861341262491@web23d.yandex.ru>
>> How goeth ipv6?
>
> IPv6 default route is lost somewhere on the way from kernel to zebra process (and not promoted by babeld respectively). I'll try looking at it tomorrow and also pulling together some thoughts on the rest of your message.
>
This seems to be caused by a difference in kernel behaviour between current CeroWrt and, for example, my notebook (3.3.7-1.fc16.x86_64). Plugged into the same network one after another, they end up with different default routes in kernel:
(cero)
default via fe80::230:48ff:fed4:63e4 dev ge00 proto kernel metric 1024 expires 1797sec
(notebook)
default via fe80::230:48ff:fed4:63e4 dev em1 proto static metric 1
default via fe80::230:48ff:fed4:63e4 dev em1 proto kernel metric 1024 expires 1786sec
Note the kernel/static route protocol. The established practice of zebra process used to be ignoring any RTPROT_KERNEL netlink messages. It is not clear if RTPROT_BOOT/RTPROT_RA should be used for a RA-originated route, but RTPROT_STATIC does the job in the latter case anyway and the default route reaches zebra. In the former case the default route is effectively isolated from zebra.
Does anybody know where this difference comes from?
--
Denis Ovsienko
next prev parent reply other threads:[~2012-07-03 8:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA93jw40kiOwDnOzG-_jUn7nKpky59bNBTec8ynjVwJJhKxr0Q@mail.gmail.com>
[not found] ` <2187151341044351@web9d.yandex.ru>
[not found] ` <7isjdcpm1q.fsf@lanthane.pps.jussieu.fr>
[not found] ` <40851341093226@web25d.yandex.ru>
[not found] ` <7ik3yoz7p2.fsf@lanthane.pps.jussieu.fr>
[not found] ` <CAA93jw5p9EqoK09Y_AXaHG_DfH-u_QDYU_FKOK_hhxBRDcuqAA@mail.gmail.com>
[not found] ` <1521341229978@web13h.yandex.ru>
2012-07-02 15:36 ` Dave Taht
2012-07-02 16:16 ` L. Aaron Kaplan
2012-07-02 16:44 ` Dave Taht
2012-07-02 16:54 ` L. Aaron Kaplan
2012-07-02 17:13 ` [Cerowrt-devel] DLEP [was: switching cerowrt to quagga-babeld issues] Juliusz Chroboczek
2012-07-02 17:36 ` [Cerowrt-devel] [Babel-users] " Henning Rogge
2012-07-02 19:50 ` [Cerowrt-devel] " L. Aaron Kaplan
2012-07-02 20:54 ` [Cerowrt-devel] [Babel-users] switching cerowrt to quagga-babeld issues Denis Ovsienko
2012-07-03 8:10 ` Denis Ovsienko [this message]
2012-07-03 12:35 ` Denis Ovsienko
2012-07-03 12:47 ` Gabriel Kerneis
2012-07-03 13:18 ` Dave Taht
2012-07-03 14:14 ` [Cerowrt-devel] " Denis Ovsienko
2012-07-06 16:36 ` [Cerowrt-devel] [Babel-users] " Denis Ovsienko
2012-07-06 16:52 ` [Cerowrt-devel] IPv6 RA and RTPROT_whatever [was: switching cerowrt to quagga-babeld issues] Juliusz Chroboczek
2012-07-03 19:17 ` [Cerowrt-devel] [Babel-users] switching cerowrt to quagga-babeld issues Jim Gettys
2012-07-06 16:59 ` David Lamparter
2012-07-07 15:53 ` dpreed
2012-07-03 15:28 ` Robert Bradley
2012-07-03 15:55 ` Robert Bradley
2012-07-04 11:34 ` Denis Ovsienko
2012-07-05 14:15 ` dpreed
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=458481341303008@web7d.yandex.ru \
--to=infrastation@yandex.ru \
--cc=babel-users@lists.alioth.debian.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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