From 7e783b0b3df7926b4ef9a24a3ceb569f768bde8e Mon Sep 17 00:00:00 2001 From: Joachim Nilsson Date: Tue, 5 May 2020 08:36:59 +0200 Subject: [PATCH] Slight clarification, your patch is welcome Signed-off-by: Joachim Nilsson --- README.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 83b5afb..6335494 100644 --- a/README.md +++ b/README.md @@ -46,12 +46,13 @@ GNU/Linux, use `mdns-scan` or Wireshark to verify your setup. Other operating systems have their own set of tools for mDNS-SD and mdnsd may not even have a place there. -mdnsd uses the system routing table, specifically the default (unicast) -route, to determine the default interface to use. To run on systems -without a default route, e.g. a link-local only system, use `-i IFACE`. -Starting mdnsd early in the boot process means the system may not yet -have acquired an IP address, or the interface itself may not even exist -yet, in which case `-p` may likely also help. +mdnsd currently only runs on one system interface. To figure out which +to use, the system routing table is queried, specifically the default +route. To run on systems without a default route, e.g. a link-local +only system, use `-i IFACE`. Starting mdnsd early in the boot process +means the system may not yet have acquired an IP address, or the +interface itself may not even exist yet, in which case `-p` may likely +also help. See the file [API.md][] for pointers on how to use the mDNS library.