From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Question about marking traffic.
Date: Wed, 30 Jun 2004 21:09:52 +0100 [thread overview]
Message-ID: <200406302109.52503.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <40E1368E.4040207@esi.it>
On Tuesday 29 June 2004 10:29 am, Marco Colombo wrote:
> Antony Stone wrote:
> >
> > Netfilter works at OSI layers 3 & 4, therefore it can't identify what is
> > HTTP / FTP / DNS etc - it can only guess.
>
> Not completely true, IMHO. conntrack modules look well above the TCP level
> (OSI levels make little sense for the TCP/IP protocol suite, they simply
> don't fit perfectly) otherwise they won't work. ip_conntrack_ftp does look
> at the FTP protocol, and is able to recognise incoming (data) connections
> as RELATED to the control one.
I agree with what you say, however the connection tracking helper modules such
as ip_conntrack_ftp look at such specific and restricted parts of the
application layer data that I wouldn't say they "work at that layer" in the
same sense that a proper proxy system does, for example.
> But I don't know how to use such knowledge
> to detect FTP running on non-stardard ports, particularly in matching a
> rule.
Indeed, because that's not what netfilter's knowledge of the application layer
is for. There is also a "string" match within netfilter, which does look
(completely generically) inside the payload of the packet, however it has
sufficient restrictions and caveats regarding its effective use that again I
would no consider this to mean that netfilter effectively "works" at the
application layer.
Regards,
Antony.
--
Bill Gates has personally assured the Spanish Academy that he will never allow
the upside-down question mark to disappear from Microsoft word-processing
programs, which must be reassuring for millions of Spanish-speaking people,
though just a piddling afterthought as far as he's concerned.
- Lynne Truss, "Eats, Shoots and Leaves"
Please reply to the list;
please don't CC me.
prev parent reply other threads:[~2004-06-30 20:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 16:17 Question about marking traffic mortar
2004-06-28 16:31 ` Antony Stone
2004-06-28 20:50 ` Re[2]: " mortar
2004-06-28 21:04 ` Antony Stone
2004-06-29 9:29 ` Marco Colombo
2004-06-30 20:09 ` Antony Stone [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=200406302109.52503.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--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 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.