From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] firehol + gentoo 3.6.11 kernel....
Date: Tue, 19 Feb 2013 11:12:09 +0700 [thread overview]
Message-ID: <CAA2qdGVbRr_02e2ft44bKW+WjPSPg_Tmj-NJJ71+vNPMy4vAXA@mail.gmail.com> (raw)
In-Reply-To: <CA+czFiCSWSFCgE5BQ2bH6uKEozPg=yMetjj4cBGomYZQJW35rQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
On Feb 19, 2013 9:10 AM, "Michael Mol" <mikemol@gmail.com> wrote:
>
> On Feb 18, 2013 8:35 PM, "Tamer Higazi" <th982a@googlemail.com> wrote:
> >
> > hi people!
> > I have used all the time "firehol" (gentoo sources 3.3.8) to make my
> > firewall rules. After kernel 3.4.x I can't make use of it any more.
> >
> > Has anyone of you got firehol running on a genoo system with a 3.4.x
> > kernel above to run?
> > And if not, can you adivse me something similiar to build linux firewall
> > rules ?!
> >
> > For a short reply I would thank you.
> >
> >
> >
> > Tamer
> >
>
> I use a fork of firehol, based on Phil Whineray's IPv6 patches...but on
Debian. I'll see about getting it working on Gentoo, and let you know.
Perhaps I can get it (or Phil's version) into the tree.
Pah! Real Men™ hack iptables rules directly with their hands, not using
baby walkers...
LOL, just kidding. What's the firehol fork's name in Debian? I'm interested
to see how it looks like now...
(About 4 years ago, these tools are so dismal I created one myself, failed
miserably, and just code the rules up by hand.)
Rgds,
--
[-- Attachment #2: Type: text/html, Size: 1513 bytes --]
next prev parent reply other threads:[~2013-02-19 4:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 1:34 [gentoo-user] firehol + gentoo 3.6.11 kernel Tamer Higazi
2013-02-19 1:51 ` Bruce Hill
2013-02-19 2:09 ` Michael Mol
2013-02-19 4:12 ` Pandu Poluan [this message]
2013-02-19 16:32 ` Michael Mol
2013-02-19 4:16 ` Alon Bar-Lev
2013-02-19 16:20 ` [gentoo-user] " James
2013-02-19 20:12 ` Mick
2013-02-28 3:52 ` [gentoo-user] " Tamer Higazi
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=CAA2qdGVbRr_02e2ft44bKW+WjPSPg_Tmj-NJJ71+vNPMy4vAXA@mail.gmail.com \
--to=pandu@poluan.info \
--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