From: Djalma Fadel Junior <dfadel@ferasoft.com.br>
To: netfilter@lists.netfilter.org
Subject: Re: Possible conntrack problem
Date: Sat, 3 Jun 2006 19:04:11 -0300 [thread overview]
Message-ID: <20060603190411.7108369a@phadell.org> (raw)
In-Reply-To: <20060602_184642_048181.zottmann@ig.com.br>
On Fri, 2 Jun 2006 15:46:42 -0300
zottmann <zottmann@ig.com.br> wrote:
> Hi !!
>
> We are seeing a lot of packets being blocked at our firewall, coming from
> our webserver, port 80, going to the several hosts at the Internet, at high
> ports, with both SET and ACK set.
>
> It seems that these packets are answers from our webserver to connections
> estabilished to it, and, for some reason, their state is not being kept.
>
> How can I track this problem?
>
> We are using iptables 1.3.1, kernel 2.6.11.12, in a Fedora Core 3 machine.
I'm facing the same problem on port 3128.
I guess that may be some kind of virus/worm that use ports like 80,1080,8080,3128 for spam purpose. They use any HTTP port to connect on mail servers and send bulk email.
My conntrack table was getting flooded and I set 2 rules, but the problem keeps on.
iptables -t nat -I PREROUTING -p tcp ! --syn -m state --state NEW -j DROP
iptables -I FORWARD -d ${MY_NETWORK} -p tcp --dport 3128 -m state --state NEW -j DROP
any effective solution would be appreciated.
thanks
--
Djalma Fadel Junior
Diretor Técnico
Ferasoft Corporation Ltda
+55 (19) 3542-3490
dfadel@ferasoft.com.br
next prev parent reply other threads:[~2006-06-03 22:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 18:46 Possible conntrack problem zottmann
2006-06-03 22:04 ` Djalma Fadel Junior [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-03 18:53 zottmann
2006-06-01 11:56 zottmann
2006-06-01 12:04 ` Sietse van Zanen
2006-06-01 12:15 ` Justin Schoeman
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=20060603190411.7108369a@phadell.org \
--to=dfadel@ferasoft.com.br \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox