[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a5ee7f3c99b14e43aac8938434fd9264@AcuMS.aculab.com>
Date: Thu, 15 Oct 2020 21:23:58 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Marcelo Ricardo Leitner' <marcelo.leitner@...il.com>,
Xin Long <lucien.xin@...il.com>
CC: network dev <netdev@...r.kernel.org>,
"linux-sctp@...r.kernel.org" <linux-sctp@...r.kernel.org>,
Neil Horman <nhorman@...driver.com>,
"Michael Tuexen" <tuexen@...muenster.de>,
"davem@...emloft.net" <davem@...emloft.net>,
"gnault@...hat.com" <gnault@...hat.com>,
"pabeni@...hat.com" <pabeni@...hat.com>,
"willemdebruijn.kernel@...il.com" <willemdebruijn.kernel@...il.com>
Subject: RE: [PATCHv3 net-next 16/16] sctp: enable udp tunneling socks
From: Marcelo Ricardo Leitner
> Sent: 15 October 2020 18:43
>
> Actually..
>
> On Tue, Oct 13, 2020 at 03:27:41PM +0800, Xin Long wrote:
> ...
> > Also add sysctl udp_port to allow changing the listening
> > sock's port by users.
I've not read through this change...
But surely the UDP port (or ports) that you need to use
will depend on the remote system's configuration.
So they need to be a property of the socket, not a
system-wide value.
I can easily imagine my M3UA code connecting to different
network providers which have decided to use different
UDP port numbers.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
Powered by blists - more mailing lists