netdev - Re: [PATCH net] vxlan: use IANA assigned port

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130427015129.GJ8882@sequoia.sous-sol.org>
Date:	Fri, 26 Apr 2013 18:51:29 -0700
From:	Chris Wright <chrisw@...s-sol.org>
To:	David Miller <davem@...emloft.net>
Cc:	stephen@...workplumber.org, netdev@...r.kernel.org,
	kduda@...stanetworks.com, chrisw@...s-sol.org
Subject: Re: [PATCH net] vxlan: use IANA assigned port

* 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.
--
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