RE: How to setup a multi vlan connection to an (Ubuntu) XEN-server !!??

["louis.forums@xxxxxxxxx" <lsrbreda@xxxxxxxxx>]

Yep,

If canonical is using netplan. IMHO all the network definitions for the server 
should be configured that way. 

Your example is in the direction I would like to go, however a lot of things 
still to be solved. To mention a few:
- I would like a proper specification of the yaml file format. Is that 
available somewhere??
- you are using macaddresses. Why?
- you do not assign ip-addresses. Why?
- you do not specify vlan related gateways and routing tables .... ??
- you are talking about a simple nic and a trunk. There seems only a trunk 
definition in the example ?
- is het necessary to add a bridge if there is only one vm using a certain vlan

So lot of questions, never the less it supports my idea that this is the way to 
go


Louis

-----Original Message-----
From: Xen-users <xen-users-bounces@xxxxxxxxxxxxxxxxxxxx> On Behalf Of Bill 
MacAllister
Sent: Thursday, October 6, 2022 12:12 AM
To: louis.forums@xxxxxxxxx <lsrbreda@xxxxxxxxx>
Cc: xen-users@xxxxxxxxxxxxxxxxxxxx
Subject: Re: How to setup a multi vlan connection to an (Ubuntu) XEN-server !!??

On 2022-10-05 00:59, louis.forums@xxxxxxxxx wrote:
> I try to configure a Xen server based on the latest Ubuntu server. The 
> server will be connected to a network trunk using vlan's.

Ubuntu network configuration has moved to using netplan.  netplan is really a 
wrapper around other network tools on the system and intended to make the 
configuration of systemd network or netmanager networking simpler.  Took me a 
while to get a trunked configuration to work, but once you get it is fairly 
straight forward.  Here is an example:

# file: /etc/netplan/config-trunk.yaml
network:
   version: 2
   renderer: networkd
   ethernets:
     eno2:
       mtu: 9000
       dhcp4: no
       dhcp6: no
   bridges:
     br179:
       macaddress: 66:c5:7f:bf:f6:00
       mtu: 9000
       dhcp4: no
       dhcp6: no
       interfaces: [ vlan179 ]
     br180:
       macaddress: 66:c5:7f:bf:f6:10
       mtu: 9000
       dhcp4: no
       dhcp6: no
       interfaces: [ vlan180 ]
   vlans:
     vlan179:
       mtu: 9000
       id: 179
       link: eno2
       dhcp4: no
       dhcp6: no
     vlan180:
       mtu: 9000
       id: 180
       link: eno2
       dhcp4: no
       dhcp6: no

This assumes that you have the netplan.io package installed.  Be careful about 
the MAC addresses you use.  Since you make them up make sure you don't 
duplicate anything on the local network.  You will note in my example that the 
second NIC is used for trunking.
This is  just because we use FAI for building systems and PXE booting is not 
supported on trunked ports.  The first NIC is a simple access port.

Once you get the bridged network up then the network definition in the xen 
configuration need to reference the VLAN.  I use xen-create-image to build 
guests which just means I add --vlan=N to the command.  An example from a xen 
cfg file is:

vif         = [ 'ip=10.0.0.18, mac=00:16:3E:1B:D1:EA, vlan=180' ]


Bill

--
"What can be asserted without evidence can also be dismissed without evidence."
Christopher Hitchens