netdev - Re: VxLAN support question

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]

Date:	Mon, 10 Aug 2015 22:37:28 -0700
From:	Alexei Starovoitov <ast@...mgrid.com>
To:	Andrew Qu <andrew.qu@...iatek.com>,
	David Miller <davem@...emloft.net>
Cc:	"tgraf@...g.ch" <tgraf@...g.ch>,
	"jesse@...ira.com" <jesse@...ira.com>,
	"pshelar@...ira.com" <pshelar@...ira.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: VxLAN support question

On 8/10/15 4:47 PM, Andrew Qu wrote:
>
> Pretty much what I want is that  kernel will have about 1K interfaces (something like Tunnel100.1-tunnel100.1000
> To be created and attached to 1K bridge domains on which each VNI is associated with given
> VNI to bridge-domain will be assigned using other CLIs)

creating 1k vxlan devices is doable, but you probably want to take
a look at recently added metadata mode of vxlan.
Also sounds like for each vni you'd need a different multicast group?
What fabric going to support that?

> ************* Email Confidentiality Notice ********************

please avoid such banners.

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