From: Pau Espin Pedrol <pespin@sysmocom.de>
To: linux-sctp@vger.kernel.org
Subject: Re: SCTP multi-homed association (::1)->(::1+127.0.0.1) attempting HEARTBEAT on 127.0.0.1->127.0.0.1
Date: Mon, 24 Aug 2020 10:00:27 +0000 [thread overview]
Message-ID: <44227020-4061-9fc9-0175-e64de5c22e15@sysmocom.de> (raw)
In-Reply-To: <552de663-8aeb-ff84-a425-988da88ca5cd@sysmocom.de>
Hi Marcelo,
Between my initial message and your response I updated my kernel to
Archlinux latest package version (5.8.3-arch1-1,
https://git.archlinux.org/linux.git/), which still shows the same bug I
mentioned in my previous message.
The commit you described is already contained in the kernel (it was
included upstream during v5.8-rc3).
Moreover, the description of the commit you shared doesn't seem to match
the issue I described. The issue I explained is about the kernel trying
to create further connections on an already ongoing association using a
local IPv4 address it was never bound to; the issue has nothing to do
with advertising of addresses (advertising is working correctly here IMHO).
Quick similar scenario setup would be something like:
SERVER:
server_fd = socket(AF_INET6, SCTP, STREAM);
sctp_bindx(server_fd, "127.0.0.1", "::1");
listen(server_fd); accept(server_fd);
CLIENT:
client_fd = socket(AF_INET6, SCTP, STREAM);
sctp_bindx(client_fd, "::1");
sctp_connectx(client_fd, "::1");
And then after client connects ::1<->::1 and gains info about server's
127.0.0.1 address, it tries to INIT 127.0.0.1->127.0.0.1 despite it was
never bound to 127.0.0.1.
Regards,
Pau
--
- Pau Espin Pedrol <pespin@sysmocom.de> http://www.sysmocom.de/
===================================* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
next prev parent reply other threads:[~2020-08-24 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 11:11 SCTP multi-homed association (::1)->(::1+127.0.0.1) attempting HEARTBEAT on 127.0.0.1->127.0.0.1 Pau Espin Pedrol
2020-08-21 20:17 ` Marcelo Ricardo Leitner
2020-08-24 10:00 ` Pau Espin Pedrol [this message]
2020-08-24 10:23 ` Pau Espin Pedrol
2020-08-24 10:33 ` Pau Espin Pedrol
2020-08-24 10:46 ` Harald Welte
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=44227020-4061-9fc9-0175-e64de5c22e15@sysmocom.de \
--to=pespin@sysmocom.de \
--cc=linux-sctp@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).