From: Marc MERLIN <marc@merlins.org>
To: cerowrt-users@lists.bufferbloat.net
Subject: [Cerowrt-users] firewalling suggestion
Date: Sun, 25 Nov 2012 12:31:42 -0800 [thread overview]
Message-ID: <20121125203142.GB24680@merlins.org> (raw)
Howdy,
I like having my ssh port available on the internet side so that I can get
into my router from there if needed.
To do so, I had to edit /etc/xinetd.conf which prevents any connection from
outside to a bunch of services, including dropbear/ssh.
In turn, this enables a bunch of services to the internet, I'm not looking
at enabling, so I firewalled them with iptables.
But this brings the question: can the default config be fixed accordingly?
Firewalling with inetd and hosts.allow is so early 1990's :)
I changed the firewalling config as such:
config rule
option src 'wan'
option proto 'tcp udp'
option target 'ACCEPT'
option name 'allow outside mgmt'
option dest_port '22 81 443'
config rule
option src 'wan'
option proto 'tcp udp'
option name 'blockconfig'
option target 'DROP'
option dest_port '1-65535'
config rule
option src 'guest'
option proto 'tcp udp'
option dest_port '80 81 137 138 139 445'
option name 'blockconfig2'
option target 'DROP'
This isn't one size fits all, but changing the default to allow all from xinetd,
block all from wan, except a few services, is probably a good idea, no?
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next reply other threads:[~2012-11-25 20:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-25 20:31 Marc MERLIN [this message]
2012-11-25 20:48 ` Dave Taht
2012-11-25 20:49 ` Marc MERLIN
2012-11-25 22:41 ` Dave Taht
2012-11-25 22:56 ` Marc MERLIN
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=20121125203142.GB24680@merlins.org \
--to=marc@merlins.org \
--cc=cerowrt-users@lists.bufferbloat.net \
/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