From: Patrick McHardy <kaber@trash.net>
To: tingwei liu <tingw.liu@gmail.com>
Cc: netfilter-devel@vger.kernel.org, netfilter@vger.kernel.org
Subject: Re: multi-path route can't keep long time connections
Date: Tue, 22 Jun 2010 08:16:17 +0200 [thread overview]
Message-ID: <4C205531.2010402@trash.net> (raw)
In-Reply-To: <AANLkTimeYhY-lgY2c5dfYQRDZ2oDLpB1U7TzkvyFQh_A@mail.gmail.com>
tingwei liu wrote:
> Because route circularly flush route cache
> (/proc/net/sys/ipv4/route/secret_timeval),the multi-path route can't
> keep long time connections. The long time connections maybe interrupt
> every "secret_timeval" seconds.
> Such as:
> default nexthop via 192.168.0.1 weight 1
> via 192.168.1.1 weight 1
> via 192.168.2.1 weight 1
>
> With a connection cross 192.168.0.1 in the first time."secret_timeval"
> seconds later,this connection maybe cross 192.168.1.1,then this
> connection will be reconnect.
>
> Anyone can help me?
Use CONNMARK to mark new connections, than use that mark
to bind them to a specific route.
next prev parent reply other threads:[~2010-06-22 6:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 1:48 multi-path route can't keep long time connections tingwei liu
2010-06-22 6:16 ` Patrick McHardy [this message]
2010-06-29 2:36 ` tingwei liu
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=4C205531.2010402@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=tingw.liu@gmail.com \
/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).