-
CONFIG_LLMNR_RESPONDER¶
LLMNR responder
Type: bool
Help¶
This option enables the LLMNR responder support for Zephyr. It will listen well-known address ff02::1:3 and 224.0.0.252. Currently this only returns IP address information. You must set CONFIG_NET_HOSTNAME to some meaningful value and then LLMNR will start to respond to <hostname> LLMNR queries. Note that LLMNR queries should only contain single-label names so there should be NO dot (“.”) in the name (RFC 4795 ch 3). Current implementation does not support TCP. See RFC 4795 for more details about LLMNR.
Direct dependencies¶
NET_HOSTNAME_ENABLE && NETWORKING
(Includes any dependencies from if’s and menus.)
Defaults¶
No defaults. Implicitly defaults to n.
Symbols selected by this symbol¶
Kconfig definition¶
At subsys/net/lib/dns/Kconfig:160
Included via Kconfig:10 → Kconfig.zephyr:39 → subsys/Kconfig:24 → subsys/net/Kconfig:84 → subsys/net/lib/Kconfig:11
Menu path: (top menu) → Networking → Network Protocols
config LLMNR_RESPONDER
bool
prompt "LLMNR responder" if NET_HOSTNAME_ENABLE && NETWORKING
select NET_IPV6_MLD if NET_IPV6 && NET_HOSTNAME_ENABLE && NETWORKING
depends on NET_HOSTNAME_ENABLE && NETWORKING
help
This option enables the LLMNR responder support for Zephyr.
It will listen well-known address ff02::1:3 and 224.0.0.252.
Currently this only returns IP address information.
You must set CONFIG_NET_HOSTNAME to some meaningful value and
then LLMNR will start to respond to <hostname> LLMNR queries.
Note that LLMNR queries should only contain single-label names
so there should be NO dot (".") in the name (RFC 4795 ch 3).
Current implementation does not support TCP.
See RFC 4795 for more details about LLMNR.
(Definitions include propagated dependencies, including from if’s and menus.)