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 ifs and menus.)

Defaults¶

No defaults. Implicitly defaults to n.

Symbols selected by this symbol¶

NET_IPV6_MLD if NET_IPV6

Kconfig definition¶

At <Zephyr>/subsys/net/lib/dns/Kconfig:167

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:34 → <Zephyr>/subsys/Kconfig:34 → <Zephyr>/subsys/net/Kconfig:89 → <Zephyr>/subsys/net/lib/Kconfig:8

Menu path: (Top) → Sub Systems and OS Services → Networking → Link layer and IP networking support → Network Protocols

config LLMNR_RESPONDER
    bool "LLMNR responder"
    select NET_IPV6_MLD if NET_IPV6
    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.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)