From: "J. Bakshi" <joydeep@infoservices.in>
To: netfilter@vger.kernel.org
Subject: Re: How to create rule from log file information ?
Date: Wed, 27 Jan 2010 08:34:26 +0530 [thread overview]
Message-ID: <4B5FAD3A.6050704@infoservices.in> (raw)
In-Reply-To: <4B5E110B.90507@chello.at>
Mart Frauenlob wrote:
> On 25.01.2010 19:49, netfilter-owner@vger.kernel.org wrote:
>
>> On 25/Jan/10 18:32, J. Bakshi wrote:
>>
>>> I have collected the iptables log against nmap scan. Like
>>>
>>> [omitted almost identical log lines]
>>>
>>> Can I make rule-set to prevent the above scan from the info collected
>>> at the log ?
>>> Kindly enlighten me. Then I can make more rule sets from the log.
>>>
>> I'm not an nmap expert, but AFAIK nmap is designed to avoid just that. I
>> have installed some logging iptables rules, similar to the ones in your
>> previous message (from Arno's iptables scripts, IIRC) and sometimes some
>> of them fire, presumably because inappropriate flags had been given to
>> nmap.
>>
>> To recognize a scan, one may look at almost simultaneous TCP syn
>> occurring to several nearby ports/ addresses, and not followed by an
>> ack. This would require specific connection tracking code that I've
>> never heard about. At any rate, you /have/ to respond to syn requests,
>> because they may be legit. You may recognize that they were scans by
>> analyzing the logs some time later, presumably for banning the relevant
>> IPs from further accessing your server...
>>
>>
>
> I have not tried them yet, but there is are extensions in
> xtables-addons. Might worth trying:
>
>
Thanks for the info. Is there anyone already working with the module ?
Please share your experience.
Thanks
--
জয়দীপ বক্সী
prev parent reply other threads:[~2010-01-27 3:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 17:32 How to create rule from log file information ? J. Bakshi
2010-01-25 18:48 ` Alessandro Vesely
2010-01-25 21:45 ` Mart Frauenlob
2010-01-27 3:04 ` J. Bakshi [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=4B5FAD3A.6050704@infoservices.in \
--to=joydeep@infoservices.in \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox