Jason Rhinelander

Eventually: ``` systemd-resolve --interface=wlp2s0 --set-dns=127.3.2.1 ``` worked but there must be a better way. (systemd-resolve is the old name of resolvectl)

I *think* that we might be able to change the systemd-resolv file to match lokitun* devices, and set: ``` DNS=127.3.2.1 Domains=~. ``` to make it take priority, but will take...

We *do* have systemd's stuff in place, but it isn't working as expected.

> Any additional dependencies to build this branch? Just libsystemd-dev (or whatever that may be called in RPM land -- perhaps systemd-devel?), but that was already an optional dependency.

I believe this issue is either no longer occurring, or is addressed in #1969 (at least, while testing that PR, I've observed routes getting removed). This likely needs confirmation before...

This has been a long-term issue (#604); we've been having some discussion recently about ways to address it (mainly we need a heuristic to figure out we went through a...

We have reason to believe this issue is fixed in the upcoming 0.9.10 release (which has several changes and fixes around how we detect interfaces and interface changes), so I...

> ... Riffle ... This paper is describing a mixnet, which is fundamentally different than what Lokinet offers. While mixnets are an interesting concept for certain use cases, Lokinet's explicit...

> The queries were sent on all interfaces You specifically reverted the DNS setting that prevents this. > i see, we'll have to block snode and loki gtld explicitly on...

So this issue is caused, apparently, by https://github.com/systemd/systemd/issues/20485 merged sometime between 247 and 249. (@majestrate is on 247.3, and doesn't see it, while my router is on 250.3 and does)....