From: Maximilian Wilhelm <max@rfc2324.org>
To: netfilter-devel@lists.netfilter.org
Subject: ct_sync-multigroup (was: Re: Made ct_sync running with 2.6.15.4...)
Date: Wed, 5 Apr 2006 01:37:45 +0200 [thread overview]
Message-ID: <20060404233745.GA26006@rfc2324.org> (raw)
In-Reply-To: <200603192258.27950@krak>
Am Sonntag, den 19. M?rz hub KOVACS Krisztian folgendes in die Tasten:
Hi!
[...]
> However, merging these changes to SVN would still need some more work.
> As the number of people working on ct_sync is very close to zero at the
> moment, I think that all effort should be concentrated on a single branch
> of the code. Because Harald has already put significant effort into
> providing support for active-active setups I think that we should try and
> get the linux-2.6-multigroup branch working first. Holger Eitzenberger
> was also doing some tests using that version and provided multiple fixes
> for problems he had found.
> So I don't think we should put significant amount of work into updating
> the old 2.6.10 branch. Instead, please give the -multigroup branch a try
> and provide feedback.
I wanted to give it a shot and updated most of the patches to fit to
2.6.17-rc1 (as in the git version of linus kernel from some hours ago).
A diff against the svn.netfilter.org version can be found at [42].
I'm experiencing some lack of "knowledge" about the newest *tables ->
x_tables chances and want to ask if someone allready has put some effort
into updating the patches/code.
If someone did, I would love to get/test/use the updates :)
If not, I will try to fix this myself these days, but I don't know if I
will be able to do so even though git makes things easier.
> Of course if you think you have the time to prepare
> an easily-committable patch for the linux-2.6 branch of ct_sync I'll be
> more than happy to update the SVN repository. I'm just unwilling to spend
> a significant amount of time updating that old branch.
At [42] there are still working patches for the "plain" ct_sync branch :)
(I splitted the patch in -fix and -cleanup)
[42] http://vvv.barbarossa.name/files/ct_sync/
Ciao
Max
--
Follow the white penguin.
prev parent reply other threads:[~2006-04-04 23:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-11 3:31 Made ct_sync running with 2.6.15.4 Maximilian Wilhelm
2006-03-19 21:58 ` KOVACS Krisztian
2006-03-20 14:25 ` Maximilian Wilhelm
2006-04-04 23:37 ` Maximilian Wilhelm [this message]
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=20060404233745.GA26006@rfc2324.org \
--to=max@rfc2324.org \
--cc=netfilter-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.