Search results

No, you don't have to bridge, but I think you gain more from having a bridge than not. Is there a reason why you don't want to bridge?

If I understand you correctly; a) you want your proxmox host to be on the 'main' network and accessible from there and potentially from outside your network via NAT b) you want your virtual machines to be on their own network but they should be able to access the internet if required So a...

Having a bridge does not preclude NAT, you only need to have a config that fits your NAT rules. Both of your networks are in the 192.168.0.0/16 subnet - i.e they are both private networks so the way you are approaching this would mean you would be having to do double-NAT to reach your VM's from...

The simplest way to set this up IMV is to install tailscale on a VM running on your proxmox host. You can then connect from outside your network using another pc running tailscale and away you go https://tailscale.com

as @_gabriel says, step1 - remove vmbr1,2 and 3 from your config. step2 - verify your host can ping a remote address like 8.8.8.8 or 1.1.1.1 (if not then this where your problem is, not on the VM config) step3 - create a vm with a nic assigned to vmbr0 and a manual IP assigned like...

You can run proxmox 'nested' - i.e in a VM running proxmox, no reason why you couldn't run a couple of virtual instances of proxmox on a single host, performance wouldn't be great but probably good enough for training and learning

try swapping the nics between slots and see what happens

what kind of cpu/chipset is your host running on? could be limitations on the pcie lanes

Are you passing just the disks or the sata controller through to the TrueNAS VM? Could be where your problem is perhaps?

I don't know this for a fact, but I would surmise that the host listens to port 53 to handle DNS replies from external servers?

By default, all hardware, including the GPU is emulated in the VM. So you could have two hosts with same spec except that one has a basic GPU and the other has some kind of mega-performance GPU but a VM running on either host will have the same GPU performance, ok for general use but not good...

You can only 'pass-through' a physical video card to a single active VM at a time (in general, there are some very expensive cards that can be shared) If you're not using hardware pass-through, the VM uses emulated video hardware - it doesn't matter what video cards are physically present in the...

I would advise that you simplify things to begin with and move onto more involved setups later. Forget about bonded and/or multiple interfaces for now - there's very little advantage in a simple home lab setup anyway. It looks like you're on a regulation home lan with an ISP modem/router on...

I think you can only have one gateway, if you want to send external traffic on the second subnet/nic you will need to define some rules using IP tables to make this work.

Yes, that syntax looks correct.

Did you try? IP Address 10.10.10.30 Network Mask 255.255.255.0 Broadcast 10.10.10.255 Gateway 10.10.10.1 Name Servers 8.8.8.8

DSM gateway should be 10.10.10.1

there could be a lot of reasons why ... can VM107 ping it's gateway (10.32.0.14)? can VM107 reach the internet (e.g ping 1.1.1.1) is 10.32.0.13 a VM or a physical device? if it's another VM is it attached to the same bridge with the same VLAN tag, does 10.32.0.13 ping from the gateway, etc

In what way does it 'not work' - are you using DHCP and it doesn't get a lease or are you using static IP addresses? All that is normally required is to make vmbr0 vlan-aware and then put the relevant vlan tag on the VM config.

You need to have a DHCP server on your network. There are lots of possibilities, depends on your use case. Simplest setup would be to create a small lxc container and install isc-dhcp-server. If you're running windows server, you can add the DHCP role and do it that way. Quite often, the...