> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Faulkner
> Sent: Tuesday, May 29, 2007 3:34 AM
> To: [email protected]
> Subject: Re: Questions about the Linux network stack
>
> Hey all,
>
> Not sure
On Tue, 29 May 2007 11:34:14 +0100
"Matthew Faulkner" <[EMAIL PROTECTED]> wrote:
> Hey all,
>
> Not sure if this should be asked within this mailing list or netdev,
> so please accept my appologies if it's in the wrong place.
>
> I'd like to know what the best way to go about "profiling" the lin
Hey all,
Not sure if this should be asked within this mailing list or netdev,
so please accept my appologies if it's in the wrong place.
I'd like to know what the best way to go about "profiling" the linux
networking code is. There are a few different methods of profiling the
linux from applicat
On Sun, 6 May 2007 19:13:37 -0400 (EDT) Alan Stern wrote:
> On Sun, 6 May 2007, Martin A. Brown wrote:
>
> > I, also, believe this to be true. (I am not a kernel developer).
>
> For a non-developer you certainly have provided remarkably detailed and
> helpful information!
>
> > : Moving on t
On Sun, 6 May 2007, Martin A. Brown wrote:
> I, also, believe this to be true. (I am not a kernel developer).
For a non-developer you certainly have provided remarkably detailed and
helpful information!
> : Moving on to IPsec...
>
> And, I can't help you with the IPSec questions.
Should I t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alan,
: The basic architecture of NetFilter is:
:
:--->[1]--->(ROUTE)--->[3]--->[4]---> where:
: |^ [1] NF_IP_PRE_ROUTING
: || [2] NF_IP_LOCAL_
I've got several questions about the way the kernel implements NAT,
the rest of Netfilter, and IPsec, and the relationships among them.
These matters aren't explained in any of the documentation I've been
able to come across.
To set the stage, here's a diagram showing the basic outline of how
Netf
