From: Maciej Soltysiak <maciej@soltysiak.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] How to close default open firewall ports in 3.3.8
Date: Wed, 10 Oct 2012 19:40:15 +0200 [thread overview]
Message-ID: <CAMZR1YBj6+Zv09YkkoQskGHaQx9dHPcr5W+LSBneHyN2RPtqwg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4srS0ABSC8t4Uydc+H-F2yuzg8MH3QeGjeZVhhgTa1oA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1952 bytes --]
This looks like an FAQ item :-) I'll have a look at the wiki.
On Oct 10, 2012 7:22 PM, "Dave Taht" <dave.taht@gmail.com> wrote:
> Several ports are open, but filtered, using various means. Does this
> tool not show filtered?
>
> For example, rsync and ssh are enabled but the default settings in
> /etc/xinetd.conf prohibit access via any but your internal private
> ips.
>
> Telnet and ftp ports (not services) are enabled, but are there to
> trigger sensors to disable other services in the advent of an attack
> from inside or outside of your firewall.
>
> You can close ports more fully to the outside world via the gui,
> editing /etc/config/firewall and/or do finer grained access control
> via /etc/xinetd.conf and /etc/xinetd.d/
>
> The web port (80) defaults open, the web configuration port (81) does
> not. The intent here is to enable you to put up your own local web
> pages.
>
> See the onboard and wiki documentation for more details.
>
> Thx for trying cerowrt!
>
> On Wed, Oct 10, 2012 at 8:44 AM, Shannon Kendrick
> <shannon@kendrickonline.org> wrote:
> > What's the best resource for learning how to configure the firewall to
> close the ports that are open by default? I installed 3.3.8-26 "sugarland"
> into a brand new WNDR3800 to be used as my home router, and I immediately
> ran ShieldsUp!! (grc.com) and noticed open ports. However, I'm at a loss
> as to how to close them.
> > Thanks,
> > Shannon Kendrick
> > _______________________________________________
> > Cerowrt-devel mailing list
> > Cerowrt-devel@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt:
> http://www.teklibre.com/cerowrt/subscribe.html
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 2777 bytes --]
next prev parent reply other threads:[~2012-10-10 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 15:44 Shannon Kendrick
2012-10-10 17:22 ` Dave Taht
2012-10-10 17:40 ` Maciej Soltysiak [this message]
2012-10-13 2:22 ` Shannon Kendrick
2012-10-13 4:01 ` Kai Yang
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMZR1YBj6+Zv09YkkoQskGHaQx9dHPcr5W+LSBneHyN2RPtqwg@mail.gmail.com \
--to=maciej@soltysiak.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox