From: Wendell Hatcher <wendellhatcher1074@gmail.com>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] promox hetzner install?
Date: Mon, 11 Oct 2021 16:58:20 -0400 [thread overview]
Message-ID: <4a3bf1bb-9f95-44f9-56ed-e9f045c4a227@gmail.com> (raw)
https://community.hetzner.com/tutorials/install-and-configure-proxmox_ve
I am following the promox hetzner installation guide and my new linux
bridge keeps failing. It is stating it needs a virtual mac address per
hetzner as well as setup properly. It locks up my system each time what
am i doing wrong here?
# /etc/network/interfaces# /etc/network/interfaces
iface eno1 inet static
address 192.9.122.105/27
gateway 192.9.122.97
up route add -net 192.9.122.96 netmask 255.255.255.224 gw 192.9.122.97
dev eno1
# route 192.9.122.96/27 via 192.9.122.97
#auto vmbr0
#iface vmbr0 inet static
# address 10.10.10.2/24
# hwaddress 00:50:56:00:88:1E # MAC address of the NIC, required since
Proxmox 7.0
# netmask 255.255.255.254
# bridge-ports eno1
# bridge-stp off
# bridge-fd 0
# bridge-vlan-aware yes
# bridge-vids 2-4094
reply other threads:[~2021-10-11 20:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4a3bf1bb-9f95-44f9-56ed-e9f045c4a227@gmail.com \
--to=wendellhatcher1074@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