[pve-devel] [PATCH pve-docs 0/1] vxlan l3 routing

[Alexandre DERUMIER]

looking at kernel code in this patch
https://lore.kernel.org/patchwork/patch/768867/


+		if (tmp->cfg.vni != conf->vni)
+			continue;
+		if ((tmp->default_dst.remote_ip.sa.sa_family == AF_INET6 ||
+		     tmp->cfg.saddr.sa.sa_family == AF_INET6) != use_ipv6)
+			continue;
+		if (tmp->cfg.dst_port != vxlan->cfg.dst_port)
+			continue;

it's only possible with a different dstport.

/bin/ip  link add dev vxlan20 type vxlan id 20 dstport 4789
/bin/ip  link add dev vxlan21 type vxlan id 20 dstport 4790

(not sure it's usefull)



+		if ((tmp->flags & VXLAN_F_RCV_FLAGS) !=
+		    (vxlan->flags & VXLAN_F_RCV_FLAGS))
+			continue;

or some diffents flags
#define VXLAN_F_RCV_FLAGS		(VXLAN_F_GBP |			\
					 VXLAN_F_GPE |			\
					 VXLAN_F_UDP_ZERO_CSUM6_RX |	\
					 VXLAN_F_REMCSUM_RX |		\
					 VXLAN_F_REMCSUM_NOPARTIAL |	\
					 VXLAN_F_COLLECT_METADATA)


+
+#if IS_ENABLED(CONFIG_IPV6)
+		if (conf->remote_ifindex != tmp->cfg.remote_ifindex &&
+		    conf->saddr.sa.sa_family == AF_INET6 &&
+		    tmp->cfg.saddr.sa.sa_family == AF_INET6 &&
+		    (ipv6_addr_type(&conf->saddr.sin6.sin6_addr) &
+		     IPV6_ADDR_LINKLOCAL) &&
+		    (ipv6_addr_type(&tmp->cfg.saddr.sin6.sin6_addr) &
+		     IPV6_ADDR_LINKLOCAL))
+			continue;

or with ipv6 local link







----- Mail original -----
De: "aderumier" <aderumier at odiso.com>
À: "dietmar" <dietmar at proxmox.com>
Cc: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Jeudi 13 Décembre 2018 11:13:51
Objet: Re: [pve-devel] [PATCH pve-docs 0/1] vxlan l3 routing

>>Is there a technical reason for that, or is that just a bug? 

I really don't know if it's in vxlan rfc or not. 
Maybe because we have 16 million vxlan-id, they don't have implemented it in the kernel. 

----- Mail original ----- 
De: "dietmar" <dietmar at proxmox.com> 
À: "aderumier" <aderumier at odiso.com> 
Cc: "pve-devel" <pve-devel at pve.proxmox.com> 
Envoyé: Jeudi 13 Décembre 2018 10:03:52 
Objet: Re: [pve-devel] [PATCH pve-docs 0/1] vxlan l3 routing 

> On December 13, 2018 at 9:12 AM Alexandre DERUMIER <aderumier at odiso.com> wrote: 
> 
> 
> >>I just noticed that can have v(x)lan IDs multiple times, 
> >>once for each transport zone? So we need a better 
> >>naming scheme, for example: 
> 
> >>vxlan2 in zone1 => z1vxlan2 
> >>vxlan2 in zone2 => z2vxlan2 
> 
> it's not possible to have 2 vxlan vtep with same vxlan-id. 
> 
> auto vxlan2 
> iface vxlan2 inet manual 
> vxlan-id 2 
> 
> auto vxlan3 
> iface vxlan3 inet manual 
> vxlan-id 2 
> 
> # ifup vxlan2 
> # ifup vxlan3 
> warning: vxlan3: vxlan add/set failed: cmd '/bin/ip link add dev vxlan3 type vxlan id 2 dstport 4789' failed: returned 2 (Error: A VXLAN device with the specified VNI already exists. 

Is there a technical reason for that, or is that just a bug? 

_______________________________________________ 
pve-devel mailing list 
pve-devel at pve.proxmox.com 
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel