netdev - Is there a preferred way to get the VXLAN port number?

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-next>] [day] [month] [year] [list]

Message-ID: <51521B05.6060401@intel.com>
Date:	Tue, 26 Mar 2013 15:02:45 -0700
From:	Alexander Duyck <alexander.h.duyck@...el.com>
To:	netdev <netdev@...r.kernel.org>
CC:	"Gasparakis, Joseph" <joseph.gasparakis@...el.com>,
	Stephen Hemminger <shemminger@...tta.com>, pshelar@...ira.com,
	David Miller <davem@...emloft.net>
Subject: Is there a preferred way to get the VXLAN port number?

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