Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Raileanu Grigore <grisha@unixro.net>
To: netfilter@lists.netfilter.org
Subject: Re: port scan identification
Date: Wed, 9 Jun 2004 19:22:48 +0300	[thread overview]
Message-ID: <20040609192248.0cf52066.grisha@unixro.net> (raw)
In-Reply-To: <7EACCDBB65D37443912D80713CC1245D472828@fsnsab20.losangeles.af.mil>

On Wed, 9 Jun 2004 08:43:08 -0700 
Hudson Delbert J Contr 61 CS/SCBN <Delbert.Hudson@LOSANGELES.AF.MIL> wrote:

> Why would one care about ho many ports get scanned as long as your rulesets
> cover the ones you care about + other ports discovered as you go.
> as long as you CYA, it wong get sunburned.
> 
> ~piranha
> 
> -----Original Message-----
> From: netfilter-admin@lists.netfilter.org
> [mailto:netfilter-admin@lists.netfilter.org]On Behalf Of Raileanu
> Grigore
> Sent: Wednesday, June 09, 2004 3:32 AM
> To: netfilter@lists.netfilter.org
> Subject: Re: port scan identification
> 
> 
> On Wed, 09 Jun 2004 11:33:59 +0200
> Rakotomandimby Mihamina <rktmb.list@wanadoo.fr> wrote:
> 
> > Hello
> > 
> > I try to set correctly up my firewall ans would need your help on one
> > thing :
> > 
> > I have this rule :
> > [...]
> > iptables -A INPUT -p tcp --tcp-flags SYN,ACK,FIN,RST RST \
> > -j LOG --log-level debug --log-prefix 'p_scan_: '
> > [...]
> > 
> > and i see this when i tail the output file :
> > 
> > [...]
> > Jun  8 22:52:32 milina kernel: p_scan_: IN=ppp0 OUT= MAC=
> > SRC=81.220.171.201 DST=81.248.95.56 LEN=40 TOS=0x00 PREC=0x00 TTL=54
> > ID=45424 PROTO=TCP SPT=4391 DPT=80 WINDOW=0 RES=0x00 RST URGP=0
> > [...]
> > 
> > Well . According to me, a port scan is the action to scan _all_ the
> > ports ... why is the port scan identified as only scaning the 80th port
> > ? I mean, a port scan should not be on one port only ... isn't it ?
> > 
> > -- 
> > Rakotomandimby Mihamina Andrianifaharana
> > Tel : +33 2 38 76 43 65
> > http://stko.dyndns.info/site_principal/Members/mihamina
> > 
> > 
> 
> Try to use psd , from patch-o-matic patches.
> 
> http://www.iptables.org/downloads.html#pomng-20040302
> 
> You can create a rule like this: 
> 
> iptables -A INPUT -p ALL -m psd -j LOG --log-level DEBUG --log-prefix
> "PORTSCAN:"
> 



You can tune PSD accuracy, and other parameters.
Look at this: http://www.iptables.org/patch-o-matic/pom-base.html#pom-base-psd

-- 
Best regards,
Raileanu Grigore
mail: grisha at unixro dot net
phone: +40 742759147


  reply	other threads:[~2004-06-09 16:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-09 15:43 port scan identification Hudson Delbert J Contr 61 CS/SCBN
2004-06-09 16:22 ` Raileanu Grigore [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-09  9:33 Rakotomandimby Mihamina
2004-06-09  9:30 ` Patrick Leslie Polzer
2004-06-09 10:31 ` Raileanu Grigore
2004-06-09 11:43 ` John A. Sullivan III
2004-06-09 16:37   ` Rakotomandimby Mihamina
2004-06-09 16:51     ` John A. Sullivan III
2004-06-09 17:04       ` Antony Stone
2004-06-08 21:55 Rakotomandimby Mihamina
2004-06-10 10:37 ` Antony Stone

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=20040609192248.0cf52066.grisha@unixro.net \
    --to=grisha@unixro.net \
    --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