[PVE-User] How to configure which network is used for migration

[Uwe Sauter]

Mark, Alexandre,

thanks for pointing that out.

@Mark: as these are private, isolated networks I'm unsure how IPv6 would help with the issue. I
could use link-local addresses (fe80::) but would need to append to every request the "%interface"
postfix in order to tell the system which interface to use…

Using unique local unicast addresses is no different in using private IPv4 networks…

So please enlighten me how IPv6 would help in that situation.

Besides that I agree – we should switch to IPv6 where it is sensible and possible (from an
organization's point of view).

Regards,

	Uwe

Am 15.12.22 um 09:04 schrieb Mark Schouten:
> Hi,
> 
> Some unsolicited advice, switch to IPv6 ;)
> 
> As for your question, you can set that up in the datacenter -> options tab. See
> https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_guest_migration
> 
> Regards,
> 
> —
> Mark Schouten, CTO
> Tuxis B.V.
> mark at tuxis.nl / +31 318 200208
> 
> 
> ------ Original Message ------
> From "Uwe Sauter" <uwe.sauter.de at gmail.com>
> To "Proxmox VE user list" <pve-user at lists.proxmox.com>
> Date 12/15/2022 8:23:41 AM
> Subject [PVE-User] How to configure which network is used for migration
> 
>> Good morning,
>>
>> I'm currently replacing one PVE cluster with another. The new hardware has a bunch of different
>> network interfaces that I want to use to separate VM traffic from Corosync/Ceph/migration traffic.
>>
>> Is there a way to configure the interface/network that is used for migration or does this depend on
>> the combination of hostname resolution and which hostname was used to create the cluster?
>> (I have various hostnames configured per host, for each configured network one, so that I can
>> explicitly choose which interface I use to connect to a host.)
>>
>> Regards,
>>
>>     Uwe
>>
>>
>> Interface configuration:
>>
>> eno1np0 --+-- untagged VLAN X -- Corosync ring 1/management network (192.168.1.0/24)
>>
>> eno2np1 N/C
>>
>> enp3s0  --+
>>           +-- bond0 --+-- bond0.100 -- vmbr100 \
>> enp4s0  --+           +-- bond0.101 -- vmbr101 +-- VM traffic
>>                       +-- bond0.102 -- vmbr102 /
>>
>> enp5s0  --+
>>           +-- bond1 --+-- untagged VLAN Y -- Corosync ring 0/Ceph (172.16.1.0/24)
>> enp6s0  --+
>>
>> _______________________________________________
>> pve-user mailing list
>> pve-user at lists.proxmox.com
>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>>
>