From: Patrick McHardy <kaber@trash.net>
To: Amin Azez <azez@ufomechanic.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: does ipset conflict with ipsec SuSE kernel patch?
Date: Sat, 08 Jul 2006 05:06:03 +0200 [thread overview]
Message-ID: <44AF211B.1040504@trash.net> (raw)
In-Reply-To: <44AE63F1.1020707@ufomechanic.net>
Amin Azez wrote:
>>Does this mean IPsec conflicts with ipsets? The comment of SuSE kernel
>>patch said the patches are from netfilter team, and the ipsets are also
>>from netfilter.org. Since they are both belong to netfilter team, is
>>there any way to resolve the conflict?
>>
>>Please let me know if you need more information. Thanks for your time.
As far as I know SuSE chose to use an extremly beta (and horribly outdated
and incompatible to what we have today) version of my IPsec patches.
They have lots of known bugs, and SuSE certainly made a poor decision
(after buggering me for weeks) here. Please take it on with their
support or use the vanilla kernel.
next prev parent reply other threads:[~2006-07-08 3:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 21:05 does ipset conflict with ipsec SuSE kernel patch? Hung Lin
2006-07-07 13:38 ` Amin Azez
2006-07-08 3:06 ` Patrick McHardy [this message]
2006-07-09 15:34 ` Jozsef Kadlecsik
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=44AF211B.1040504@trash.net \
--to=kaber@trash.net \
--cc=azez@ufomechanic.net \
--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.