[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200624203123.GC47547@localhost.localdomain>
Date: Wed, 24 Jun 2020 17:31:23 -0300
From: Marcelo Ricardo Leitner <marcelo.leitner@...il.com>
To: minyard@....org
Cc: Xin Long <lucien.xin@...il.com>,
Michael Tuexen <Michael.Tuexen@...chi.franken.de>,
Yasevich <vyasevich@...il.com>,
Neil Horman <nhorman@...driver.com>,
linux-sctp@...r.kernel.org, linux-kernel@...r.kernel.org,
Corey Minyard <cminyard@...sta.com>
Subject: Re: [PATCH] sctp: Don't advertise IPv4 addresses if ipv6only is set
on the socket
On Tue, Jun 23, 2020 at 11:04:17AM -0500, minyard@....org wrote:
> From: Corey Minyard <cminyard@...sta.com>
>
> If a socket was set ipv6only, it would still send IPv4 addresses in the
> init and init ack packets. So don't add IPv4 addresses to ipv6only
> sockets.
>
> Based on a patch by Xin Long <lucien.xin@...il.com>
>
> Signed-off-by: Corey Minyard <cminyard@...sta.com>
> ---
> I have tested this and it seem to fix the issue. However, I'm wondering
> if it might be better to fix it where the addresses are put into the
> association as opposed to where they are put into the message.
Yes, it is. It even highlights why this issue was there in the first
place. Sending a patch right after this email.
Marcelo
Powered by blists - more mailing lists