netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: ja@ssi.bg
Cc: netdev@vger.kernel.org
Subject: Re: IPVS-DR problem with neigh lookup in 3.6
Date: Thu, 04 Oct 2012 02:58:08 -0400 (EDT)	[thread overview]
Message-ID: <20121004.025808.2302904472507419433.davem@davemloft.net> (raw)
In-Reply-To: <alpine.LFD.2.00.1210040923010.1618@ja.ssi.bg>

From: Julian Anastasov <ja@ssi.bg>
Date: Thu, 4 Oct 2012 09:52:47 +0300 (EEST)

> 	Is it a good idea to keep rt_gateway always
> valid and to check RTCF_REDIRECTED where needed?

What exactly do you mean by this?  rt_gateway can only
be explicit nexthop or zero for local subnet.

It cannot take on any other value, otherwise routes are
not properly sharable.

> Because adding rt_dst does not look good, it will not
> help to callforward_do_filter too.

Adding rt_dst is not to be seriously considered.

  reply	other threads:[~2012-10-04  6:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-04  6:52 IPVS-DR problem with neigh lookup in 3.6 Julian Anastasov
2012-10-04  6:58 ` David Miller [this message]
2012-10-04  9:11   ` Julian Anastasov

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=20121004.025808.2302904472507419433.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ja@ssi.bg \
    --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).