Problem with DHCP updated IP addresses as swarm nodes

[tetsuos]

On my network, our PCs occasionally change IP address due to DHCP lease expiry. It seems that when this happens, the IP address in the V-ray Swarm service does not follow the newly acquired address. This causes render nodes to fail to connect until the swarm service is deactivated and reactivated manually. Is this a known bug, or am I doing something wrong?

[tetsuos]

I am using the most recent version of V-ray for SketchUp.

[delineator]

huh....I've never noticed our dropping, though I have to recheck my tables and see what the expiry time frame is. Do you us the tagging? Also, is the network discovery set to auto?

[tetsuos]

No I don't have any of the nodes tagged, but network discovery is set to auto. In the web GUI the problem is obvious when it happens, as the IP address shown for the problem node does not match the currently assigned address, although the node does still appear. I haven't seen this on my Mac OS nodes, only windows (all on Win10), but it could be coincidence as I only have 2 Mac nodes. I'm guessing that it's due to the DHCP lease expiring (any being assigned to another device), since I can't think of any other reason why the IP wouldn't match after a long time.

[Tania.Metodieva]

Thank you for your feedback. This seems to be an issue in Swarm and it has been reported to the developers for further investigation.Meanwhile as a workaround you can either restart the Swarm service when the issue appears or configure a DHCP reservation in your DHCP server in order to use a permanent IP address assignment.

[tetsuos]

That's exactly the method I have been using as a workaround for now.