Linux Netfilter discussions
 help / color / mirror / Atom feed
From: cldavis@speakeasy.net
To: Jason Williams <jwilliams@courtesymortgage.com>,
	netfilter@lists.netfilter.org
Subject: Re: Final IPTables script (hopefully)
Date: Wed, 29 Dec 2004 02:20:03 +0000	[thread overview]
Message-ID: <W856975398238081104286803@webmail1> (raw)


> -----Original Message-----
> From: Jason Williams [mailto:jwilliams@courtesymortgage.com]
> Sent: Tuesday, December 28, 2004 11:48 PM
> To: netfilter@lists.netfilter.org
> Subject: Final IPTables script (hopefully)
>
> Hello everyone.
>
> Back from a much needed vacation today and started back at IPTables. After
> reading up on a lot of documentation and taking some very good advice from
> this list, here is what i have come up with, in hopes of getting it right,
> to act as a personal firewall for my home network.
>
[...]
> $IPTABLES -P INPUT DROP
> $IPTABLES -P OUTPUT DROP
> $IPTABLES -P FORWARD DROP
[...]
> $IPTABLES -A OUTPUT -j ACCEPT
>
[...]
Looks pretty good...except you have the policy for OUTPUT set to DROP, but you are allowing all unmatched traffic on OUTPUT to pass through.  If you want to allow all traffic outbound you may want to eliminate the line: $IPTABLES -A OUTPUT -j ACCEPT and change your OUTPUT policy to ACCEPT.

If you want to really tighten the belt so to speak and leave the policy for OUTPUT to drop, you might want to consider using nmap, strace, and log all dropped packets for a while and set rules specifically for outbound traffic.

I say looks good otherwise...if you plan on admining the box via remote interfaces make sure to leave yourself a way in :)

~Regards,
Chris




             reply	other threads:[~2004-12-29  2:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-29  2:20 cldavis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-12-28 23:48 Final IPTables script (hopefully) Jason Williams
2004-12-29 20:07 ` Jason Opperisano

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=W856975398238081104286803@webmail1 \
    --to=cldavis@speakeasy.net \
    --cc=jwilliams@courtesymortgage.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox