From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <uwe.sauter.de@gmail.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
 (No client certificate requested)
 by lists.proxmox.com (Postfix) with ESMTPS id ED098F2E6
 for <pve-user@lists.proxmox.com>; Thu, 15 Dec 2022 08:23:51 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
 by firstgate.proxmox.com (Proxmox) with ESMTP id B68C840B2
 for <pve-user@lists.proxmox.com>; Thu, 15 Dec 2022 08:23:51 +0100 (CET)
Received: from mail-wr1-x42b.google.com (mail-wr1-x42b.google.com
 [IPv6:2a00:1450:4864:20::42b])
 (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
 (No client certificate requested)
 by firstgate.proxmox.com (Proxmox) with ESMTPS
 for <pve-user@lists.proxmox.com>; Thu, 15 Dec 2022 08:23:50 +0100 (CET)
Received: by mail-wr1-x42b.google.com with SMTP id f18so2106145wrj.5
 for <pve-user@lists.proxmox.com>; Wed, 14 Dec 2022 23:23:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
 h=content-transfer-encoding:subject:from:content-language:reply-to:to
 :user-agent:mime-version:date:message-id:from:to:cc:subject:date
 :message-id:reply-to;
 bh=xZUKxW+Fon72d4G7ZD7RHa6ja2POgiFYVbQXFbVUUfA=;
 b=IsGwIvBpCU7aR8h0B52qfVESRSRYCDkiyH+Hv/7+iKKXhO0+9sB0QZG3TtL6zKKchK
 nSmz0LJnHnPtdbedoxhM0Yadcz0h19aJjfKRxmiD6vBbF+DpMaHSM10jejHguQiwG9GJ
 xXoX2VihgAL+7gP5KWE2QB7l/Qg7BzVtKuoRB7kQ8uBCnSvterE8QJJuiEd/IWlAKjm+
 G9SiCxETK57MAnDEDlwKTlbZ2JoMfXfnAqzHVNjRZuPyIWsbQOSx2JYkq+PzybGw/u9N
 mbg+uR6ppxpiX6dAI12Ir9RLeljRCvhDo7UAJkoP1IJ8uOGqPO9Sogidi7F8Azsqdutc
 A6pA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=content-transfer-encoding:subject:from:content-language:reply-to:to
 :user-agent:mime-version:date:message-id:x-gm-message-state:from:to
 :cc:subject:date:message-id:reply-to;
 bh=xZUKxW+Fon72d4G7ZD7RHa6ja2POgiFYVbQXFbVUUfA=;
 b=Hyegusqn3yoz0sBD9LLGANytXfW99SV+jMt0vzpvn6f9bX7RrG3meU/O9vci7GrCKS
 aRslSYC1SSJxVwChbKe56cX+00AE1NsPH6KJBdiIkcwOcIcLXssb4jmcgI0dNLIyvdc1
 EVppt3DvIww5+Cf+q60QAAoLjz4xpipW837kBEq5UOls1QKIGnnEoS4l1p0rrwItew1f
 msh+rwsM4FpybjrWtMkIoXjblyTMyIXZvviDl/al/FODKYOjPFa7rMZtgsiSvdz3UcX0
 ewBz5cZ6512U+RbCNbpfDNBZc+bbtM7RTcnmBuxqAVewxiKIsm7QOQ7MW5v6fH6T6YGX
 YWfg==
X-Gm-Message-State: ANoB5plTCBK2gw6lKamwnGIXE0y3U815uMltWafKiIMJ5/AMAO6e8+r2
 /aczg1lsYAvDOItlB1uJ5HNG8aU3ukk=
X-Google-Smtp-Source: AA0mqf5qQdZCqvXsg4+D8Hh+DCs6wGTsoo/5xPosQwUYug5je5PITEWVqcyyr37+tkYDZdGSqnni/Q==
X-Received: by 2002:a05:6000:383:b0:254:3dcb:dbb3 with SMTP id
 u3-20020a056000038300b002543dcbdbb3mr6401240wrf.53.1671089022785; 
 Wed, 14 Dec 2022 23:23:42 -0800 (PST)
Received: from ?IPV6:2a02:8070:a280:2d80:5605:dbff:fe76:161d?
 ([2a02:8070:a280:2d80:5605:dbff:fe76:161d])
 by smtp.googlemail.com with ESMTPSA id
 u10-20020a5d514a000000b00242710c9910sm5261893wrt.8.2022.12.14.23.23.41
 for <pve-user@lists.proxmox.com>
 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
 Wed, 14 Dec 2022 23:23:42 -0800 (PST)
Message-ID: <0792849c-8d3f-e0de-460c-e89245c8d12b@gmail.com>
Date: Thu, 15 Dec 2022 08:23:41 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.6.0
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Reply-To: uwe.sauter.de@gmail.com
Content-Language: de-DE
From: Uwe Sauter <uwe.sauter.de@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-SPAM-LEVEL: Spam detection results:  0
 AWL -0.500 Adjusted score from AWL reputation of From: address
 BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
 DKIM_SIGNED               0.1 Message has a DKIM or DK signature,
 not necessarily valid
 DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature
 DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's
 domain
 DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from
 domain
 FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider
 KAM_EVIL_NUMBERS4           1 Phone Numbers used by scammers
 RCVD_IN_DNSWL_NONE     -0.0001 Sender listed at https://www.dnswl.org/,
 no trust
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_PASS               -0.001 SPF: sender matches SPF record
Subject: [PVE-User] How to configure which network is used for migration
X-BeenThere: pve-user@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE user list <pve-user.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>, 
 <mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-user/>
List-Post: <mailto:pve-user@lists.proxmox.com>
List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>, 
 <mailto:pve-user-request@lists.proxmox.com?subject=subscribe>
X-List-Received-Date: Thu, 15 Dec 2022 07:23:52 -0000

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  --+