nils/gluon
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fixup! Gluon-core: Allow multiple domain names for next_node-feature

Browse Source
This commit is contained in:
Christof Schulze 2018-02-15 22:05:42 +01:00
parent 122bd5138c
commit 2e80dffa68
2 changed files with 6 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/user/site.rst
View File

@ -174,12 +174,12 @@ next_node \: package
defaults to ``16:41:95:40:f7:dc``; this value usually doesn't need to be
changed, but it can be adjusted to match existing deployments that use a
different value. Each entry in the ``name``-field will be resolved to the
ipv4 and ipv6-address.
IPv4 and IPv6-address.
For this to work, clients must use the next-node as their resolver. In
batman-based networks this requires setting the central dhcp server to
deliver this address as DNS-server via DHCP-option. When running a radvd
batman-based networks this requires setting the central DHCP server to
deliver this address as DNS server via DHCP option. When running a radvd
inside the network, this should be set to deliver the next-node
ipv6-address via rdnss.
IPv6-address via rdnss.
mesh \: optional
Options specific to routing protocols.

6
package/gluon-core/luasrc/lib/gluon/upgrade/820-dns-config
View File

@ -33,10 +33,8 @@ local function set_dns_record(name, ip, sectionname)
})
end
uci:foreach("dhcp", "domain", function(s)
if (s['.name'] and string.match(s['.name'], "^nextnode[46]_")) then
uci:delete("dhcp", s['.name'])
end
uci:delete_all('dhcp', 'domain', function(s)
return (s['.name'] and string.match(s['.name'], "^nextnode[46]"))
end)
for i, name in ipairs(next_node.name or {}) do