From: Mikhail Paremski <mparemm@gmail.com>
To: netdev@vger.kernel.org
Subject: IPv6 destination cache in Linux kernel
Date: Mon, 4 Jul 2011 17:35:04 -0700 [thread overview]
Message-ID: <CF5C0F47-9A82-44CF-8441-AC23C26E476B@gmail.com> (raw)
Hello,
I'm trying to understand how Linux kernel routes IPv6 datagrams. It looks it does it much different from IPv4. While IPv4 uses Destination cache to find out what is the destination IP, MAC and interface index to send packet out, in IPv6 case it uses some destination tree to do that. It also does not uses that tree in case, if destination address is not on a local network. Is it correct?So, I have a few questions:
1. What are the reasons to rout datagrams differently fromIPv4?
2. Where I could get details how IPv6 stack routes datagrams?
3. Are there around books like "IPv6 Core Protocols Implementation" but with Linux specific details?
4. Any other sources of information about this topic?
Thank you very much,
Mikhail.
next reply other threads:[~2011-07-05 0:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 0:35 Mikhail Paremski [this message]
2011-07-05 0:46 ` IPv6 destination cache in Linux kernel David Miller
2011-07-05 19:58 ` Chris Friesen
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=CF5C0F47-9A82-44CF-8441-AC23C26E476B@gmail.com \
--to=mparemm@gmail.com \
--cc=netdev@vger.kernel.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