From: "Alexis" <alexis@attla.net.ar>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: Filtered Port 21 somewhat open - iptables weirdness?
Date: Sat, 24 Jan 2004 11:39:46 -0300 [thread overview]
Message-ID: <000501c3e287$ea1f5490$0200000a@heretic> (raw)
In-Reply-To: 20040124014842.GA9219@localnet
try using
netstat -tupan and see wich process is using that port. if any.
----- Original Message -----
From: "Sven Riedel" <sr@gimp.org>
To: <netfilter@lists.netfilter.org>
Sent: Friday, January 23, 2004 10:48 PM
Subject: Filtered Port 21 somewhat open - iptables weirdness?
> Hi,
> one of the machines I administer to is running iptables with an input
> policy of drop, and allows only a few, selected services. Ftp is most
> definitely not among them, and there is no ftp server installed on the
> machine in question.
>
> nmap -P0 -sS reports that among the expected, port 21 is open.
> telnetting to port 21 shows indeed a successful connect:
> radagast@angmar:~>telnet <machine> 21
> Trying <ip>...
> Connected to <machine>
> Escape character is '^]'.
> ^]
> telnet> quit
>
> But it just sits there, no welcoming banner, no response to obvious
> ascii-commands.
>
> At the same time the kernel logs report that my telnet packets are being
> blocked by iptables. hping2 -A gets reset packets from that port as
> well, as if it weren't filtered, while amap shows me nothing of value.
>
> Is this maybe some ip_conntrack weirdness? I already sweeped the machine
> as well as I could and so far I came up with no indication for a rootkit
> or backdoor.
>
> Regs,
> Sven
> --
> Sven Riedel sr@gimp.org
> Liebigstr. 38
> 30163 Hannover "Python is merely Perl for those who
> prefer Pascal to C" (anon)
>
>
next prev parent reply other threads:[~2004-01-24 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-24 1:48 Filtered Port 21 somewhat open - iptables weirdness? Sven Riedel
2004-01-24 14:39 ` Alexis [this message]
2004-01-24 18:57 ` Sven Riedel
2004-01-24 19:19 ` 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='000501c3e287$ea1f5490$0200000a@heretic' \
--to=alexis@attla.net.ar \
--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 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.