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

[Dietmar Maurer]

> >>That "transport zone" looks interesting. 
> 
> >>We you just mark physical interfaces (or bridges?) as part of a transport zone. 
> >>Then we have everything to setup the vxlan (each vlan belong to a zone)? 
> 
> yes, it should work. (interface could be better I think).
> 
> /etc/network/interfaces
> iface eth0
>   transportzone 1
>   address 192.168.0.1

Do we want to name "transport zones"? And do they have additional 
associated setting? If so, can/should we store them in /etc/pve/network.cfg?

/etc/pve/network.cfg
------------------------
zone: network1
   comment: 100Gbit local net for Customers
   ...

vlan : mycustombridge
   transportzone network1
   ...
-------------------------

??

> for vlan
> --------
> /etc/pve/network.cfg
> 
> vlan : mycustombridge
>        transportzone 1
>        vlan 2
>        bridge-vlan-aware 1|0  (for QinQ)
> 
> This create
> 
> iface mycustombridge
>      bridge-ports eth0.2
>      ....
> 
>