cannot ping outside proxmox vm

J

janot928

New Member
Mar 13, 2022
2
0
1
29
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.)
 
hi,

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

janot928 said:
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.)
Click to expand...
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 ;)
 
janot928 said:
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)
Click to expand...
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).
 
Last edited:
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 ?
 
janot928 said:
@oguz i can't see any option to do such a thing inside truenas is there any way to do that inside PVE ?
Click to expand...
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
 
Sry for necro-posting but I came across this post by googling so this is just for people who have the same problem.

Setup the same as OP: TrueNAS Scale on bare metal, Proxmox VE as VM and then Containers/VMs in this Proxmox VM.
My server only has one HBA and no other SATA ports so my boot disk is also connected to the HBA so passing it through to an VM is not an option.

What the OP and I did when creating the Proxmox VM in TrueNAS (and if you landed here by searching probably you too), was to just attach the TrueNAS default network interface to the VM. This leads to exactly the scenario that the Proxmox VM itself will be able to communicate normally with the Gateway and local network but all CT/VMs inside Proxmox will only be able to ping each other and the Proxmox VM itself but not be able to reach the Router or LAN outside Proxmox.

Steps to fix it:
Don't worry. Changing Interfaces and saving them will not apply the changes yet, TrueNAS Scale will require you to "Test Changes" so you will not lose connectivity and if you mess something up entirely the changes will revert after 60 seconds.
  1. In the TrueNAS GUI go to "Network".
    • Find the Interface that TrueNAS is currently using to be able to reach your Gateway (probably the only Interface with an IP assigned - the IP should be the one you use to connect to the GUI)
    • Remember/note down the Interface name and the assigned IP.
    • Edit the Interface and remove the IP from the Aliases.
    • Save the Interface change.
  2. Add a new Interface of type Bridge
    • Name: Whatever (e.g. br0) and
    • Member: Select the Interface you remembered/noted down in Step 1.
    • Not neccessary but makes things easier imo: Disable DHCP and as Alias set the IP you remembered/noted down in Step 1.
    • Save the Interface
  3. "Test Changes" - if everything was done correctly and you chose the same IP in the new Interface as the one you removed from the other Interface, then it should be a very quick reload and the you should be able to "Save Changes".
    If you fucked up then it will take 60 seconds and revert what you have done.
    If you chose a different IP, you might need to directly enter that IP in your browser (and "Save Changes" within the 60 seconds before everything reverts!) as I had trouble with redirections before.
  4. Go to "Virtualization" select your Proxmox VM and in "Devices" edit the NIC (or add one if there is none)
    • Adapter Type: VirtIO
    • NIC To Attach: The new Bride Interface you just created.
    • Save
  5. Restart your Proxmox VM.
    That should do it. All VMs/CTs in Proxmox should be able to communicate with your LAN and Gateway now.
 
Last edited:
  • Like
Reactions: waltar
You must log in or register to reply here.
Top Bottom