Am Mon, 10 Apr 2017 12:46:02 +0200
schrieb Lennart Poettering :
> On Mon, 10.04.17 12:41, Kai Krakow (hurikha...@gmail.com) wrote:
>
> > > Queries and responses in LLMNR are supposed to be delayed by a
> > > random time up to 100ms according to the RFC. See:
> > >
> > >
On Mon, 10.04.17 13:50, Kai Krakow (hurikha...@gmail.com) wrote:
> > > According to RFC2119, the terminology SHOULD suggests that systemd
> > > could maybe make this configurable? Maybe taking the proper
> > > warnings for this configuration into account for administrators...
> > > Still you
On Mon, 10.04.17 12:41, Kai Krakow (hurikha...@gmail.com) wrote:
> > Queries and responses in LLMNR are supposed to be delayed by a random
> > time up to 100ms according to the RFC. See:
> >
> > https://tools.ietf.org/html/rfc4795 section 2.7, and section 7.
> >
> > If you add up the delay for
Am Mon, 10 Apr 2017 10:26:14 +0200
schrieb Lennart Poettering :
> On Sun, 09.04.17 19:22, Paul Freeman (p...@coredev.org.uk) wrote:
>
> > Hi,
> > We are seeing high latency (>100ms) when resolving local names via
> > LLMNR.
>
> Queries and responses in LLMNR are
On Sun, 09.04.17 19:22, Paul Freeman (p...@coredev.org.uk) wrote:
> Hi,
> We are seeing high latency (>100ms) when resolving local names via
> LLMNR.
Queries and responses in LLMNR are supposed to be delayed by a random
time up to 100ms according to the RFC. See:
Hi,
We are seeing high latency (>100ms) when resolving local names via
LLMNR.
systemd v233 / Gentoo
There appears to be a large delay between systemd-resolved receiving
the udp query over 127.0.0.53:53 and when it dispatches the LLMNR query:
18:29:38.752644 clock_gettime(CLOCK_BOOTTIME,