Linux Netfilter discussions
 help / color / mirror / Atom feed
From: /dev/rob0 <rob0@gmx.co.uk>
To: netfilter@lists.netfilter.org
Cc: KOVACS Krisztian <hidden@balabit.hu>
Subject: Re: building a iptables-firewallcluster
Date: Mon, 22 Aug 2005 08:15:45 -0500	[thread overview]
Message-ID: <200508220815.45545.rob0@gmx.co.uk> (raw)
In-Reply-To: <200508221350.48867@nienna>

On Monday 2005-August-22 06:50, KOVACS Krisztian wrote:
> On Sunday 21 August 2005 15.37, Marc Schoechlin wrote:
> > No resonse for two weeks - am i right to assume that this
> > project is dead ?
>
>   Almost, but not completely dead.

Did we not just have 2 iptables releases last month? Slow perhaps, but 
the rumours of the death of netfilter would appear to be greatly 
exaggerated. :)

>   Unfortunately Harald does not seem to have the time necessary to
> work on this project right now, and neither do I. (Apart from this, I
> also don't have the devices necessary to do _any_ testing apart from
> compiling the code...)

I can't suggest anything to help with making more hours in the day, 
other than take a lot of westbound jet flights, and always continue 
westbound. ;) But I have a couple of ideas for the device shortage:

1. Skip surfing / dumpster diving
   Old "useless" machines are excellent netfilterers.
2. User-mode Linux
   Set up an entire network on one physical machine.
-- 
    mail to this address is discarded unless "/dev/rob0"
    or "not-spam" is in Subject: header


  reply	other threads:[~2005-08-22 13:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-02 12:03 building a iptables-firewallcluster Marc Schoechlin
2005-08-21 13:37 ` Marc Schoechlin
2005-08-22  4:10   ` Grant Taylor
2005-08-22 11:50   ` KOVACS Krisztian
2005-08-22 13:15     ` /dev/rob0 [this message]
2005-08-22 14:42       ` KOVACS Krisztian
2005-08-22 18:29       ` Taylor, Grant
2005-08-22 18:26     ` Taylor, Grant

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=200508220815.45545.rob0@gmx.co.uk \
    --to=rob0@gmx.co.uk \
    --cc=hidden@balabit.hu \
    --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