[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130327105254.2e10de02@nehalam.linuxnetplumber.net>
Date: Wed, 27 Mar 2013 10:52:54 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Alexander Duyck <alexander.h.duyck@...el.com>
Cc: netdev <netdev@...r.kernel.org>,
"Gasparakis, Joseph" <joseph.gasparakis@...el.com>,
Stephen Hemminger <shemminger@...tta.com>, pshelar@...ira.com,
David Miller <davem@...emloft.net>
Subject: Re: Is there a preferred way to get the VXLAN port number?
On Tue, 26 Mar 2013 15:02:45 -0700
Alexander Duyck <alexander.h.duyck@...el.com> wrote:
> I was wondering if someone would happen to know if there is already a
> preferred way to get the VXLAN port number for things such as
> configuring a device to recognize a VXLAN frame on receive for parsing
> purposes?
>
> I just wanted to check to make sure I hadn't missed something before
> submitting a patch that would export a simple function for supplying the
> vxlan_port value.
>
> Thanks,
>
> Alex
> --
> 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
There are two views of the world. One view is that the UDP port number
should be a fixed assigned number by IANA, and since VXLAN looks exactly
like Cisco LISP, that is what most people use. Others like DOVE seem
to want to use lots of values.
--
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