netdev - Re: 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAEP_g=9cXwxNE=Fxis2F_qStp1gPsjyXr2wE2agHO9rLZcquXA@mail.gmail.com>
Date:	Wed, 27 Mar 2013 10:26:06 -0700
From:	Jesse Gross <jesse@...ira.com>
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, Mar 26, 2013 at 3:02 PM, 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.

There isn't a good way to do this at the moment.  One thing that would
be nice though is if we can make this as generic as possible to
different tunneling formats that might need to be configured in this
way rather than specific to VXLAN.

Another area think about is how best to supply the information to
GRO/RPS to do the software version of these offloads.
--
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