2018-06-15 07:55:48 +00:00
|
|
|
menu "mDNS"
|
|
|
|
|
2019-01-25 16:10:53 +00:00
|
|
|
config MDNS_MAX_SERVICES
|
|
|
|
int "Max number of services"
|
|
|
|
range 1 64
|
|
|
|
default 10
|
|
|
|
help
|
|
|
|
Services take up a certain amount of memory, and allowing fewer
|
|
|
|
services to be open at the same time conserves memory. Specify
|
|
|
|
the maximum amount of services here. The valid value is from 1
|
|
|
|
to 64.
|
|
|
|
|
2019-11-02 20:32:52 +00:00
|
|
|
config MDNS_TASK_PRIORITY
|
|
|
|
int "mDNS task priority"
|
|
|
|
range 1 255
|
|
|
|
default 1
|
|
|
|
help
|
|
|
|
Allows setting mDNS task priority. Please do not set the task priority
|
|
|
|
higher than priorities of system tasks. Compile time warning/error
|
|
|
|
would be emitted if the chosen task priority were too high.
|
|
|
|
|
2020-04-30 06:17:50 +00:00
|
|
|
config MDNS_TASK_STACK_SIZE
|
|
|
|
int "mDNS task stack size"
|
|
|
|
default 4096
|
|
|
|
help
|
|
|
|
Allows setting mDNS task stacksize.
|
|
|
|
|
2019-11-02 20:32:52 +00:00
|
|
|
choice MDNS_TASK_AFFINITY
|
|
|
|
prompt "mDNS task affinity"
|
|
|
|
default MDNS_TASK_AFFINITY_CPU0
|
|
|
|
help
|
|
|
|
Allows setting mDNS tasks affinity, i.e. whether the task is pinned to
|
|
|
|
CPU0, pinned to CPU1, or allowed to run on any CPU.
|
|
|
|
|
|
|
|
config MDNS_TASK_AFFINITY_NO_AFFINITY
|
|
|
|
bool "No affinity"
|
|
|
|
config MDNS_TASK_AFFINITY_CPU0
|
|
|
|
bool "CPU0"
|
|
|
|
config MDNS_TASK_AFFINITY_CPU1
|
|
|
|
bool "CPU1"
|
|
|
|
depends on !FREERTOS_UNICORE
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
config MDNS_TASK_AFFINITY
|
|
|
|
hex
|
|
|
|
default FREERTOS_NO_AFFINITY if MDNS_TASK_AFFINITY_NO_AFFINITY
|
|
|
|
default 0x0 if MDNS_TASK_AFFINITY_CPU0
|
|
|
|
default 0x1 if MDNS_TASK_AFFINITY_CPU1
|
|
|
|
|
|
|
|
config MDNS_SERVICE_ADD_TIMEOUT_MS
|
|
|
|
int "mDNS adding service timeout (ms)"
|
|
|
|
range 10 30000
|
|
|
|
default 2000
|
|
|
|
help
|
|
|
|
Configures timeout for adding a new mDNS service. Adding a service
|
|
|
|
fails if could not be completed within this time.
|
|
|
|
|
2021-03-05 17:12:51 +00:00
|
|
|
config MDNS_STRICT_MODE
|
|
|
|
bool "mDNS strict mode"
|
|
|
|
default "n"
|
|
|
|
help
|
|
|
|
Configures strict mode. Set this to 1 for the mDNS library to strictly follow the RFC6762:
|
|
|
|
Currently the only strict feature: Do not repeat original questions in response packets
|
|
|
|
(defined in RFC6762 sec. 6).
|
|
|
|
Default configuration is 0, i.e. non-strict mode, since some implementations,
|
|
|
|
such as lwIP mdns resolver (used by standard POSIX API like getaddrinfo, gethostbyname)
|
|
|
|
could not correctly resolve advertised names.
|
|
|
|
|
2019-11-02 20:32:52 +00:00
|
|
|
config MDNS_TIMER_PERIOD_MS
|
|
|
|
int "mDNS timer period (ms)"
|
|
|
|
range 10 10000
|
|
|
|
default 100
|
|
|
|
help
|
|
|
|
Configures period of mDNS timer, which periodically transmits packets
|
|
|
|
and schedules mDNS searches.
|
|
|
|
|
2021-06-30 16:39:29 +00:00
|
|
|
config MDNS_NETWORKING_SOCKET
|
|
|
|
bool "Use BSD sockets for mdns networking"
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
Enables optional mdns networking implementation using BSD sockets
|
|
|
|
in UDP multicast mode.
|
|
|
|
This option creates a new thread to serve receiving packets (TODO).
|
|
|
|
This option uses additional N sockets, where N is number of interfaces.
|
|
|
|
|
2021-09-13 11:33:02 +00:00
|
|
|
config MDNS_MULTIPLE_INSTANCE
|
|
|
|
bool "Multiple instances under the same service type"
|
|
|
|
default y
|
|
|
|
help
|
|
|
|
Enables adding multiple service instances under the same service type.
|
|
|
|
|
2018-06-15 07:55:48 +00:00
|
|
|
endmenu
|