Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Stefanos Harhalakis <v13@it.teithe.gr>
To: netfilter@lists.netfilter.org
Subject: nat/conntrack module names
Date: Wed, 3 Sep 2003 23:54:55 +0300	[thread overview]
Message-ID: <200309032354.56137.v13@it.teithe.gr> (raw)

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 587 bytes --]

 In short....

I believe that the modules named ip_nat_* (like ip_nat_ftp) should be named 
ip_conntrack_* (ip_conntrack_ftp). "nat" is not correct because they are used 
in cases where nat is not performed. 

For example, firewalls that want to allow ftp sessions will load the 
ip_nat_ftp module no matter if they are doing nat or not... Since this has to 
do with connection tracking their name should contain 'conntrack' instead of 
'nat'.

Sorry if this is a known issue...

TIA

<<V13>>

p.s. Please CC any reply to me too since I'm not subscribed to the list...

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2003-09-03 20:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200309032354.56137.v13@it.teithe.gr \
    --to=v13@it.teithe.gr \
    --cc=netfilter@lists.netfilter.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