From: "Dave Nebinger" <dnebinger@joat.com>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] Re: iptables example on Gentoo
Date: Tue, 06 Sep 2005 16:39:58 -0400 [thread overview]
Message-ID: <00e201c5b323$2614ece0$4501010a@jnetlab.lcl> (raw)
In-Reply-To: <loom.20050906T214946-246@post.gmane.org>
> It's not a parade, it's what old-timers do, it's how I learn.
I started that way too (being an old-timer myself ;-)
However after consuming info available on the net and buying/reading an
iptables book, I quickly came to realize that it's quite easy to shoot
yourself in the foot with iptables.
Shorewall, and many of the other alternatives, end up handling the nuances
of iptables quite nicely and take most of the bullets out of your gun, thus
protecting your feet.
> > /etc/shorewall/interfaces:
> > # Assumes you're getting IP address from dhcp server
> > net eth0 detect dhcp,routefilter,norfc1918,tcpflags
> > # Assumes you're serving dhcp to internal systems
> > loc eth1 detect dhcp,tcpflags
> how about for a static
> loc eht1 detect tcpflags <????????>
Yes, /etc/shorewall/interfaces file has excessive documentation that
explains what would go on the end.
>
> Thanks for your help. I think I've got enough here to get
> it basically working. One I make the rulesets more complex,
> I'll use shorewall generated rules and configs to see what I
> have missed.
You may be in a little trouble if you're talking about mixing shorewall &
iptables... They really don't play well together.
Shorewall (and many of the others) create custom chains to contain
individual rules of varying types. The problem is that these custom chains
tend to get intertwined with each other and trying to identify a
shorewall-based iptable rule that you want to copy to a straight iptable
implementation can be difficult.
That plus if you start shorewall it basically clears all existing chains to
load it's own info, so all firewall rules must be kept in the shorewall
files.
So you really have to pick one or the other but not both.
Dave
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-06 20:43 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 17:22 [gentoo-user] iptables example on Gentoo James
2005-09-06 17:39 ` Dave Nebinger
2005-09-06 17:53 ` Holly Bostick
2005-09-06 18:25 ` [gentoo-user] " James
2005-09-06 19:04 ` Dave Nebinger
2005-09-06 20:00 ` James
2005-09-06 20:39 ` Dave Nebinger [this message]
2005-09-07 0:02 ` gentuxx
2005-09-07 1:20 ` W.Kenworthy
2005-09-07 13:08 ` Dave Nebinger
2005-09-07 17:06 ` James
2005-09-07 18:14 ` Holly Bostick
2005-09-07 19:11 ` James
2005-09-07 19:53 ` Dave Nebinger
2005-09-08 18:14 ` James
2005-09-08 19:30 ` kashani
2005-09-07 20:09 ` Holly Bostick
2005-09-07 18:40 ` gentuxx
2005-09-07 19:29 ` James
2005-09-07 19:56 ` gentuxx
2005-09-07 20:49 ` Dave Nebinger
2005-09-07 18:48 ` Dave Nebinger
2005-09-07 22:08 ` James
2005-09-07 23:51 ` gentuxx
2005-09-08 1:23 ` James
2005-09-08 9:20 ` Neil Bothwick
2005-09-08 17:43 ` James
2005-09-08 16:19 ` James
2005-09-08 16:42 ` Dave Nebinger
2005-09-09 9:44 ` Michael Kintzios
2005-09-09 13:38 ` Dave Nebinger
2005-09-08 17:35 ` Neil Bothwick
2005-09-09 0:52 ` Jerry McBride
2005-09-07 23:52 ` Rumen Yotov
2005-09-07 18:48 ` James
2005-09-07 19:44 ` [gentoo-user] " Bryan Whitehead
2005-09-08 1:34 ` [gentoo-user] " James
2005-09-08 15:37 ` Rumen Yotov
2005-09-09 11:19 ` [gentoo-user] " Timo Boettcher
2005-09-09 14:23 ` Dave Nebinger
2005-09-10 17:04 ` Timo Boettcher
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='00e201c5b323$2614ece0$4501010a@jnetlab.lcl' \
--to=dnebinger@joat.com \
--cc=gentoo-user@lists.gentoo.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