All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike <1100100@gmail.com>
To: Jason Opperisano <opie@817west.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Port 21, 23, and 80 are open according to Shields Up at grc.com
Date: Mon, 13 Sep 2004 11:18:12 -0400	[thread overview]
Message-ID: <8ca4228204091308186fc50d59@mail.gmail.com> (raw)
In-Reply-To: <1095079786.1899.8.camel@wolfpack.ljm.dom>

Hi J,

Thanks for the guidance.
There's definitely no DNATing/PREROUTING currently set up in the
iptables firewall.  So, I guess the only thing that could explain port
21 and/or 23 is there must be an ftp daemon using those ports.

As for port 80, I wonder if it's got anything to do with Apache
running the intranet webserver inside the LAN.  I don't believe I've
got apache even installed on the routerbox.

Well, enough guessing.  I'll try some netstat research and see what
percolates to the surface.

Best regards.

Mike


On Mon, 13 Sep 2004 08:53:07 -0400, Jason Opperisano <opie@817west.com> wrote:
> 
> you need to keep in mind that if your netfilter box is performing
> MASQ/SNAT for your LAN machines--the IP being scanned by grc.com is the
> public IP of the netfilter box.
> 
> unless your doing some DNATs to machines on your LAN--you should focus
> your efforts on the netfilter machine itself.
> 
> "netstat -lntu" would be a good place to start.
> 
> i've always questioned the output of web-based scanners like grc.com;
> however, i just went to grc.com and tried it out, and achieved a
> *perfect* "TruStealth" rating...which must mean i'm super l33t like
> stevie...  :-P
> 
> -j
> 
> --
> Jason Opperisano <opie@817west.com>
> 
>


  reply	other threads:[~2004-09-13 15:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-11 18:50 MAC addresses Darren Kirby
2004-09-11 20:01 ` active
2004-09-13 15:57   ` Jose Maria Lopez
2004-09-13 20:03     ` srg
2004-09-11 21:31 ` Frank Gruellich
2004-09-11 22:23 ` Jason Opperisano
2004-09-12  0:26   ` Darren Kirby
2004-09-12  0:54     ` Jason Opperisano
2004-09-12  1:14       ` Darren Kirby
2004-09-12  2:30       ` Chris Brenton
2004-09-12 23:09         ` Darren Kirby
2004-09-11 23:09 ` Port 21, 23, and 80 are open according to Shields Up at grc.com Mike
2004-09-11 23:14   ` George Alexandru Dragoi
2004-09-12  7:38     ` Mike
2004-09-13  1:15       ` George Alexandru Dragoi
2004-09-13 12:35         ` Mike
2004-09-14  1:01           ` Nick Drage
2004-09-13 12:53   ` Jason Opperisano
2004-09-13 15:18     ` Mike [this message]
2004-09-13 21:22     ` James B. Hiller
2004-09-13 23:47       ` Mike
2004-09-14  5:09         ` Mike
2004-09-14  0:12     ` <SOLVED>Port " Mike
  -- strict thread matches above, loose matches on Subject: below --
2004-09-13 15:21 Port " Miguel Laborde
2004-09-13 15:39 ` Mike
2004-09-13 16:04 ` Jose Maria Lopez

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=8ca4228204091308186fc50d59@mail.gmail.com \
    --to=1100100@gmail.com \
    --cc=netfilter@lists.netfilter.org \
    --cc=opie@817west.com \
    /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.