Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Eric Leblond <eric@regit.org>
To: Britt Tabor <btabor@edgeaccess.net>
Cc: netfilter@lists.netfilter.org
Subject: Re: ip_conntrack_ftp
Date: Tue, 14 Oct 2003 18:08:22 +0200	[thread overview]
Message-ID: <1066147702.1692.38.camel@porky> (raw)
In-Reply-To: <BDF3100EBB9E3A47B84F816A10D9A4E5A8E3@eai-exchange.edgeaccess.net>

[-- Attachment #1: Type: text/plain, Size: 824 bytes --]

Le lun 13/10/2003 à 23:22, Britt Tabor a écrit :
> lsmod:
> bash-2.05# lsmod
> Module                  Size  Used by
> ip_conntrack_ftp        3856   0  (unused)
> vhub                    9664   0  (unused)
> iptable_nat            14432   1  (autoclean)
> ip_conntrack           16656   2  (autoclean) [ip_conntrack_ftp iptable_nat]
> iptable_filter          1760   1  (autoclean)
> via-rhine              12768   1 
> eepro100               18432   1 
> mii                     2160   0  [via-rhine eepro100]
> pcmcia_core            40608   0 
> doc                   146464   1
> 
> why does my ftp data still get block/dropped ???
the NAT is the problem the module "ip_nat_ftp" is not here to correctly
nat connection.

BR,
-- 
Eric Leblond
Nufw, Now User Filtering Works (http://www.nufw.org)

[-- Attachment #2: Ceci est une partie de message numériquement signée. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-10-14 16:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-13 21:22 ip_conntrack_ftp Britt Tabor
2003-10-14 16:08 ` Eric Leblond [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-06-24  8:01 ip_conntrack_ftp Nicolas Olivier
2005-06-24  8:10 ` ip_conntrack_ftp Nicolas Olivier
2002-10-07 12:09 ip_conntrack_ftp vlad f kropachew
2002-10-10  1:40 ` ip_conntrack_ftp Alistair Tonner

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=1066147702.1692.38.camel@porky \
    --to=eric@regit.org \
    --cc=btabor@edgeaccess.net \
    --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