All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Feldmann <feldmann_markus@gmx.de>
To: netfilter@vger.kernel.org
Subject: Re: iptables NEW or SYN
Date: Fri, 14 May 2010 02:06:34 +0200	[thread overview]
Message-ID: <hsi46a$sro$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTilx7Gimy8RwVszEx1ijkR4mx2Q70HKJO72fAhTK@mail.gmail.com>

Thanks for your help,

I changed this at this afternoon today, because otherwise my server is
not reachable. I changed line 132 and 133 from "state NEW" to the
iptables argument "--syn".

I have no idea why NEW does not work but --syn.

@Curby
The packets will not dropped in the INPUT chain, see the LOG of my friend.
https://debianforum.de/forum/pastebin.php?mode=view&s=34615
All packets will only dropped in the attacksinput chain. I made this log
with <grep SRC=84.141.159.142 /var/log/syslog>, so it contains all
dropped packets from my friend.

When the packets with DPORT=80,443 goes back to the INPUT chain it will
be ACCEPTED, see line 241 to 247. But as i said the packets will only be
dropped in my atttacksinput chain and i don't know why.

The first dropped packet of my friend has the DPT=443 (Redirection from
80 to 443) and SYN flag set with TCP protocol. So i asume that the first
packets with DPORT=80 were accepted. The next packet (singular) with
DPT=443 was dropped at <attacksinput(NEW,INVALID)>, so it went over the
rule in line 133. Line 133 says clearly to catch all NEW packets with
DPT=443. Because it didn't so, the packet was not NEW, and because it
was catched by <attacksinput(NEW,INVALID)>, it has to be INVALID !

Question, is a packet still marked as NEW, after it is redirected from
80 to 443 ???

regards Markus



  parent reply	other threads:[~2010-05-14  0:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-13 17:08 iptables NEW or SYN Markus Feldmann
2010-05-13 17:18 ` Jan Engelhardt
2010-05-13 17:42   ` Markus Feldmann
2010-05-13 18:00   ` Markus Feldmann
2010-05-13 18:09     ` Markus Feldmann
2010-05-13 20:09       ` Pascal Hambourg
2010-05-13 20:55         ` Markus Feldmann
2010-05-13 18:05   ` Markus Feldmann
2010-05-13 18:19     ` Curby
2010-05-13 18:45       ` Markus Feldmann
2010-05-13 19:23         ` Mistick Levi
2010-05-13 21:45           ` Markus Feldmann
2010-05-13 22:46             ` Curby
2010-05-14  0:06           ` Markus Feldmann [this message]
2010-05-14  0:23             ` Markus Feldmann
2010-05-14  2:19             ` Markus Feldmann
2010-05-14  6:41             ` Jan Engelhardt
2010-05-14 12:16               ` Markus Feldmann
2010-05-14  5:08         ` Mart Frauenlob
  -- strict thread matches above, loose matches on Subject: below --
2010-05-13 13:17 Markus Feldmann
2010-05-13 15:21 ` ratheesh k

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='hsi46a$sro$1@dough.gmane.org' \
    --to=feldmann_markus@gmx.de \
    --cc=netfilter@vger.kernel.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.