[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20130426.232232.688463657786151100.davem@davemloft.net>
Date: Fri, 26 Apr 2013 23:22:32 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: chrisw@...s-sol.org
Cc: stephen@...workplumber.org, netdev@...r.kernel.org,
kduda@...stanetworks.com
Subject: Re: [PATCH net] vxlan: use IANA assigned port
From: Chris Wright <chrisw@...s-sol.org>
Date: Fri, 26 Apr 2013 18:51:29 -0700
> * David Miller (davem@...emloft.net) wrote:
>> From: Stephen Hemminger <stephen@...workplumber.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@...workplumber.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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists