Search results

As stated above you need change your /etc/apt/sources.list file. yoi can do that from the CLI as linked above or since pve 7 you can also disable the enterprise repository and add the non-enterprise repository from the web-gui...

You seem to be on Proxmox 7.2 not the latest 7.3, maybe update your base install first then try for the new kernel. try a apt update && apt full-upgrade first before apt install pve-kernel-6.1 .

Edit your original First post. Click the "No Prefix" adjacent the thread title and select "solved from the drop-down menu/popup. Save the edit.

How about the other direction? Can the default gateway or anything in the 192.168.0.0 subnet ping 192.168.100.16? What are you using as a router? Does that router know, sometimes requires static routes, where and what interface to use to send data, DNS/web, back to the 192.168.0.0 subnet?

What does your full /etc/network/interfaces file look like? Will help answer questions such as what is the gateway, how many other IP's assigned to proxmox and does proxmox have more than 1 IP on the 10.10.10.0/24 subnet.

By default you can only have one gateway for the proxmox host. You should consider one of the below for each different Linux bridge/subnet you create that you would like to have internet access for the guest VM/LXC. Routed Configuration Masquerading (NAT) with iptables

many ways to go about this, BTW it appears you want redundancy so if your switch can handle it consider creating an LACP bond at switch port 3/4 and on proxmox host ports enp1s0/enp2s0 then use that bond# in vmbr0 making your /etc/network/interfaces file simpler (no need for any vmbr1 then). But...

Mainly wanted the option to do PCI-e passthrough.

OPNsense 22.7 vm working well for me. Uses FreeBSD 13.1 as a base and can use q35.

Jumbo frames are typically more trouble than they are worth particularly at 10g or less. Typically only bother with them for storage only networks. jumbo frames intermittently and seemingly randomly can screw up some normal background network traffic, from mDNS to ssh and others. Switches and...

seems to be working as I would expect, might be a misunderstanding on your part on how tagged and untagged traffic should work from the perspective of your switch port. Current setup on switch port 4: PVID 100, tagged 1, 101 plugged into Proxmox. All untagged network packets from proxmox and a...

This may not be the only issue but could be causing other problems at some time, on the switch, unless I am mistaken you should not have ant most 1 untagged vlan per switch port. You can have multiple tagged vlans per switchport though. 1. when a network Packet arrives at the switch port...

The only error I see is under vmbr0 the line iface vmbr0 inet static should no longer be static but should now be manual iface vmbr0 inet manual. Not sure if that will impact vmbr0.10 though. Change that then ifrelaod -a and see if you can get a connection. Have you double-checked that your...

Can you copy your /etc/network/interfaces file here? After making the changes did you reload the Network ifreload -a in a few rare instances people have had to reboot the Proxmox node to get Network changes such as vlans to come up correctly.

I find it easier to think about a linux bridge (vmbr#) as a switch with unlimited ports. When you define an IP/Gateway at the proxmox host level (with or without vlan) this is like plugging the proxmox host into the switch and not the Guest (vm/LXC). So adding a second IP address in a different...

Maybe I am misunderstanding the problem, but you would not need to define/create the 2 other VM IP's in the Proxmox host /etc/network/interfaces file at all. Using your second example /etc/network/interfaces file option, You create/install the 2 VM's and use vmbr0 as the Bridge for the network...

vmbr0 is just the default Proxmox starts naming bridges with, but it holds no magic otherwise. The management IP could be assigned to vmbr1 or vmbr67 and any vlan from 2-4094. vmbr0.10 is tied to vmbr0 by standard naming nomenclature. Just as vmbr67.8 would be one way to define/create vlan8 on...

What version of VyOS? I have 1.3.2 running in my home lab, but not there at the moment. by memory I did not use bridges in VyOS though. I set up the Vlans directly on eth0 interface not a bridge. maybe I am missing something, but Why have separate vlans at all if you are just going to bridge...

@spirit What is the cli command verify these new default setting? Should we check from Proxmox host cli or vm? any general advice on the number of queues relative to the number of VM vcpus? 1 to 1 a good starting point?

to be clear you intend to connect the Proxmox node directly to the internet without a firewall? connecting to the internet is not the same for everyone. What type of internet service provider (ISP) do you have? Do have modem? Is there a modem and dhcp server connected to the layer 2 switch...