On 9/18/24 11:39 AM, bd730c5053df9efb via Users wrote:
Hi Laine! Thank you very much for your answer, it does make perfect sense but my use case is much simpler. The two servers are two samba 4 ad domain controllers and I have to demote one of them remove it from the net and then add another one with the same ip address as the demoted one. All the test is between these two servers, the host workstation doesn't get involved in this test and I can't change their ip addresses. I had considered created an isolated network in the 192.168.1.0/24 address space and keep the manually set address on the servers in the 192.168.0.0/24 address space but I'm not quite sure that will work. I I needed to test a workstation I could add to the test another guest workstation also in the 192.168.0.0/24 address space, but it wont be the host.
Well, if the two servers have statically configured IP addresses (which I guess they do, since they're servers :-P) then you can create a "very isolated" network, which is a network that has no <ip> section at all. Then the guests can communicate with each other (IPv4 only, there is another attribute that needs to be added to enable IPv6 in this case) but can't get to the host (or beyond, of course). Keep in mind that means they also won't have access to other infrastructure things, e.g. the DNS server.
https://libvirt.org/formatnetwork.html#network-config-with-no-gateway-addresses
(Sorry if the "addresses" after the final - is split to the next line. my email client autowraps everything, and I've never found a simple way to turn it off :-))
