From: Dale <dalek@exceedtech.net>
To: "Kevin O'Gorman" <kogorman@gmail.com>, gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Wha' hoppen to firestarter?
Date: Wed, 06 Jun 2007 11:55:48 -0500 [thread overview]
Message-ID: <4666E714.9010301@exceedtech.net> (raw)
In-Reply-To: <9acccfe50706060635l5e244f0oe669a54e04e3a29d@mail.gmail.com>
Kevin O'Gorman wrote:
> On 6/5/07, Dale <dalek@exceedtech.net> wrote:
>> Kevin O'Gorman wrote:
>> > I had firestarter-1.0.3 emerged for quite some time. I hadn't really
>> > used it, but I'm a bit surprised now to find that it's interfering
>> > with normal emerges because it's got a big red "M" smacked on it.
>> >
>> > I suppose that means there's a problem with it, and it's explained in
>> > some forum or list that I don't normally get. But now I'd like a
>> > clue: what's the {prognosis, workaround, fix, alternative}. As I
>> > mentioned, I hadn't really started to use it, but I'd like to have a
>> > better firewall tool than building iptables scripts in vim.
>> >
>>
>> This is from the Gentoo dev list.
>>
>> > The upstream development for firestarter has been dead for some time
>> > (last news update Jul 31 2005). Recent changes to the netfilter code
>> > in the kernel have caused firestarter not to work (see bug #179792).
>> > That bug has a patch that fixes that particular problem but the
>> fact that
>> > upstream is dead, the several other open bugs about firestarter and
>> the
>> > fact that I no longer use it myself mean I'm masking it for removal.
>> >
>> > I feel there are several good alternatives in net-firewall/ to use as
>> > replacements for the iptables-generating aspect of firestarter. If
>> > someone
>> > would like to pick up and maintain this package, they're welcome to
>> it,
>> > otherwise, I'll remove it in thirty days.
>> >
>> > Michael Sterrett
>> > -Mr. Bones.-
>>
>> So, if you like firestarter, better say something pretty soon. ;-)
>>
>> That help any??
>>
>> Dale
>
> That helps some, but in net-firewall I'm finding a lot of unstable
> packages, and no really good idea which ones will be the best for a
> personal firewall, let alone which ones are best supported upstream so
> this doesn't happen to me again. So I'm interested in
> recommendations. What did you switch to?
>
> ++ kevin
>
I haven't crossed the switching bridge yet. I use iptables myself. I
just browse around and "steal" someone else's script or rules. :D
Dale
:-) :-) :-)
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-06-06 17:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 3:39 [gentoo-user] Wha' hoppen to firestarter? Kevin O'Gorman
2007-06-06 3:54 ` Dale
2007-06-06 4:07 ` [gentoo-user] " Ali Polatel
2007-06-06 13:35 ` [gentoo-user] " Kevin O'Gorman
2007-06-06 13:59 ` Jorge Almeida
2007-06-06 14:21 ` Dave Jones
2007-06-06 14:03 ` Ken
2007-06-06 14:10 ` John J. Foster
2007-06-06 18:47 ` Mick
2007-06-07 16:25 ` David Snider
2007-06-06 16:55 ` Dale [this message]
2007-06-14 20:19 ` Roy Wright
2007-06-15 6:52 ` Mick
2007-06-15 11:52 ` Arturo 'Buanzo' Busleiman
2007-06-06 8:07 ` Alan McKinnon
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=4666E714.9010301@exceedtech.net \
--to=dalek@exceedtech.net \
--cc=gentoo-user@lists.gentoo.org \
--cc=kogorman@gmail.com \
/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