On Saturday 2005-October-01 21:16, Henrik Nordstrom wrote:
> On Sat, 1 Oct 2005, /dev/rob0 wrote:
> > Also, I'm not sure it would do anything at all, because there
> > cannot be that many --state NEW connections in such a short time.
> > Conntrack would call those "RELATED". I think you should try --syn,
> > not --state NEW.
>
> The syn part is correct, but not RELATED.
I know 2 things: RTFM and experience. From The Fine Manual: " ...
RELATED meaning that the packet is starting a new connection, but is
associated with an existing connection, such as an FTP data transfer,
or an ICMP error."
How is this association known to conntrack?
Experience tells me that my little ssh attack blocking ploy using -m
limit did not work if a --state RELATED,ESTABLISHED -j ACCEPT rule
preceded it, but it did/does work if the rule matches only --state
ESTABLISHED.
My inference therefrom was that the association is determined from the
IP addresses. For example if my MTA makes an outbound connection to
send mail to a remote site, and that site does an identd query, we have
a RELATED connection.
> each time a new connection is seen (unique source/destination/ports)
> the first packet is NEW, simply by the fact that the connection is
> not yet known to conntrack.
TFM does appear to contradict this opinion. I'm unable to check the
source code for the definite answer. (Unable to understand the source,
I mean.) If you have done so please do clear up these issues for us.
> conntrack calls syn retransmits on already accepted connections as
> ESTABLISHED.
Yes, since conntrack itself is protocol-agnostic it won't know or care
about TCP flags.
> RELATED is "NEW" on other traffic flows which forms a known related
> connection to a already known connection. For example the data
> channel in the FTP protocol.
Here again conntrack is protocol-agnostic. You and I know that with FTP
we talk to the server on its 21/tcp, and when we try to GET from it we
will expect the server to connect back to our port 20/tcp.
I do not believe that conntrack knows that. How it sees an FTP data
connection is probably no different from my SMTP->out in<-identd
example. It knows it has an ESTABLISHED connection between those two
addresses, but not of any protocol relationship (because in this
example there is none; identd checking is not defined in SMTP.)
> NEW is not related to syn, even if most TCP packets with state NEW is
> syn packets. Any packet from a TCP (or UDP) session not yet known to
> conntrack is NEW, even a TCP RST packet.
Sure, conntrack won't care about protocol features. But precisely how
are you suggesting the determination of RELATED state is made?
--
mail to this address is discarded unless "/dev/rob0"
or "not-spam" is in Subject: header
