From: Mike <1100100@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: Port 21, 23, and 80 are open according to Shields Up at grc.com
Date: Tue, 14 Sep 2004 01:09:07 -0400 [thread overview]
Message-ID: <8ca4228204091322097d44fbc1@mail.gmail.com> (raw)
In-Reply-To: <8ca42282040913164724b70aa4@mail.gmail.com>
SOLVED.
This is pretty embarassing but I will go ahead and post it so that it
is forever archived under the "silly noobs on routers" directory.
1. I've been too lazy to get the roaring penguin dsl client working
on my routerbox. Historically, I've had trouble with making the right
data packet sizes and providing headroom for packet headers, etc.
2. So, I'm still using a simple $50 Netgear cable/dsl router to act
as my LAN's DHCP server.
3. The LAN diagram looks like: Internet --> Netgear Router --> Linux
firewall/router/gateway --> LAN clients.
4. A while back I needed to set up some video conferencing for my
boss. I wanted to make sure there were no issues with the Netgear
router so I simply turned it into a DMZ that let everything through to
the Linux routerbox.
5. Forgetful as I am, I modified the linux firewall back to its
original state once the video conferencing was completed, but never
turned off the DMZ settings on the Netgear router. That was the
entire problem. The netgear was responding and opening ports as it is
designed to do while set on DMZ.
Long story, short. I tested the linux box on its own with no Netgear
in front of it, and then also tested it with the Netgear set up as the
DHCP server, but no longer set up as a DMZ. Both tests yielded
results of complete stealth.
Where's the beer.
Mike
next prev parent reply other threads:[~2004-09-14 5:09 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
2004-09-13 21:22 ` James B. Hiller
2004-09-13 23:47 ` Mike
2004-09-14 5:09 ` Mike [this message]
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=8ca4228204091322097d44fbc1@mail.gmail.com \
--to=1100100@gmail.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 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.