* [PATCH net] vxlan: use IANA assigned port
@ 2013-04-26 23:33 Stephen Hemminger
2013-04-26 23:44 ` David Miller
0 siblings, 1 reply; 5+ messages in thread
From: Stephen Hemminger @ 2013-04-26 23:33 UTC (permalink / raw)
To: David Miller, netdev; +Cc: Kenneth Duda, Chris Wright
Ken Duda of Arista Networks, one of the VXLAN RFC authors notified
me that IANA has assigned an official port for VXLAN. My initial version
of the driver used the value from CISCO LISP that was also being used by
OpenVswitch.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
--- a/drivers/net/vxlan.c 2013-04-22 15:44:00.962002827 -0700
+++ b/drivers/net/vxlan.c 2013-04-26 16:29:19.349507680 -0700
@@ -8,7 +8,6 @@
* published by the Free Software Foundation.
*
* TODO
- * - use IANA UDP port number (when defined)
* - IPv6 (not in RFC)
*/
@@ -66,7 +65,7 @@ struct vxlanhdr {
};
/* UDP port for VXLAN traffic. */
-static unsigned int vxlan_port __read_mostly = 8472;
+static unsigned int vxlan_port __read_mostly = 4789;
module_param_named(udp_port, vxlan_port, uint, 0444);
MODULE_PARM_DESC(udp_port, "Destination UDP port");
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH net] vxlan: use IANA assigned port
2013-04-26 23:33 [PATCH net] vxlan: use IANA assigned port Stephen Hemminger
@ 2013-04-26 23:44 ` David Miller
2013-04-27 1:51 ` Chris Wright
0 siblings, 1 reply; 5+ messages in thread
From: David Miller @ 2013-04-26 23:44 UTC (permalink / raw)
To: stephen; +Cc: netdev, kduda, chrisw
From: Stephen Hemminger <stephen@networkplumber.org>
Date: Fri, 26 Apr 2013 16:33:46 -0700
> Ken Duda of Arista Networks, one of the VXLAN RFC authors notified
> me that IANA has assigned an official port for VXLAN. My initial version
> of the driver used the value from CISCO LISP that was also being used by
> OpenVswitch.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
So how does this interact with already deployed VXLAN links?
What is the backwards compatability story? What if one node upgrades
with this patch installed, but all the other nodes are left using
the older port number by default?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH net] vxlan: use IANA assigned port
2013-04-26 23:44 ` David Miller
@ 2013-04-27 1:51 ` Chris Wright
2013-04-27 3:22 ` David Miller
0 siblings, 1 reply; 5+ messages in thread
From: Chris Wright @ 2013-04-27 1:51 UTC (permalink / raw)
To: David Miller; +Cc: stephen, netdev, kduda, chrisw
* David Miller (davem@davemloft.net) wrote:
> From: Stephen Hemminger <stephen@networkplumber.org>
> Date: Fri, 26 Apr 2013 16:33:46 -0700
>
> > Ken Duda of Arista Networks, one of the VXLAN RFC authors notified
> > me that IANA has assigned an official port for VXLAN. My initial version
> > of the driver used the value from CISCO LISP that was also being used by
> > OpenVswitch.
> >
> > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>
> So how does this interact with already deployed VXLAN links?
>
> What is the backwards compatability story? What if one node upgrades
> with this patch installed, but all the other nodes are left using
> the older port number by default?
With this patch, I think one node upgrading would need to override
the default vxlan_port module param (falling back to the pre IANA
default) to keep active with the existing overlays.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH net] vxlan: use IANA assigned port
2013-04-27 1:51 ` Chris Wright
@ 2013-04-27 3:22 ` David Miller
[not found] ` <CAOaVG14yv=TixikAkrjEOTBznoC6YDqm1vb4ByZ32bgXM3Q7xQ@mail.gmail.com>
0 siblings, 1 reply; 5+ messages in thread
From: David Miller @ 2013-04-27 3:22 UTC (permalink / raw)
To: chrisw; +Cc: stephen, netdev, kduda
From: Chris Wright <chrisw@sous-sol.org>
Date: Fri, 26 Apr 2013 18:51:29 -0700
> * David Miller (davem@davemloft.net) wrote:
>> From: Stephen Hemminger <stephen@networkplumber.org>
>> Date: Fri, 26 Apr 2013 16:33:46 -0700
>>
>> > Ken Duda of Arista Networks, one of the VXLAN RFC authors notified
>> > me that IANA has assigned an official port for VXLAN. My initial version
>> > of the driver used the value from CISCO LISP that was also being used by
>> > OpenVswitch.
>> >
>> > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>>
>> So how does this interact with already deployed VXLAN links?
>>
>> What is the backwards compatability story? What if one node upgrades
>> with this patch installed, but all the other nodes are left using
>> the older port number by default?
>
> With this patch, I think one node upgrading would need to override
> the default vxlan_port module param (falling back to the pre IANA
> default) to keep active with the existing overlays.
That's an unacceptable burdon for our users.
We're stuck with the initial port number you've choosen.
People can override to the "official" port if they want to.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH net] vxlan: use IANA assigned port
[not found] ` <CAOaVG14yv=TixikAkrjEOTBznoC6YDqm1vb4ByZ32bgXM3Q7xQ@mail.gmail.com>
@ 2013-04-27 7:43 ` David Miller
0 siblings, 0 replies; 5+ messages in thread
From: David Miller @ 2013-04-27 7:43 UTC (permalink / raw)
To: stephen; +Cc: kduda, netdev, chrisw
From: Stephen Hemminger <stephen@networkplumber.org>
Date: Fri, 26 Apr 2013 21:53:59 -0700
> The port should be a property anyway.
> That way the value is easier to control. And we can do the transistion
> there.
Works for me.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2013-04-27 7:43 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-04-26 23:33 [PATCH net] vxlan: use IANA assigned port Stephen Hemminger
2013-04-26 23:44 ` David Miller
2013-04-27 1:51 ` Chris Wright
2013-04-27 3:22 ` David Miller
[not found] ` <CAOaVG14yv=TixikAkrjEOTBznoC6YDqm1vb4ByZ32bgXM3Q7xQ@mail.gmail.com>
2013-04-27 7:43 ` David Miller
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).