From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
Patrick Buryk <pburyk@gmail.com>
Subject: Re: [PVE-User] Subject: Proxmox VE 7.1-2 Installation question
Date: Mon, 10 Jan 2022 09:34:34 +0100 [thread overview]
Message-ID: <c54049f6-5018-685d-4205-66ff90056501@proxmox.com> (raw)
In-Reply-To: <CAEJyo+tdjRJPm9tnEWGLRDOHFhE1g3+9TDHK4Ku_0N0WWD+k3A@mail.gmail.com>
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 <NIC> 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
>
>
next prev parent reply other threads:[~2022-01-10 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 19:01 Patrick Buryk
2022-01-10 8:34 ` Aaron Lauterer [this message]
2022-01-10 9:00 ` Konold, Martin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c54049f6-5018-685d-4205-66ff90056501@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=pburyk@gmail.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox