* multi-path route can't keep long time connections
@ 2010-06-22 1:48 tingwei liu
2010-06-22 6:16 ` Patrick McHardy
0 siblings, 1 reply; 3+ messages in thread
From: tingwei liu @ 2010-06-22 1:48 UTC (permalink / raw)
To: netfilter-devel, netfilter
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?
Your response is pleasure.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: multi-path route can't keep long time connections
2010-06-22 1:48 multi-path route can't keep long time connections tingwei liu
@ 2010-06-22 6:16 ` Patrick McHardy
2010-06-29 2:36 ` tingwei liu
0 siblings, 1 reply; 3+ messages in thread
From: Patrick McHardy @ 2010-06-22 6:16 UTC (permalink / raw)
To: tingwei liu; +Cc: netfilter-devel, netfilter
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: multi-path route can't keep long time connections
2010-06-22 6:16 ` Patrick McHardy
@ 2010-06-29 2:36 ` tingwei liu
0 siblings, 0 replies; 3+ messages in thread
From: tingwei liu @ 2010-06-29 2:36 UTC (permalink / raw)
To: Patrick McHardy, netfilter-devel
Thank you very much.
2010/6/22 Patrick McHardy <kaber@trash.net>:
> 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.
>
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-06-29 2:36 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-06-22 1:48 multi-path route can't keep long time connections tingwei liu
2010-06-22 6:16 ` Patrick McHardy
2010-06-29 2:36 ` tingwei liu
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).