From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 212921] New: ECMP not working for local sockets
Date: Mon, 3 May 2021 07:38:49 -0700 [thread overview]
Message-ID: <20210503073849.27f9b4c0@hermes.local> (raw)
Begin forwarded message:
Date: Sun, 02 May 2021 07:10:44 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 212921] New: ECMP not working for local sockets
https://bugzilla.kernel.org/show_bug.cgi?id=212921
Bug ID: 212921
Summary: ECMP not working for local sockets
Product: Networking
Version: 2.5
Kernel Version: 5.8.0-50-generic
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: IPV4
Assignee: stephen@networkplumber.org
Reporter: nitin.i.joy@gmail.com
Regression: No
When you're creating local TCP sockets in a Linux machine, the connections to
the same destination IP are not load-balanced across multiple interfaces when
ECMP path is set. Even when net.ipv4.fib_multipath_hash_policy is set to L4
hash, multiple interfaces are never used for same destination.
I tried working around the issue by setting two route table entries with same
metric using `ip route append` command. In this case, the connections get
load-balanced across multiple interfaces for 5-10 seconds, after which all
future connections will choose one of the interfaces. There is no configuration
that can disable this behavior. I tried disabling tcp_metrics_nosave
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-05-03 14:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210503073849.27f9b4c0@hermes.local \
--to=stephen@networkplumber.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).