From: Anders Fugmann <afu@fugmann.dhs.org>
To: wickedsun <wickedsun@phreaker.net>
Cc: netfilter@lists.netfilter.org
Subject: Re: ftp server issue, trying to DL 1.2.7a
Date: Sat, 07 Sep 2002 15:18:01 +0200 [thread overview]
Message-ID: <3D79FC89.9070001@fugmann.dhs.org> (raw)
In-Reply-To: 3D79F330.000001.00620@athlon1000
wickedsun wrote:
> FTP Issues, round 2.
>
>
> With further testing, I've noticed that it doesnt quite work. For some
> unknown reason, it *seems* to work on port 21, but doesnt on other
Seems or does?
> ports. From what I understood in your post, you said it would work on
> any port. (FTP, of course).
>
No. The ftp connection tracking module only monitors on port 21. Because
it has to examine all packets beeing send though, it would simple be too
much work to monitor any connection made. If you want it to monitor
other ports also, you can compile the ftp connection tracking as a
module, and then use:
modprobe ip_conntrack_ftp 21,5006
to let it listen on ports 21 and 5006.
I do not know if there is any way to make this work with
ftp_connection_tracking statically compiled in the kernel.
Regards
Anders Fugmann
--
Author of FIAIF
FIAIF Is An Intelligent Firewall
http://fiaif.fugmann.dhs.org
next prev parent reply other threads:[~2002-09-07 13:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-05 17:29 ftp server issue, trying to DL 1.2.7a Rob
2002-09-05 18:30 ` Rob
2002-09-06 1:50 ` Fabrice MARIE
2002-09-05 18:32 ` Antony Stone
2002-09-05 22:00 ` wickedsun
2002-09-05 18:33 ` Ramin Alidousti
2002-09-05 19:57 ` Alistair Tonner
2002-09-06 9:39 ` Anders Fugmann
2002-09-07 12:38 ` wickedsun
2002-09-07 13:18 ` Anders Fugmann [this message]
2002-09-07 15:33 ` wickedsun
2002-09-07 15:40 ` Alistair Tonner
[not found] <002901c2551c$f5dd4700$3200a8c0@fcol.com>
2002-09-05 21:34 ` Rob
2002-09-05 22:37 ` R. Sterenborg
2002-09-06 3:49 ` Rob
2002-09-06 6:05 ` R. Sterenborg
-- strict thread matches above, loose matches on Subject: below --
2002-09-10 3:51 Rob
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=3D79FC89.9070001@fugmann.dhs.org \
--to=afu@fugmann.dhs.org \
--cc=netfilter@lists.netfilter.org \
--cc=wickedsun@phreaker.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.