-
Hey, as soon as i try to create a hostile portal ap i get this traceback error:
Traceback (most recent call last):
File "/usr/lib/python3.12/configparser.py", line 767, in get
value = d[op…
-
### What is the issue?
When connected to Tailscale, machines can still resolve and connect to machines on their local subnets that use LLMNR or mDNS to resolve `*.local` system names that aren't in D…
-
LLMNR is schedule to be deprecated by MS in favour of mDNS.
Currently, LLMNR works as advertised for me when it comes resolving Windows 10 hosts, but I think that the plan is for this to be turned …
ermo updated
2 months ago
-
### systemd version the issue has been seen with
systemd-resolved 255.4-1ubuntu8.4 amd64
### Used distribution
Ubuntu 24.04
### Linux kernel version used
6.8.0-45-generic
### CPU archite…
-
### What is the issue?
Related to #2697, except I *want* MagicDNS to have the highest priority (because I run some services that are exposed only over Tailscale). I could live with either one winnin…
-
-
### Port, board and/or hardware
rp2040
### MicroPython version
mp 1.22.2
### Reproduction
There isn't a code sample, the feature is built-in in the firmware.
### Expected behaviour
…
-
First of all, thanks for great work.
So, may be it's worst to add to ksmbd LLMNR name resolution (IPv4, IPv6, multicast) and WS-Discovery neighborhood showng/browsing (WSDD2 daemon written at C - h…
-
**systemd version the issue has been seen with**
> 248
**Used distribution**
> Fedora 34
**Linux kernel version used** (`uname -a`)
> `5.12.5-300.fc34.x86_64`
**Expected behaviour you didn…
-
**Is your feature request related to a problem? Please describe.**
Yes, described in #23494. LLMNR eats also queries to single label names, which are not wanted to be resolved by LLMNR. It should not…