This message was deleted.

what network are you using to create your VMs? It sounds like they might not be getting an IP from your network. Which might be part of the problem for both 1 and 2

Based on the guide it seems a DHCP server is a must. I don't have DHCP. https://docs.harvesterhci.io/v1.0/networking/harvester-network/

You can use your Harvester node as a jump host to your VM:

ssh –J rancher@<harvester_vip_address> <image_username>@<vm_ip_address>

Smoother if you've added your public SSH key to Harvester nodes and VMs so no password required

Unless your Harvester nodes with one network interface are connected to a VLAN capable network switch, practically, you're only going to be able connect to VMs which are not in the same network - in your case 10.255.156.0/24. 1. have you created a VLAN 1 network in your Harvester cluster (see image 1)? 2. have you connected your VMs to that network (see image 2)? 3. have you configure your VMs with static IPs in that network?

Thanks for the responses. I have configured a vlan, but since I only have one interface card, for now the vlan is on the management interface. I have not been able to configure a static IP. I tried using Network Data configuration in Cloud Config when creating the VM, but it does not seem to take.

So - in the switch connected to your Harvester nodes, do you actually have VLAN 30 tagged on the network interfaces your Harvester nodes are connected to?

Most likely not. I did not setup the physical network.

If you just want the network that the Harvester node is connected on to get into the VMs you must create a Network in Harvester with the special VlanID of 1.

ok. I didn't catch that the first time. I will change the VlanID to 1.

Yeh - sorry. It looks like I wrote the sentence in one way and then changed it, but did not remove the 'not'. It should say "Unless your Harvester nodes with one network interface are connected to a VLAN capable network switch, practically, you're only going to be able connect to VMs which are in the same network - in your case 10.255.156.0/24."

well, I just solved that issue. you need to create another network, set mode to bridge, use network parameters matching your host network and it's working.

You mean you've put to subnets on the same Ethernet collision-zone? Yeh, that'll work but routing can be a bit exciting 😉