From: Ben Greear <greearb@candelatech.com>
To: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
Cc: Pavel Emelianov <xemul@openvz.org>,
Kirill Korotaev <dev@openvz.org>,
Linux Netdev List <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Linux Containers <containers@lists.osdl.org>,
Stephen Hemminger <shemminger@linux-foundation.org>,
Patrick McHardy <kaber@trash.net>
Subject: Re: [PATCH] Virtual ethernet tunnel (v.2)
Date: Fri, 08 Jun 2007 16:46:32 -0700 [thread overview]
Message-ID: <4669EA58.3000306@candelatech.com> (raw)
In-Reply-To: <4669B2BD.5060208@gmx.net>
Carl-Daniel Hailfinger wrote:
> On 08.06.2007 19:00, Ben Greear wrote:
>> I have another sysfs patch that allows setting a default skb->mark for
>> an interface so that you can set the skb->mark
>> before it hits the connection tracking logic, but I'm been told this one
>> has very little chance
>> of getting into the kernel. The skb->mark patch is only useful (as far
>> as I can tell) if you
>> also include a patch Patrick McHardy did for me that allowed the
>> conn-tracking logic to
>> use skb->mark as part of it's tuple. This allows me to do NAT between
>> virtual routers
>> (routing tables) on the same machine using veth-equivalent drivers to
>> connect the
>> routers. He thinks this will probably not ever get into the kernel either.
>
> Are these patches available somewhere? I'm currently doing NAT between
> virtual routers by some advanced iproute2/iptables trickery, but I have
> no way to handle the occasional tuple conflict.
A consolidated patch against 2.6.20.12 is here. It has a lot more than
just the patches mentioned above, but it shouldn't hurt anything to have
the whole patch applied:
http://www.candelatech.com/oss/candela_2.6.20.patch
The original patch for using skb->mark as a tuple was
written by Patrick McHardy, and is here:
http://www.candelatech.com/oss/skb_mark_conntrack.patch
His patch merged with my patch to sysfs to set skb->mark on ingress is here:
http://www.candelatech.com/oss/conntrack_mark_with_ssyctl.patch
Thanks,
Ben
>
> Regards,
> Carl-Daniel
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2007-06-08 23:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 11:13 [PATCH] Virtual ethernet tunnel (v.2) Pavel Emelianov
2007-06-07 11:16 ` [PATCH] Module for ip utility to support veth device (v.2) Pavel Emelianov
2007-06-07 15:59 ` Stephen Hemminger
2007-06-07 15:23 ` [PATCH] Virtual ethernet tunnel (v.2) Ben Greear
2007-06-07 15:39 ` Pavel Emelianov
2007-06-07 15:51 ` Ben Greear
2007-06-07 16:04 ` Pavel Emelianov
2007-06-07 16:35 ` Ben Greear
2007-06-08 16:00 ` Pavel Emelianov
2007-06-08 17:00 ` Ben Greear
2007-06-08 19:49 ` Carl-Daniel Hailfinger
2007-06-08 23:46 ` Ben Greear [this message]
2007-06-11 11:42 ` Patrick McHardy
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=4669EA58.3000306@candelatech.com \
--to=greearb@candelatech.com \
--cc=c-d.hailfinger.devel.2006@gmx.net \
--cc=containers@lists.osdl.org \
--cc=davem@davemloft.net \
--cc=dev@openvz.org \
--cc=ebiederm@xmission.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
--cc=xemul@openvz.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;
as well as URLs for NNTP newsgroup(s).