My local network is 192.168.69.*, with the Unraid server at 192.168.69.99. The DHCP server is a Pi-hole at 192.168.69.13.

I recently tried to set up a new VM, only to find that it could not see the network. I found that Unraid had created something at 192.168.122.1, and was running its own DHCP server on that, meaning the VM was getting an IP address of 192.168.122.196 and could not see or be seen by anything else.

I changed my Mac's subnet mask to 255.255.0.0 so I could see what was going on, and nmap found that 192.168.122.1 was exposing the same ports as 192.168.69.99's VMs — I could VNC into each one.

Existing VMs behave correctly, and I can't see anything in the new VM setup that tells Unraid to do this.

How do I stop Unraid from trying to be a DHCP server? I have a DHCP server, and a second one on some random subnet just breaks things!

Edited May 12May 12 by ElectricBadger
Forgot to finish a sentence 🤦‍♂️

can't answer as i lack some details about your setup but i'd look at network source in the vm settings. For example if you are using bridging for your unraid network interface, you would want to have br0 as your network source in your vm settings.

Thanks — both are network source virbr0, and network model virtio-net. I don't even have br0 in the list!

Enable bridging for eth0 (Network Settings) and then select br0 for the VM

@ElectricBadger if you have your VM configured to use virbr0 then this means it acts as if it is behind a NAT and foes not see your local network directly (and thus the behaviour you describe). You need to have it configured to a different option to have direct access to the LAN. Typically this means br0 rather than virbr0 but it does not look like you have bridging enabled in the Unraid network settings? Maybe configuring one of the ethX options will work - not sure.

You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one zip file) to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

@JorgeB Thanks — that's fixed it!

Bizarre that the other two VMs were getting the right IP address despite appearing to use virbr0, but now that I've enabled bridging on the interface, they seem to have changed to br0 without any manual intervention!

I wonder if they were using bridging all along?

2 hours ago, ElectricBadger said:

Bizarre that the other two VMs were getting the right IP address despite appearing to use virbr0

That's very weird, but glad it's resolved.