Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Rob Sterenborg" <rob@sterenborg.info>
To: 'Netfilter Group' <netfilter@lists.netfilter.org>
Subject: RE: udp port 135
Date: Thu, 14 Aug 2003 07:35:33 +0200	[thread overview]
Message-ID: <001201c36225$e166d270$0401000a@sterenborg.info> (raw)
In-Reply-To: <3F3B0EF9.5040002@belfordhk.com>

> iptables -A INPUT -i $EXT_DEV -p tcp -d $EXT_DEV --dport 135 -j DROP
> iptables -A INPUT -i $EXT_DEV -p udp -d $EXT_DEV --dport 135 -j DROP
                                       ^^^^^^^^^^^

I guess the above and below is are typos ? It should be -d $EXT_IP.

> iptables -A OUTPUT -o $EXT_DEV -p tcp -d $EXT_DEV --dport 135 -j DROP
> iptables -A OUTPUT -o $EXT_DEV -p udp -d $EXT_DEV --dport 135 -j DROP

-d $EXT_IP --dport 135 should be -s $EXT_IP --sport 135.

> But with :
> 
> nmap -sU -P0 -p 135 <ext ip>,
> 
> I get a (135/udp open).

I have the same results.

> Can someone explain to me what I'm doing wrong or what
> information I have forgotten?    Does it even matter
> if the udp 135 port is open?  I'm currently in
> the process of closing all unneccessary ports
> (be it tcp or udp).

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 ?


Gr,
Rob



  reply	other threads:[~2003-08-14  5:35 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 [this message]
2003-08-14  7:54   ` cc
2003-08-14  8:38     ` Maciej Soltysiak
2003-08-14 10:12     ` Ralf Spenneberg
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='001201c36225$e166d270$0401000a@sterenborg.info' \
    --to=rob@sterenborg.info \
    --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