From: /dev/rob0 <rob0@gmx.co.uk>
To: netfilter@vger.kernel.org
Subject: Re: Diskless and Firewall
Date: Thu, 1 Apr 2010 07:18:29 -0500 [thread overview]
Message-ID: <20100401121829.GF7051@cardinal> (raw)
In-Reply-To: <1270117547.3335.15.camel@khaled-laptop>
On Thu, Apr 01, 2010 at 01:25:47PM +0300, Khaled Hussein wrote:
> I am running a machine with diskless boot, it is running CentOS,
> i have problem with iptables, when i restart iptables i lost
> connection with NFS server so i lost my hard disks and machine
> become unreachable, this happened when i use DROP as default
> policy on INPUT and OUTPUT and FORWARD chains, i tried to use
> mangle table with default ACCEPT on these chains but the same,
> if i changed default policy to ACCEPT on above chains, so is
> there any way to avoid this problem
1. Point gun away from foot (and other body parts)
2. [Optional] Pull trigger
rob0 rule of thumb: If you need to ask for help to make it work, you
do not need OUTPUT filtering. Just say ACCEPT.
You cannot possibly secure a diskless boot system from possible
attack by its rootfs NFS server. The idea of firewall limits between
a system and its rootfs is ... silly. So also ACCEPT everything from
the NFS server, in INPUT.
See "man iptables" and Netfilter packet flow diagrams (Wikipedia has
one) to see why policies in the mangle table do not override your
policies in the filter table.
> ==========================
> Khaled J. Hussein
> Senior System Engineer
> Bisan Systems Ltd.
Happy April Fools Day to you, too.
> Tel: +970-22985941
> Fax: +970-22985942
> Web: www.bisan.com
> Email: khaled@bisan.com
> ==========================
>
>
>
>
> *************
> This message has been scanned for viruses and dangerous content by
> Bisan Systems Ltd MailScanner, and is believed to be clean. Bisan
> Systems Ltd does not represent that any attachment is free from
> computer viruses or defects and the user assumes all responsibility
> for any loss, damage or consequence resulting directly or
> indirectly from the use of any attachment. The information
> contained in any email does not necessarily reflect the views of
> Bisan systems or any other related entities or persons.
And many thanks for that, as well. At least it doesn't have the
offensively silly aspects of other email disclaimers.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
next prev parent reply other threads:[~2010-04-01 12:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 10:25 Diskless and Firewall Khaled Hussein
2010-04-01 12:18 ` /dev/rob0 [this message]
2010-04-01 12:32 ` Jan Engelhardt
2010-04-01 14:20 ` Roman Fiedler
2010-04-03 7:28 ` Khaled Hussein
[not found] ` <1270279479.3340.1.camel@khaled-laptop>
2010-04-06 7:41 ` Roman Fiedler
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=20100401121829.GF7051@cardinal \
--to=rob0@gmx.co.uk \
--cc=netfilter@vger.kernel.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.