cannot ping outside proxmox vm

[janot928]

Hi everyone,
I have recently remade my home NAS. The setup is the following :

Truenas core as the "root OS"
Proxmox on a VM inside truenas
vm 1 (windows)
vm 2 (kemp)
CT 1 ( ubuntu)

Everything is on the same network : 192.168.69.0/24, gateway and DNS are both 192.168.69.254
-I can see the VM from my router (ip and shows as connected),
-I can ping and download from proxmox VM
-I can ping in-between VM
The problem :
-I cannot ping from a VM to an ip "beyond" proxmox
-I cannot ping from my main computer to a VM

How can i troubleshoot and fix that ?

(consider me a complete noob when it comes to networking.)

 

[oguz]

hi,

i'm not sure about the truenas setup, how exactly are you running the PVE inside that?

Everything is on the same network : 192.168.69.0/24, gateway and DNS are both 192.168.69.254
-I can see the VM from my router (ip and shows as connected),
-I can ping and download from proxmox VM
-I can ping in-between VM
The problem :
-I cannot ping from a VM to an ip "beyond" proxmox
-I cannot ping from my main computer to a VM

How can i troubleshoot and fix that ?

(consider me a complete noob when it comes to networking.)

it sounds like your NAS might be creating issues in that case.

normally when PVE is in a nested virtualization setup in a different hypervisor (like vmware, virtualbox or hyper-v) you might have to enable something called "promiscuous mode" or "mac spoofing" (not sure how it's called in truenas). this is done to allow different mac addresses (of your VMs) to utilize the NIC of your host OS (in this case truenas?).

but what is your goal by running the PVE inside the truenas? you could do it the other way around as well

 

[Dunuin]

I have recently remade my home NAS. The setup is the following :

Truenas core as the "root OS"
Proxmox on a VM inside truenas
vm 1 (windows)
vm 2 (kemp)
CT 1 ( ubuntu)

Why? TrueNAS Core with its bhyve is a very rudimentary hypervisor and nested virtualization can cause problems and additional overhead so that generally should only be used for testing purposes and not for productive systems. Would be way more useful to have a bare metal PVE host with TrueNAS Core as a VM (and that best with PCI Passthrough of a HBA card).

 

[janot928]

Why truenas first and then proxmox on top? it's simply because i want a NAS first and then have a few things on top. Passing trough each disk one by one in command line ... I've done it once, i do not want to do it again.

The problem is that i would like to have Kemp as a reverse proxy (easy GUI, and enough bandwidth for my server and a nextcloud), but I haven't found a way to import the kemp image into truenas.

@oguz i can't see any option to do such a thing inside truenas is there any way to do that inside PVE ?

 

[oguz]

@oguz i can't see any option to do such a thing inside truenas is there any way to do that inside PVE ?

are you talking about the mac spoofing option or importing an image?

inside PVE you can import VM disks or OVF files [0]. though i've never heard of "kemp" and not sure what kind of image they use, so you'll have to look at that. if you can get a raw disk out then it should be importable.

as for your network issue (which was the original reason for the thread?), you'll need to check your network configuration on the truenas side since you insist using that on top

[0]: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_importing_virtual_machines_and_disk_images