Search results

the switch ports assigned to the two proxmox hosts should be left as untagged on vlan1 but should be tagged for vlan5, this shouldn't affect your existing setup. Once this is done, a vm on one host with a nic assigned to vmbr0v5 should be able to communicate with a vm on the other host, setup...

Create a VLAN interface on either host, allow tagged traffic on each port on the switch e.g iface eno1 inet manual iface eno1.5 inet manual auto vmbr0v5 iface vmbr0v5 inet manual bridge-ports eno1.5 bridge-stp off bridge-fd 0 auto vmbr0 iface vmbr0 inet static...

all of that can be done without TrueNAS - its just that the TrueNAS GUI makes it far easier to do. And if that's your core requirement, then install TrueNAS and run VM's under TrueNAS. Otherwise you can install samba and winbind either directly on the host or on a container but you will need to...

if you have a switch that supports VLANs you could span vlan traffic between the hosts

do you have firewall enabled on OMV VM?

your main problem is that the HP disk controller is a RAID controller not a HBA. It's possible to install a generic LSI card but you would need to purchase a set of internal SAS cables. I've done it, but it's not pretty or cheap. My goal was to run ZFS so there's no guarantee that you would be...

would certainly appear that there is an issue with the N5105 https://forum.proxmox.com/search/5335653/?q=N5105&o=date

did you test this or is that your assumption?

so what happens if you plug your laptop/desktop into the modem .... what dhcp address does that get?

you should check your IOMMU groups, the pci device could be in the same group as the NIC is eno1 considered 'UP' on the proxmox host? is the WAN interface 'UP' on the VM? try restarting networking on the host (make a non-critical network change in the host GUI like changing the auto-start...

the information in the screenshot you posted shows 'eno1: <NO-CARRIER, BROADCAST, MULTICAST, UP> .... vmbr0 DOWN' suggesting there is no link detected between host and switch, possible cable fault perhaps? do you have link lights on the switch and nic port?

the other variation is that you are tagging vlan 600 and an ip address explictly on bond1.600 where vlan 100 is configured differently. the documentation suggests auto bond0 iface bond0 inet manual bond-slaves eno1 eno2 bond-miimon 100 bond-mode 802.3ad...

can the host ping itself and the gateway? can you access the proxmox host from your desktop on the same lan? the default route doesn't look right... I'd expect that to look like this from the config you posted earlier? 192.168.254.254/24 dev vmbr0 proto kernel onlink

please try ip a | grep vmbr0

on the proxmox host what output does ip r and ip a produce?

your proxmox server probably has the same IP address as your router so they conflict when both are on.

I have to agree with much of what you say. I do think there is a case for a subscription-tier aimed at the 'home-lab' user, which perhaps just allows removal of the 'nag' and perhaps 'homelab subscriber' status in the forums. Having said that, I really appreciate the efforts of the proxmox...

The transfer speed will depend on a lot of factors. you have not given enough information for anyone to help you

First observation I would make is that you have allocated 4 cpu cores to a single VM when the host only has 4 cores to begin with, so in that case the host and VM are competing with each other for system resources. Also, how much RAM does the host have? pfSense runs quite well on 1cpu and 1gb of...

That's good advice, I would also avoid over-allocating RAM and CPU resources - it can often be counter-productive. That hardware is never going to offer great VM performance but see how your Windows VM runs with 2cpu and 8gb of ram and then go from there in small steps.