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

[Alexandre DERUMIER]

>>I suggest to always use the zone id as prefix for vlan/vxlan
>>devices. Its simply to implement and avid problems in future.

ok no problem.  
(in this case, for vlan, do you want to use  eth0.x in bridge slaves directly ? or create a named vlan interface with vlan-raw-device ?)


>>Although most people will only have only one zone? 

yes, mostly. 




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

I suggest to always use the zone id as prefix for vlan/vxlan 
devices. Its simply to implement and avid problems in future. 

Although most people will only have only one zone? 

> On December 13, 2018 at 11:46 AM Alexandre DERUMIER <aderumier at odiso.com> wrote: 
> 
> 
> 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