Repository navigation
Shepherd 1.1.0
A setting that could only be reached by editing shepherd.toml is now in the portal, and it is a
per-device setting as well as a network-wide one: the one device on a network that cannot cope with
a withheld AAAA answer can be handed the real one on its own card, while nothing changes for the
rest.
Added
-
AAAA filtering is a portal setting, and can be set per device.
dns.filter_aaaawas
reachable only by editingshepherd.tomland restarting, which is the wrong place for it: the
device that needs it is found by watching the query log, and nobody watching a query log should
have to go and edit a file. The three positions (auto,on,off) are now on
Upstreams -> IPv6 answers, with the mode and whether outbound IPv6 is reachable shown
separately, so "automatic" says what it has decided and why. A mode saved there is kept in
<data_dir>/settings.jsonand wins overdns.filter_aaaafrom then on, with no restart;
dns.filter_aaaaremains the value for a first run.Each device also has its own switch, on its card under Devices -> IPv6 answers, because
the network-wide setting cannot fix a device that will not take an answer. A synthesized
NODATA has carried an SOA since the last release so a client can cache it (RFC 2308), but a
client that does not cache it has nothing to remember, and one that then does not fall back to
IPv4 just asks again: a solar inverter here asked for the same filteredAAAAabout forty times
a second, indefinitely, and still does. Answer in full hands that one device the real
answer and lets it fail to connect over IPv6 the way it would without Shepherd, while the rest
of the network keeps the filter; withhold is the opposite exception. Both survive a merge of
two device records, an explicit "answer in full" preferentially, since it is the setting that
keeps a device working.aaaa:offfinds them again in the device search,set_aaaasets them in
bulk, andGET/PUT /api/dns/aaaais the network-wide mode. See
docs/IPV6.md, which also corrects hard rule 3: blocking never decided by address
family, and now says so instead of claiming AAAA records are never withheld.
Fixed
- The public demo's modules are stamped with a content hash, so a returning visitor can no longer be served a fresh
app.jsalongside modules cached from an earlier version. The site's CDN serves.jswith a year-long lifetime, and
the cache buster on the site side can only stamp URLs written in HTML or CSS — not the ~70 modulesapp.jsimports.
scripts/sync-site-demonow rewrites those imports through the newcmd/stamp-demo-modules, hashing bottom-up so a
change in any module changes the URL of everything that reaches it. See
docs/PORTAL.md.