netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ninad Adi <adi.ninad@gmail.com>
To: netfilter@vger.kernel.org
Subject: Re: QUES : connection tracking
Date: Tue, 22 Jun 2010 14:32:37 +0530	[thread overview]
Message-ID: <AANLkTimRqfY21Aymecae8ffB05PaDZ_aCuQsctdlHoTb@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinyiIqkyccSaDciSCbrbOYNPbS8sqA4Mj_VsTHq@mail.gmail.com>

To, Netfilter Giants and Professionals,

I am a netfilter newbie, trying to analyse the system architecturally.

Sorry for answering the questions myself, Let me know if I am wrong !!!!!

QUES:  What code is present architecturally in net/ipv4/netfilter
           directory and what code is present architecturally in net/netfilter
           directory ?
           Kernel 2.6.34 --> ubuntu Linux 10.04
           net/ipv4/netfilter --> This code contains connection
trackers, NAT helpers and
                                        kernel part for rule targets.
           net/netfilter --> This code contains conntrack helpers and
main conntrack system and
                                  conntrack subsystem.

QUES: Why do we use terms layer 5 connection trackers and layer 3
           connection trackers whereas connection is maintained only
           at layer 4 ?

           Finally after studying the code I got what I wanted.

           Layer 3 connection trackers are just for ipaddress tuple
entries and are practically
           useless if there is no layer 4 connection tracker with it.
           i.e we can say layer3 conection trackers are entry point
into the conntrack system as
           they are not dependent on incoming and outgoing interfaces.

           Layer 5 connection trackers are nothing but merely helpers
like FTP data port
           connection and which tells whether a particular connection
is related to the
           main connection or not.

           Layer 4 connection trackers functioning shows us the actual
entries in the conntrack
           table/tuple doubly linked list or in proc/net/nf_conntrack entries.

           Finally the connection is registered at the exit from POST
ROUTING HOOK.


Thanks,
A newbie into the world of firewall security mechanism.


On Mon, Jun 21, 2010 at 1:13 PM, Ninad Adi <adi.ninad@gmail.com> wrote:
> QUES:  What code is present architecturally in net/ipv4/netfilter
>            directory and what code is present architecturally in net/netfilter
>            directory ?
>
> QUES: Why do we use terms layer 5 connection trackers and layer 3
>           connection trackers whereas connection is maintained only
> at layer 4 ?
>
>
>
> Ninad.
>

      reply	other threads:[~2010-06-22  9:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-21  7:43 QUES : connection tracking Ninad Adi
2010-06-22  9:02 ` Ninad Adi [this message]

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=AANLkTimRqfY21Aymecae8ffB05PaDZ_aCuQsctdlHoTb@mail.gmail.com \
    --to=adi.ninad@gmail.com \
    --cc=netfilter@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;
as well as URLs for NNTP newsgroup(s).