I've installed Proxmox many times on various bits of hardware without a problem. I came in to possession of two old i7 Mac Minis and thought I'd try out Proxmox on them. The Proxmox installer didn't work so I went with the install Debian then Proxmox approach following the instructions here...
VLANs work simply by adding a bit of information in the header that says "I'm in VLAN 25". Untagged port 25 is the switch saying "I expect the traffic to tell me what to do" and Tagged 25 is "I'm telling the traffic what to do". This is obviously oversimplified but it's pretty close.
One thing...
It might be that your cards are directly compatible with Debian. Mine obviously aren't and need the ixgbe driver loaded to function.
https://www.intel.co.uk/content/www/uk/en/support/articles/000005688/network-and-i-o/ethernet-products.html
Based on what you've written
The ports should be untagged for the VLANs
Your Proxmox bridges should be VLAN Aware (it's a checkbox)
Your VMs should be on the VLAN you need them on (text box on the Networking page of the VM Hardware tab)
If you want a VM to see more than one VLAN it either...
Can you run
cat /etc/network/interfaces
on the Proxmox server and paste the output here?
Also the output of
ip address show up
And the IP config of your laptop or router (a screenshot will do) just as a point as reference.
I'm using bridges so the physical devices shouldn't need to autostart.
Update: Tried it anyway, still get the "error: vmbr1: bridge port enp2s0f1 does not exist" error
Last year I built a DIY NAS using a motherboard that had a 10Gb port on it. Since then I've been slowly updating my home network to 10Gb.
Now I've got a (second hand but known to be working) 10gb card which I've put in to my (existing) Proxmox server. Powered it back on and the OS and Proxmox...
This is it's CURRENT config - as I said there has been fiddling and tweaking going on.
root@pve:~# qm config 908
agent: 1
bootdisk: scsi0
cores: 4
ide2: local:iso/ubuntu-18.04.3-live-server-amd64.iso,media=cdrom
memory: 65536
name: externaldocker
net0...
Hi,
I have a Proxmox machine that has quite a beefy spec - 256Gb RAM, a few SSDs and HDs and dual Xeon(R) CPU E5-2640. It's a powerful machine and Proxmox runs everything I throw at it. Until recently.
I used to use an i5 Shuttle with 8Gb of RAM and a 1tb hard disk as my Docker server running...
I have been having a problem with my Proxmox server's networking so I gave up and wiped it and reinstalled Proxmox from scratch. I still have the problem and it seems to be something about Proxmox.
I know this is going to be something simple and I just need to tweak something somewhere. The...
That document is no use at all. The very first paragraph tells you it's not what I'm looking for. And to offer "I know this does not work at the moment, but if it would you could." as a suggestion makes me wonder what I pay my subscription for.
I recently made a complete mess of my Proxmox server (it's a homelab) by trying to install a GPU. Made such a mess that I gave up and reinstalled everything. This was fine until I tried to install the self-signed certificates that I'd had installed on the previous version of the server. (They...
I had some LXC containers running on my Proxmox server and wanted up upgrade the hard disk they were located on. I moved their storage to another hard disk on my server, shut down the server, replaced the disk with some 6Tb disks and powered everything back on. Created a new zpool with the new...
root@pve1:~# ip addr show up
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.