From: ro0ot <ro0ot@phreaker.net>
To: Paul Annesley <paul.annesley@gmail.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: lots of tcp port 445 traffic
Date: Fri, 10 Dec 2004 21:52:42 +0800 [thread overview]
Message-ID: <41B9AA2A.4020804@phreaker.net> (raw)
In-Reply-To: <99fb058804120913377e13904a@mail.gmail.com>
I include these rules below and it helps: -
iptables -t nat -A PREROUTING -p tcp --dport 135 -j DROP
iptables -t nat -A PREROUTING -p tcp --dport 445 -j DROP
Paul Annesley wrote:
>>>iptables -I cus2jarwan -p tcp --dport 445 -j REJECT --reject-with tcp-reset
>>>
>>>or
>>>
>>>iptables -I cus2jarwan -p tcp --dport 445 -j DROP
>>>
>>>
>>>
>>You definately don't want to use -J REJECT - this will do more harm
>>than good, as it will be generating an ICMP unreachable message for
>>each port 445 packet.
>>
>>
>
>My mistake - I didn't notice you were using "--reject-with tcp-reset".
>Pretty sure you'd be better off with DROP anyway.
>
>Regards,
>Paul
>
>
>
>
prev parent reply other threads:[~2004-12-10 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 16:54 lots of tcp port 445 traffic ro0ot
2004-12-06 22:56 ` Paul Annesley
2004-12-09 21:17 ` Jose Maria Lopez
2004-12-09 21:37 ` Paul Annesley
2004-12-10 13:52 ` ro0ot [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=41B9AA2A.4020804@phreaker.net \
--to=ro0ot@phreaker.net \
--cc=netfilter@lists.netfilter.org \
--cc=paul.annesley@gmail.com \
/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