This message was deleted.

I will first assume you have no way to change this configuration as it makes no sense. Is there a switch between these machines? If this is what you get then build a router on harvester one interface to internet and then create another interface for your virtual machines to attach to. Then your virtual router can handle all the traffic and networking for your virtual machines and will use your Internet 100%.

Thanks for the suggestion regarding the router, I didn't think about virtualising it. In terms of this type of configuration, yes, any private NICs on the host are connected to a switch. In the simplest setup, I can provision Harvester nodes using only their private interfaces, but then there's no internet connectivity, hence a separate router in the first attempt, as without it, I'd be essentially doing an air-gapped install Having separate public NICs may not be optimal in this situation, but I don't think it's unusual as part of standard offerings by bare-metal providers, (in this case, OVH), as it allows a simple way to sell individual servers with x amount of allocated internet bandwidth and x amount of private bandwidth.

More question's: • What is your goal? What do you need to accomplish with this setup? • Do you have access to the switch or switches? • How many nodes do you have? • Do the public interfaces also land on a switch or are they direct? • Does this provider support BGP with private ASN? • Will this provider route additional IPs to you or allow you to announce via bgp to them, or provide a completely different network setup? • I have a design in my head that should work well for you, sorry for all the questions.

Harvester VM network now only supports VLAN based network, or sharing the management-network. The VLAN based network means it needs L2 broadcast and futher with router; Harvester does not support L3 IP based VM network now. When each NODE has an public IP-reachable NIC (or bonding), and wish to utilize the L3 network directly, it has many challenges: (1) How to allocate the IP to certain VM, each NODE may carry many VMs (2) It will mean, Harvester needs to create another layer of network to allocate private IP, and use the public IP as the default router in each NODE. There are such solutions, e.g. the VxLan, but it is planned to Harvester v1.3.0 or later.