Skip to content

Conversation

@jukkar
Copy link
Owner

@jukkar jukkar commented Mar 22, 2018

Link-Local multicast name resolution (LLMNR) is a multicast DNS technique used in Windows networks. This PR adds support for LLMNR client functionality. What this means in practice, is that all the DNS queries (unless it is mDNS query) are sent to [ff02::1:3]:5355 or 224.0.0.252:5355 instead of unicast DNS server port 53.
This PR depends on mDNS PR zephyrproject-rtos#1341 so there are couple of extra patches here that belong to that mDNS PR.

jukkar added 2 commits March 22, 2018 15:27
This implements LLMNR client from RFC 4795. This means that caller
is able to resolve DNS resource records using multicast DNS.
The LLMNR is used in Windows networks.

Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
By default the LLMNR is disable in this sample. You can enable
it by setting CONFIG_LLMNR_RESOLVER=y

Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
@jukkar jukkar changed the title LLMNR client LLMNR client [Obsolete branch, this is already merged upstream] Jul 20, 2018
@jukkar jukkar closed this Jul 22, 2018
jukkar pushed a commit that referenced this pull request Jun 22, 2020
This makes the gatt metrics also available for
gatt write-without-rsp-cb so it now prints the rate of each write:

uart:~$ gatt write-without-response-cb 1e ff 10 10
Write #1: 16 bytes (0 bps)
Write #2: 32 bytes (3445948416 bps)
Write #3: 48 bytes (2596929536 bps)
Write #4: 64 bytes (6400 bps)
Write #5: 80 bytes (8533 bps)
Write #6: 96 bytes (10666 bps)
Write #7: 112 bytes (8533 bps)
Write #8: 128 bytes (9955 bps)
Write #9: 144 bytes (11377 bps)
Write #10: 160 bytes (7680 bps)
Write #11: 176 bytes (8533 bps)
Write #12: 192 bytes (9386 bps)
Write Complete (err 0)
Write #13: 208 bytes (8533 bps)
Write #14: 224 bytes (9244 bps)
Write #15: 240 bytes (9955 bps)
Write #16: 256 bytes (8000 bps)

Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
@jukkar jukkar deleted the llmnr-client branch February 29, 2024 08:20
jukkar pushed a commit that referenced this pull request Mar 13, 2024
D9/SCK pin is #9 pin, not #0.

Signed-off-by: TOKITA Hiroshi <tokita.hiroshi@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants