netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Julian Anastasov <ja@ssi.bg>
Cc: lvs-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Forward Shared Patch
Date: Mon, 26 Sep 2011 08:00:51 +0900	[thread overview]
Message-ID: <20110925230050.GL19787@verge.net.au> (raw)
In-Reply-To: <alpine.LFD.2.00.1109251129190.1474@ja.ssi.bg>

On Sun, Sep 25, 2011 at 11:39:21AM +0300, Julian Anastasov wrote:
> 
> 	Hello,
> 
> On Sun, 25 Sep 2011, Simon Horman wrote:
> 
> > Hi Julian,
> > 
> > I am wondering if you have any interest in/objections to trying
> > to merge your forward shared patch which allows an IPVS director
> > to act as a router for realservers using the direct routing or tunnelling
> > forwarding mechanisms.
> > 
> > http://www.ssi.bg/~ja/#lvsgw
> 
> 	Such feature is already added to 2.6.33:
> 
> /proc/sys/net/ipv4/conf/*/accept_local

Oh, great. Sorry for the noise.

      reply	other threads:[~2011-09-25 23:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-25  1:13 Forward Shared Patch Simon Horman
2011-09-25  8:39 ` Julian Anastasov
2011-09-25 23:00   ` Simon Horman [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=20110925230050.GL19787@verge.net.au \
    --to=horms@verge.net.au \
    --cc=ja@ssi.bg \
    --cc=lvs-devel@vger.kernel.org \
    --cc=netdev@vger.kernel.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).