* IPv6 destination cache in Linux kernel
@ 2011-07-05 0:35 Mikhail Paremski
2011-07-05 0:46 ` David Miller
0 siblings, 1 reply; 3+ messages in thread
From: Mikhail Paremski @ 2011-07-05 0:35 UTC (permalink / raw)
To: netdev
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: IPv6 destination cache in Linux kernel
2011-07-05 0:35 IPv6 destination cache in Linux kernel Mikhail Paremski
@ 2011-07-05 0:46 ` David Miller
2011-07-05 19:58 ` Chris Friesen
0 siblings, 1 reply; 3+ messages in thread
From: David Miller @ 2011-07-05 0:46 UTC (permalink / raw)
To: mparemm; +Cc: netdev
From: Mikhail Paremski <mparemm@gmail.com>
Date: Mon, 4 Jul 2011 17:35:04 -0700
> 1. What are the reasons to rout datagrams differently fromIPv4?
It was just a design decision made when the ipv6 routing code
was implemented.
> 2. Where I could get details how IPv6 stack routes datagrams?
By reading the source code.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: IPv6 destination cache in Linux kernel
2011-07-05 0:46 ` David Miller
@ 2011-07-05 19:58 ` Chris Friesen
0 siblings, 0 replies; 3+ messages in thread
From: Chris Friesen @ 2011-07-05 19:58 UTC (permalink / raw)
To: David Miller; +Cc: mparemm, netdev
On 07/04/2011 06:46 PM, David Miller wrote:
> From: Mikhail Paremski<mparemm@gmail.com>
> Date: Mon, 4 Jul 2011 17:35:04 -0700
>
>> 1. What are the reasons to rout datagrams differently fromIPv4?
>
> It was just a design decision made when the ipv6 routing code
> was implemented.
Presumably there was some rationale for doing it differently than the
existing IPv4 code. Or was it just for fun?
>> 2. Where I could get details how IPv6 stack routes datagrams?
>
> By reading the source code.
While the source code has the final say, for someone new to a given part
of the kernel it is helpful to have a high-level view of the overall
flow. It's a lot easier to understand something if you can place it in
the overall scheme of of things.
Chris
--
Chris Friesen
Software Developer
GENBAND
chris.friesen@genband.com
www.genband.com
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-07-05 19:59 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-07-05 0:35 IPv6 destination cache in Linux kernel Mikhail Paremski
2011-07-05 0:46 ` David Miller
2011-07-05 19:58 ` Chris Friesen
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.