Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "David F. Strauch" <dstrauch@cyberlink.com>
To: netfilter@lists.netfilter.org
Subject: open ports 25/tcp and 110/tcp
Date: Wed, 3 Dec 2003 16:46:31 -0600	[thread overview]
Message-ID: <002101c3b9ef$53e5d780$0201a8c0@OurPC> (raw)

Hello All,

I've been working with giptables firewall and have run into a big issue.
Although my script seems to be correct namp is finding ports 25/tcp and
110/tcp open.  To start troubleshooting this problem I've commented
everything out and stripped down the ruleset to just the default DROP
policy.  Yet nmap -sT -F -P0 -0 xx.xx.xx.xx still returns 25/tcp and 110/tcp
as open!

Now I'm starting to think that iptables is broken. I've built iptables with
grsecurity-1.9.12 and iptables1.2.8 with a plain vanilla kernel 2.4.22   Is
anyone aware of any issues?

Dave




             reply	other threads:[~2003-12-03 22:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-03 22:46 David F. Strauch [this message]
2003-12-03 23:01 ` open ports 25/tcp and 110/tcp Antony Stone
2003-12-03 23:15   ` David F. Strauch
2003-12-03 23:23     ` Antony Stone
2003-12-03 23:34   ` David F. Strauch
     [not found]   ` <002201c3b9f5$c7ee11a0$0201a8c0@OurPC>
2003-12-03 23:39     ` Antony Stone
2003-12-03 23:58       ` David F. Strauch
2003-12-04  0:08         ` Antony Stone
2003-12-04  0:14           ` Michael Gale
2003-12-04  0:28             ` Jeffrey Laramie
2003-12-04  0:37               ` Michael Gale
2003-12-04  1:14                 ` Jeffrey Laramie
2003-12-04  0:39               ` Antony Stone
2003-12-04  1:27                 ` Jeffrey Laramie
2003-12-04  3:46                 ` David F. Strauch
2003-12-04  0:11         ` Jeffrey Laramie
2003-12-03 23:08 ` Rob Sterenborg
2003-12-03 23:17   ` 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='002101c3b9ef$53e5d780$0201a8c0@OurPC' \
    --to=dstrauch@cyberlink.com \
    --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