systemd-resolved: find the links to give back from resolved, never a routed one; answer-within is a config value (issue 1981 review)
The guard kept the links it had turned off in memory, so a VPN link turned off before it was routed got its default route back, and a guard restarted behind a sign-in page gave nothing back. It now reads them from resolved each round and skips a link whose domains are all routing domains. How long a mesh resolver is given to answer is the config value answer-within.
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
{
|
||||
"module": "systemd-resolved",
|
||||
"version": "0.1",
|
||||
"version": "0.2",
|
||||
"upgrade": {
|
||||
"policy": "record",
|
||||
"why": "the machine's names: a build that breaks this resolver stops every name resolving on a machine a person works on, the bus's included, and then neither the gate's rollback nor a push reaches it (hq ADR 0236, ADR 0247)"
|
||||
@@ -81,6 +81,14 @@
|
||||
"kind": "unit"
|
||||
}
|
||||
},
|
||||
{
|
||||
"id": "answer-within",
|
||||
"type": "file",
|
||||
"path": "/etc/node-resolver/answer-within",
|
||||
"mode": "0644",
|
||||
"trusted": false,
|
||||
"template": "files/answer-within"
|
||||
},
|
||||
{
|
||||
"id": "guard",
|
||||
"type": "process",
|
||||
@@ -109,5 +117,14 @@
|
||||
]
|
||||
}
|
||||
]
|
||||
},
|
||||
"config": {
|
||||
"answer-within": {
|
||||
"type": "number",
|
||||
"description": "How long, in seconds, the guard gives one of the mesh's resolvers to answer its question each round (novox/hq issue 1981): while none answers within it, a network's own servers answer every name, so a sign-in page can be found. 1 suits a tunnel's usual round trip; a slower link (tethered, abroad) needs more, or the guard takes a slow mesh for a silent one.",
|
||||
"minimum": 0.2,
|
||||
"maximum": 5,
|
||||
"default": 1
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user