From: Ralf Spenneberg <lists@spenneberg.org>
To: cc <cc@belfordhk.com>
Cc: Rob Sterenborg <rob@sterenborg.info>,
'Netfilter Group' <netfilter@lists.netfilter.org>
Subject: Re: udp port 135
Date: 14 Aug 2003 12:12:05 +0200 [thread overview]
Message-ID: <1060855924.1717.75.camel@kermit> (raw)
In-Reply-To: <3F3B404A.7060400@belfordhk.com>
Am Don, 2003-08-14 um 09.54 schrieb cc:
> Rob Sterenborg wrote:
> >
> > No. I am interested too in why udp shows "open" from a foreign host,
> > while tcp shows filtered.
> > How can I check if an udp port is really closed/filtered or opened ?
>
> I'm completely stumped on this issue.
There are three possible responses to an udp probe as nmap sends it:
1. Port is closed. OS hopefully sends an ICMP-Port-Unreachable
2. Port is open. Either the application sends an error via UDP or does
not answer at all
3. Port is filtered. No response since the original packet is dropped.
When you compare 2 and 3, you will see that nmap cannot distinguish
between an open and an filtered port. Thus nmap will mark all (drop)
filtered and open ports as open and will recognize only closed and
rejected ports as closed.
Cheers,
Ralf
--
Ralf Spenneberg
RHCE, RHCX
Book: Intrusion Detection für Linux Server http://www.spenneberg.com
IPsec-Howto http://www.ipsec-howto.org
Honeynet Project Mirror: http://honeynet.spenneberg.org
next prev parent reply other threads:[~2003-08-14 10:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 4:24 udp port 135 cc
2003-08-14 5:35 ` Rob Sterenborg
2003-08-14 7:54 ` cc
2003-08-14 8:38 ` Maciej Soltysiak
2003-08-14 10:12 ` Ralf Spenneberg [this message]
2003-08-14 7:16 ` Maciej Soltysiak
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=1060855924.1717.75.camel@kermit \
--to=lists@spenneberg.org \
--cc=cc@belfordhk.com \
--cc=netfilter@lists.netfilter.org \
--cc=rob@sterenborg.info \
/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.