netdev - Re: IPv6 destination cache in Linux kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 05 Jul 2011 13:58:58 -0600
From:	Chris Friesen <chris.friesen@...band.com>
To:	David Miller <davem@...emloft.net>
CC:	mparemm@...il.com, netdev@...r.kernel.org
Subject: Re: IPv6 destination cache in Linux kernel

On 07/04/2011 06:46 PM, David Miller wrote:
> From: Mikhail Paremski<mparemm@...il.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@...band.com
www.genband.com
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html