From: "Landon Chelf" <landonc@starrobbins.com>
To: netfilter@lists.netfilter.org
Subject: RE: Broken ftp through iptables
Date: Tue, 26 Aug 2003 11:42:02 -0400 [thread overview]
Message-ID: <000a01c36be8$9b990f70$6901a8c0@Station13> (raw)
In-Reply-To: <3F4B7D1A.2010408@nucdc.org>
Thanks but it is loaded from what I can tell. Below is the iptables
stuff of an lsmod
Module Size Used by Not tainted
ip_conntrack_ftp 5296 0 (unused)
ip_conntrack 26976 1 [ip_conntrack_ftp]
iptable_filter 2412 1 (autoclean)
ip_tables 15096 1 [iptable_filter]
-----Original Message-----
From: Jamie Pratt [mailto:jamie@nucdc.org]
Sent: Tuesday, August 26, 2003 11:31 AM
To: Landon Chelf
Subject: Re: Broken ftp through iptables
hi - do you have the ip_conntrack_ftp module loaded on the server?
(lsmod command will show you all the modules that are currently
loaded).. - if not, try putting 'insmod ip_conntrack_ftp' in your
script.. (near the top obviously ;-)
jamie
Landon Chelf wrote:
> Hello,
>
> I've ran into a recent problem both on rh8 and rh9 using iptables.
> I've setup my firewall to drop everything incomming and forward and am
> only allowing certain ports to be open. I've opened ftp (port 21 tcp)
> and I can connect via FTP from one machine and authenticate, but when
> I issue my first command like "ls" for instance the connection locks
> up and won't do anything. Is there a way to fix this?
>
> Landon
>
>
>
>
next parent reply other threads:[~2003-08-26 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F4B7D1A.2010408@nucdc.org>
2003-08-26 15:42 ` Landon Chelf [this message]
2003-08-26 16:05 ` Broken ftp through iptables Julian Gomez
2003-08-26 16:18 ` Peter Marshall
2003-08-26 22:29 ` Alistair Tonner
2003-08-27 2:43 Josh.Berry
-- strict thread matches above, loose matches on Subject: below --
2003-08-26 15:21 Landon Chelf
2003-08-26 15:59 ` Peter Marshall
2003-08-26 16:14 ` Landon Chelf
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='000a01c36be8$9b990f70$6901a8c0@Station13' \
--to=landonc@starrobbins.com \
--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