Scenario: In general a ubuntu machine (called server) runs in a network and gets an IP from it. Due to testing, sometimes a windows machine (client) is physical connected to the ubuntu machine exclusively. (Because the server is mounted on a car trailer and there is sometimes no existing network availible.)
It should run without any regular effort on the server.
Situation now: Because noone runs a DHCP server both will get a zeroconf (169.254.x.x) address. The problem is that Windows don't resolve names via mDNS otherwise I could simply use avahi.
My thoughts for solutions are
- server side
- after DHCP discover timout start an own DHCP server serving an IP for the client
- use static IP (zeroconf subnet) on DHCP discover timeout (thus client knows it)
- windows side
- install mDNS or Bonjour :( respectively
- both sides
- use static IPs (annoys and error-prone at the client side)
Do I consider all sorts of solutions? If yes which one seems to be the best? Ideally I don't want to install extra software on windows and don't set a static IP on the client all the time. So setting a static zeroconf address on the server seems to be the best?