Quote:
Originally Posted by jhersh
While what you describe can work, the simpler configuration that teams are expected to use when at an event in the pits is to set all devices to DHCP + Link Local (the default for most devices) and use mDNS to find them even when they get a 169.254 address.
|
Aha! I want to highlight this portion of your remark, because I didn't fully understand it while at the regional. The DS and the Robo Rio both apparently are set such that if there is no DHCP server, they fall back to 'link local' (also apparently aka stateless address autoconfiguration). I'm not particularly familiar with that mode.
But if you can persuade all your other devices to do the same, and all your software can use names, you should indeed be in great shape. (A lazy 5 minute Google and read of the M1011 manual suggests possibilities, but not clear paths to doing that. The M1011 appears to let you set *two* addresses; not sure which gets the 'axis-camera.local' name. The Pi can use avahi to set a link local address. It's not clear to me if there is an easy or clean way to have the dhcp server fall back. I suspect another 20 minutes of Googling might help...)
Quote:
Originally Posted by Mr. Lim
I'd have to agree with jhersh in saying that the best situation is to get all devices on dynamic IPs via DHCP + mDNS, then address them only by their hostnames.
|
Yeah, I agree. I think this is a good change, and hopefully once the bumps are ironed out, the teams will reap the benefits into the future.
Quote:
Originally Posted by Mr. Lim
|
Just to confirm - they both do, and it's nice. It's particularly nice because the mDNS continues to work in both static and DHCP modes.
Cheers,
Jeremy