Closed dh1tw closed 4 years ago
After investigating this issue, I think I will leave it as is. The web server (remoteRotator web
) will just ignore a rotator with the same name.
Since MDNS is also not always reliable, a check on startup would take considerable time. Let's trust in the user to name the remoteRotator server lan
instances properly. In the worst case, duplicate instances just get ignored.
On startup of a rotator (
remoteRotator server lan --name=myRotator
) it should be checked that this rotator does not exist on the lan. Otherwise there will be collisions between the two rotator instances.This applies only the the
lan
transport option. This check is already included in thenats
transport.