From: Mike D <mdm@optonline.net>
To: Anders Fugmann <afu@fugmann.dhs.org>,
wickedsun <wickedsun@phreaker.net>,
unsubscribe@netfilter.org
Cc: netfilter <netfilter@lists.netfilter.org>
Subject: Re: Is iptables kickin' that much?
Date: Sat, 07 Sep 2002 08:46:52 -0400 [thread overview]
Message-ID: <002701c2566c$a41bb090$c7fea8c0@louie> (raw)
In-Reply-To: 3D793DE4.2060504@fugmann.dhs.org
----- Original Message -----
From: "Anders Fugmann" <afu@fugmann.dhs.org>
To: "wickedsun" <wickedsun@phreaker.net>
Cc: "netfilter" <netfilter@lists.netfilter.org>
Sent: Friday, September 06, 2002 7:44 PM
Subject: Re: Is iptables kickin' that much?
> wickedsun wrote:
> > thing to say, it works.
> Great.
>
> > Now the question is, will this work with any
> > protocol? (ftp, irc, etc).
> as of today, only ftp and IRC is implemented in the vanilla tree. POM
> may have connection tracking for other protocols.
>
> A protocol that requests something and then receives an answer is
> handled by basic connection tracking (Which is why you dont need
> connection tracking modules for e.g. http and pop, since no new
> connection are established). It is the RELATED packets that are hard to
> find.
>
> >The thing is scary me a bit. I read in your email
> > that you have to load up a FTP module (which I have compiled in the
kernel)
> > and it seems to me that it works with other protocol as well. (I was
able to
> > enable Active in DC++ without having to forward manually each ports like
I
> > used to do).
> Active DC++???? Never heard of it.
>
> >
> > This was of a huge help for the iptables newbies (including me) and
thanks.
> No problem.
>
> Regards
> Anders Fugmann
>
> --
> Author of FIAIF
> FIAIF Is An Intelligent Firewall
> http://fiaif.fugmann.dhs.org
>
>
prev parent reply other threads:[~2002-09-07 12:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-06 13:40 Is iptables kickin' that much? wickedsun
2002-09-06 23:44 ` Anders Fugmann
2002-09-07 2:12 ` wickedsun
2002-09-07 9:11 ` Anders Fugmann
2002-09-07 12:46 ` Mike D [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='002701c2566c$a41bb090$c7fea8c0@louie' \
--to=mdm@optonline.net \
--cc=afu@fugmann.dhs.org \
--cc=netfilter@lists.netfilter.org \
--cc=unsubscribe@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox