From: Roberto Nibali <ratz@drugphish.ch>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@lists.netfilter.org,
Henrik Nordstrom <henrik@henriknordstrom.net>,
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>,
Jan Engelhardt <jengelh@linux01.gwdg.de>
Subject: Re: [PATCH 1/1] Re: dangerous? Setting mark in nat table
Date: Thu, 15 Mar 2007 14:12:29 +0100 [thread overview]
Message-ID: <45F9463D.6050502@drugphish.ch> (raw)
In-Reply-To: <45F87F09.2070009@trash.net>
>>> just spewing ideas at this time. As Patrick I do not consider the core
>>> iptables worth the effort of such redesign and if redesigning stuff then
>>> something significantly better should be done. nf-HiPAC is one possible
>>> alternative where a lot is done much smarter even if communication
>>> between the projects is pretty distant at the moment.
>>
>> Speaking of HiPAC, when is it going to be merged? IIRC the merge was
>> discussed at the netfilter workshop 2005 with the goal to merge it in
>> 2.6.16. Has this decision been overturned/revised/forgotten or was
>> the report I read about that netfilter workshop inaccurate?
>
> Unfortunately the discussion pretty much came to a halt over a year
> ago because of some disagreements. I still consider merging it a
> good idea, but since there is no progress in this area I will start
> working on a netlink based iptables replacement myself in the next
> months.
Cough ... could we guys over at ../ipv4/ipvs/ synchronise with your
ideas? I've once started a port of IPVS to the netlink framework
together with Thomas Graf, but stopped the project because I didn't find
enough time. I'll be offline for at least one year soon but my fellow
hackers (Horms at the moment) over at IPVS sure would like to combine
efforts; maybe we can even completely integrate IPVS into the new (fast
and memory-efficient like nf-hipac) netfilter framework and share the
netlink code in user space with regards to iptables and ipvsadm.
Best regards,
Roberto Nibali, ratz
--
echo
'[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq' | dc
next prev parent reply other threads:[~2007-03-15 13:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 15:25 dangerous? Setting mark in nat table Amin Azez
2007-03-13 15:36 ` Jan Engelhardt
2007-03-13 16:12 ` Amin Azez
2007-03-13 16:18 ` Jan Engelhardt
2007-03-14 10:35 ` Henrik Nordstrom
2007-03-14 11:02 ` Patrick McHardy
2007-03-14 12:43 ` Henrik Nordstrom
2007-03-14 12:52 ` [PATCH 1/1] " Amin Azez
2007-03-14 13:08 ` Patrick McHardy
2007-03-14 13:21 ` Jozsef Kadlecsik
2007-03-14 14:09 ` Jozsef Kadlecsik
2007-03-14 20:35 ` Patrick McHardy
2007-03-14 20:45 ` Henrik Nordstrom
2007-03-14 20:48 ` Jan Engelhardt
2007-03-14 22:21 ` Henrik Nordstrom
2007-03-14 22:58 ` Carl-Daniel Hailfinger
2007-03-14 23:02 ` Patrick McHardy
2007-03-14 23:12 ` Jan Engelhardt
2007-03-14 23:15 ` Patrick McHardy
2007-03-15 13:12 ` Roberto Nibali [this message]
2007-03-16 12:31 ` Patrick McHardy
2007-03-15 0:41 ` Henrik Nordstrom
2007-03-14 14:11 ` Amin Azez
2007-03-14 14:32 ` One unified table of nat/mangle/filter Henrik Nordstrom
2007-03-14 14:47 ` [PATCH 1/1] Re: dangerous? Setting mark in nat table Jozsef Kadlecsik
2007-03-14 16:47 ` Jan Engelhardt
2007-03-14 13:14 ` Henrik Nordstrom
2007-03-14 12:43 ` Amin Azez
2007-03-14 10:27 ` Henrik Nordstrom
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=45F9463D.6050502@drugphish.ch \
--to=ratz@drugphish.ch \
--cc=c-d.hailfinger.devel.2006@gmx.net \
--cc=henrik@henriknordstrom.net \
--cc=jengelh@linux01.gwdg.de \
--cc=kaber@trash.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.