From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 DED8C88B60 for ; Mon, 10 Jan 2022 10:08:56 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id CD117B4D1 for ; Mon, 10 Jan 2022 10:08:26 +0100 (CET) Received: from mx0.konsec.net (hbase53.h.konsec.com [88.99.94.78]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 0328BB4C5 for ; Mon, 10 Jan 2022 10:08:26 +0100 (CET) Received: from kolab.konsec.com (unknown [10.21.1.190]) by mx0.konsec.net (Postfix) with ESMTPS id B684B85C117 for ; Mon, 10 Jan 2022 10:00:50 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=konsec.com; s=201809; t=1641805250; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=15+a15UPzBU6mud3ww+7nasfU8/b9HAJxTrd6zW//J0=; b=DNwffslUhWpNdf2o3YFb6rWc182DZmHZwxOT+4AY/4azf1wNDyPy0QKDzjY1Fab8m8ob/l oukiEa/VGkiz1aI3HDOd9Njt53nsDwnnh1OoiJPqwpZJS2DiQzE40jPaoC2PGKXoHMJopc svdRDal4GnqEWmk6/y2+BOAUJ1uegAdwN6xXY2LPLsLywaPWr7Imf+AaPyxp+CIW62wcNp shF4pwH7PfYoBSTnfqDIegG0f2WKxmmKUTIKwcBbotfIwr3upDJY+1AZqz9jP9gdRw7WgN brjxoCT1me1eN3jZExegB0eF/wv1D0B32nPScCL/vYil+nIhtSxpTlKYEI8XYw== Sender: martin.konold@konsec.com MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Mon, 10 Jan 2022 10:00:50 +0100 From: "Konold, Martin" To: Proxmox VE user list Reply-To: martin.konold@konsec.com In-Reply-To: References: Message-ID: <9582a88b2bdba2b803dde227cef900a8@konsec.com> X-Sender: martin.konold@konsec.com Organization: KONSEC GmbH X-SPAM-LEVEL: Spam detection results: 0 AWL 0.100 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 JMQ_SPF_NEUTRAL 0.5 SPF set to ?all KAM_ASCII_DIVIDERS 0.8 Spam that uses ascii formatting tricks SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [PVE-User] Subject: Proxmox VE 7.1-2 Installation question X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jan 2022 09:08:56 -0000 Hi, I made the experience that the device names did change between the installation and the first boot. You may need to adjust the device names in /etc/network/interfaces. Regards ppa. Martin Konold -- Martin Konold - Prokurist, CTO KONSEC GmbH -⁠ make things real Amtsgericht Stuttgart, HRB 23690 Geschäftsführer: Andreas Mack Im Köller 3, 70794 Filderstadt, Germany Am 2022-01-10 09:34, schrieb Aaron Lauterer: > That the IP address is configured on the vmbr0 interface is normal and > the basic default after a fresh installation. You can change that > later if you want to place the MGMT IP somewhere else. > The vmbr0 interface is needed as the "virtual switch" to which the > guests will be connected to. > The vmbr0 is using the physical interface as bridge port. Check out > the /etc/network/interfaces file for more details. > > Regarding the network not working; do you have more than one NIC in > that system? > If so, it is likely that the installer selected the NIC that is > currently not connected. You could try to just plug in the cable to > the other NIC or change the /etc/network/interfaces file accordingly > so that the vmbr0 will use that other NIC. Then either reboot or run > `ifreload -a` to apply the network config. > > If that is not the case, and there is only one NIC in the system, try > to run `ip l s up` and also check your kernel logs / dmesg for > any messages regarding the network that might give us more information > why the NICs are not up. > > Best regards, > Aaron > > On 1/9/22 20:01, Patrick Buryk wrote: >> Hello, All - >> >> I'm a new user of Proxmox, having just installed VE 7.1-2 for about >> the 5th >> time trying to resolve the following issue: >> >> After a successful install, I login to my host as root. >> I cannot ping in or out of the host; "ip address" & "ip link" commands >> show >> that the eno1 and vmbr0 interfaces are "UP", but their states are >> "DOWN". >> Static IP address is shown on vmbr0 interface only - I would have >> imagined >> that it would have been set to the eno1 interface instead during the >> install but, again, this is my first exposure to this product. >> Connection >> to my switch show no activity from the host. Ethernet cable has been >> verified to work on another host. >> >> Any ideas?? >> >> Thanks, and best wishes to all in 2022! >> >> Cheers! >> Patrick >> pburyk@gmail.com >> _______________________________________________ >> pve-user mailing list >> pve-user@lists.proxmox.com >> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user >> >> > > > _______________________________________________ > pve-user mailing list > pve-user@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user