Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 19 Aug 2006 21:57:03 -0700
From:      Julian Elischer <julian@elischer.org>
To:        Ruslan Ermilov <ru@freebsd.org>
Cc:        freebsd-net@freebsd.org, Rajkumar S <rajkumars@gmail.com>
Subject:   Re: ng_ip_input ?
Message-ID:  <44E7EB9F.5060503@elischer.org>
In-Reply-To: <20060819154215.GB9883@rambler-co.ru>
References:  <64de5c8b0608190514l1c2241edj57b114997e01a8b2@mail.gmail.com>	<20060819125550.GA8879@rambler-co.ru>	<64de5c8b0608190635q1fe2c0c5oe5d258748c1c5c95@mail.gmail.com>	<20060819135133.GC9271@rambler-co.ru>	<64de5c8b0608190728k47c9dd50kfaf8b94096aa128e@mail.gmail.com> <20060819154215.GB9883@rambler-co.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
Ruslan Ermilov wrote:

>On Sat, Aug 19, 2006 at 07:58:03PM +0530, Rajkumar S wrote:
>  
>
>>On 8/19/06, Ruslan Ermilov <ru@freebsd.org> wrote:
>>    
>>
>>>On Sat, Aug 19, 2006 at 07:05:49PM +0530, Rajkumar S wrote:
>>>      
>>>
>>>>Any points to docs to read about a packet's traversal in FreeBSD ip
>>>>stack? (especially wrt pf)
>>>>
>>>>        
>>>>
>>>What level of detalization do you need?  Filters, such as pf(4), are
>>>embedded into the normal processing using the pfil(9) API.
>>>      
>>>
>>I am a relative newbie learning freebsd. A broad overview with
>>pointers to manpages are ideal.  like the the simple pointer to
>>pfil(9) you gave along with a small description of where it appears.
>>
>>    
>>
>Then you can always start from reading the source code.
>It's been written by human beings.  :-)
>  
>

while the above seems harsh it turns out that /sys/netinet/ip_input.c is 
in fact a very easy file to
read due to the serial nature of ip processing.. give it a try

>
>Cheers,
>  
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44E7EB9F.5060503>