From: Hasso Tepper <hasso@estpak.ee>
To: netdev@oss.sgi.com
Subject: IPv6 and netlink
Date: Tue, 23 Nov 2004 23:22:50 +0200 [thread overview]
Message-ID: <200411232322.50083.hasso@estpak.ee> (raw)
While debugging IPv6 RIB in Quagga routing software I discovered some issues
with kernel rtnetlink messages.
1) RTM_NEWROUTE message with prefix ff00::/8 (if interface goes up or down)
is sent with rtm_type set to RTN_UNICAST. It's multicast route, so why not
RTN_MULTICAST? Is it bug?
2) If address is added to the interface, route is created by kernel to route
prefix to the intarface. In IPv4 these routes have rtm_protocol set to
RTPROT_KERNEL if announced it via rtnetlink, but that's not the case with
IPv6. It doesn't matter if address is added by the user or it's the link
local address (fe80::/64 route). Is it intentional or bug?
3) Not really rtnetlink related, but if this address is removed from
interface, route created by kernel (when address was added) isn't removed
from table. Is it intentional?
--
Hasso Tepper
Elion Enterprises Ltd.
WAN administrator
next reply other threads:[~2004-11-23 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 21:22 Hasso Tepper [this message]
2004-11-23 21:42 ` IPv6 and netlink David S. Miller
2004-11-25 21:13 ` Hasso Tepper
2004-11-26 1:14 ` YOSHIFUJI Hideaki / 吉藤英明
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=200411232322.50083.hasso@estpak.ee \
--to=hasso@estpak.ee \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).