novox/mesh-lab
3
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Say what holds the address, rather than that it is held

Browse Source 
dnsmasq cannot bind 127.0.0.54 and the module's own comment claims that address
is free. Which of those is wrong is the question, and naming the holder answers
it — assuming would be issue 012's mistake, where two things changed and the
plausible one was blamed.
This commit is contained in:
jschoubben
2026-08-31 13:24:40 +02:00
parent 89b6dd6080
commit a6480bbd88
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
test/integration/mesh.test.ts
+3 -1
View File
@@ -1403,7 +1403,9 @@ test("a service is reached by a name under the machine it runs on", {
`journal:\n${(await on(machine, `journalctl -u dnsmasq -n 25 --no-pager`)).out}\n` + `journal:\n${(await on(machine, `journalctl -u dnsmasq -n 25 --no-pager`)).out}\n` +
`its config:\n${(await on(machine, `cat /etc/dnsmasq.conf`)).out}\n` + `its config:\n${(await on(machine, `cat /etc/dnsmasq.conf`)).out}\n` +
`what the mesh wrote:\n${(await on(machine, `cat /etc/mesh-resolver/nodes.conf`)).out}\n` + `what the mesh wrote:\n${(await on(machine, `cat /etc/mesh-resolver/nodes.conf`)).out}\n` +
`resolv.conf:\n${(await on(machine, `cat /etc/resolv.conf`)).out}`); `resolv.conf:\n${(await on(machine, `cat /etc/resolv.conf`)).out}\n` +
`what holds a loopback address:\n` +
`${(await on(machine, `ss -lntup | grep 127.0.0 || echo none`)).out}`);
} }
// Through the machine's own resolver, by the path an application actually takes: nsswitch, then // Through the machine's own resolver, by the path an application actually takes: nsswitch, then