nils/gluon
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
40b1f1b1e2
gluon/package/gluon-core/check_site.lua

90 lines
3.4 KiB
Lua
Raw Normal View History

treewide: rework check_site_lib.lua In addition to significant internal differences in check_site_lib.lua (in particular unifying error handling to a single place for the upcoming multi-domain support), this changes the way fields are addressed in site check scripts: rather than providing a string like 'next_node.ip6', the path is passed as an array {'next_node', 'ip6'}. Other changes in site check scripts: * need_array and need_table now pass the full path to the sub fields to the subcheck instead of the key and value * Any check referring to a field inside a table implies that all higher levels must be tables if they exist: a check for {'next_node', 'ip6'} adds an implicit (optional) check for {'next_node'}, which allows to remove many explicit checks for such tables
2018-01-19 09:12:43 +00:00
need_string(in_site({'site_code'}))
need_string(in_site({'site_name'}))
gluon-site: add default domain and check for it This does not do anything yet, as this_domain() is not implemented yet. Based-on-patch-by: lemoer <git@irrelefant.net>
2018-01-19 06:15:38 +00:00
-- this_domain() returns nil when multidomain support is disabled
if this_domain() then
need_domain_name(in_site({'default_domain'}))
gluon-core: add domain aliases and pretty name Based-on-patch-by: lemoer <git@irrelefant.net>
2018-01-20 05:22:26 +00:00
need_table(in_domain({'domain_names'}), function(domain)
need_alphanumeric_key(domain)
need_string(domain)
end)
need_string(in_domain({'domain_names', this_domain()}))
gluon-site: add default domain and check for it This does not do anything yet, as this_domain() is not implemented yet. Based-on-patch-by: lemoer <git@irrelefant.net>
2018-01-19 06:15:38 +00:00
end
treewide: rework check_site_lib.lua In addition to significant internal differences in check_site_lib.lua (in particular unifying error handling to a single place for the upcoming multi-domain support), this changes the way fields are addressed in site check scripts: rather than providing a string like 'next_node.ip6', the path is passed as an array {'next_node', 'ip6'}. Other changes in site check scripts: * need_array and need_table now pass the full path to the sub fields to the subcheck instead of the key and value * Any check referring to a field inside a table implies that all higher levels must be tables if they exist: a check for {'next_node', 'ip6'} adds an implicit (optional) check for {'next_node'}, which allows to remove many explicit checks for such tables
2018-01-19 09:12:43 +00:00
need_string_match(in_domain({'domain_seed'}), '^' .. ('%x'):rep(64) .. '$')
Validate site.conf
2014-07-05 00:48:56 +00:00
Switch to OpenWrt 18.06 branch
2018-07-10 20:57:40 +00:00
need_string({'opkg', 'openwrt'}, false)
build: add site check for obsolete settings (#1702)
2019-04-28 12:38:08 +00:00
obsolete({'opkg', 'lede'}, 'Use opkg.openwrt instead.')
treewide: rework check_site_lib.lua In addition to significant internal differences in check_site_lib.lua (in particular unifying error handling to a single place for the upcoming multi-domain support), this changes the way fields are addressed in site check scripts: rather than providing a string like 'next_node.ip6', the path is passed as an array {'next_node', 'ip6'}. Other changes in site check scripts: * need_array and need_table now pass the full path to the sub fields to the subcheck instead of the key and value * Any check referring to a field inside a table implies that all higher levels must be tables if they exist: a check for {'next_node', 'ip6'} adds an implicit (optional) check for {'next_node'}, which allows to remove many explicit checks for such tables
2018-01-19 09:12:43 +00:00
need_table({'opkg', 'extra'}, function(extra_repo)
need_alphanumeric_key(extra_repo)
need_string(extra_repo)
end, false)
gluon-core: replace opkg site configuration to make it more flexible The new options allow specifying custom repositories and are evaluated in an upgrade script, not during build.
2015-10-14 00:55:13 +00:00
treewide: rework check_site_lib.lua In addition to significant internal differences in check_site_lib.lua (in particular unifying error handling to a single place for the upcoming multi-domain support), this changes the way fields are addressed in site check scripts: rather than providing a string like 'next_node.ip6', the path is passed as an array {'next_node', 'ip6'}. Other changes in site check scripts: * need_array and need_table now pass the full path to the sub fields to the subcheck instead of the key and value * Any check referring to a field inside a table implies that all higher levels must be tables if they exist: a check for {'next_node', 'ip6'} adds an implicit (optional) check for {'next_node'}, which allows to remove many explicit checks for such tables
2018-01-19 09:12:43 +00:00
need_string(in_site({'hostname_prefix'}), false)
need_string(in_site({'timezone'}))
gluon-core: replace opkg site configuration to make it more flexible The new options allow specifying custom repositories and are evaluated in an upgrade script, not during build.
2015-10-14 00:55:13 +00:00
treewide: rework check_site_lib.lua In addition to significant internal differences in check_site_lib.lua (in particular unifying error handling to a single place for the upcoming multi-domain support), this changes the way fields are addressed in site check scripts: rather than providing a string like 'next_node.ip6', the path is passed as an array {'next_node', 'ip6'}. Other changes in site check scripts: * need_array and need_table now pass the full path to the sub fields to the subcheck instead of the key and value * Any check referring to a field inside a table implies that all higher levels must be tables if they exist: a check for {'next_node', 'ip6'} adds an implicit (optional) check for {'next_node'}, which allows to remove many explicit checks for such tables
2018-01-19 09:12:43 +00:00
need_string_array({'ntp_servers'}, false)
gluon-core: replace opkg site configuration to make it more flexible The new options allow specifying custom repositories and are evaluated in an upgrade script, not during build.
2015-10-14 00:55:13 +00:00
treewide: clean up site checks for prefix[46] and extra_prefixes6 - Move site check for prefix4 and extra_prefixes6 to gluon-core, so the rules don't need to be duplicated in several packages. This also fixes gluon-respondd not checking extra_prefixes6 at all when gluon-ebtables-source-filter is not installed as well. - A redundant check for prefix6 is removed from gluon-l3roamd (this was already checked by gluon-core) - A separate check for prefix4 remains in gluon-client-bridge, as the setting in mandatory there
2021-09-04 19:17:29 +00:00
need_string_match(in_domain({'prefix4'}), '^%d+.%d+.%d+.%d+/%d+$', false)
treewide: rework check_site_lib.lua In addition to significant internal differences in check_site_lib.lua (in particular unifying error handling to a single place for the upcoming multi-domain support), this changes the way fields are addressed in site check scripts: rather than providing a string like 'next_node.ip6', the path is passed as an array {'next_node', 'ip6'}. Other changes in site check scripts: * need_array and need_table now pass the full path to the sub fields to the subcheck instead of the key and value * Any check referring to a field inside a table implies that all higher levels must be tables if they exist: a check for {'next_node', 'ip6'} adds an implicit (optional) check for {'next_node'}, which allows to remove many explicit checks for such tables
2018-01-19 09:12:43 +00:00
need_string_match(in_domain({'prefix6'}), '^[%x:]+/64$')
treewide: clean up site checks for prefix[46] and extra_prefixes6 - Move site check for prefix4 and extra_prefixes6 to gluon-core, so the rules don't need to be duplicated in several packages. This also fixes gluon-respondd not checking extra_prefixes6 at all when gluon-ebtables-source-filter is not installed as well. - A redundant check for prefix6 is removed from gluon-l3roamd (this was already checked by gluon-core) - A separate check for prefix4 remains in gluon-client-bridge, as the setting in mandatory there
2021-09-04 19:17:29 +00:00
need_string_array_match(in_domain({'extra_prefixes6'}), '^[%x:]+/%d+$', false)
Merge gluon-radio-config into gluon-core gluon-radio-config contained only a single file. The code has been adjusted to allow creating a Gluon configuration without WLAN support by removing the wifi24 and wifi5 sections from site.conf.
2015-10-26 19:59:56 +00:00
gluon-core: disable legacy_rates by default, drop support for supported and basic rates (#1716)
2019-04-28 14:47:29 +00:00
local supported_rates = {6000, 9000, 12000, 18000, 24000, 36000, 48000, 54000}
Merge gluon-radio-config into gluon-core gluon-radio-config contained only a single file. The code has been adjusted to allow creating a Gluon configuration without WLAN support by removing the wifi24 and wifi5 sections from site.conf.
2015-10-26 19:59:56 +00:00
for _, config in ipairs({'wifi24', 'wifi5'}) do
treewide: rework check_site_lib.lua In addition to significant internal differences in check_site_lib.lua (in particular unifying error handling to a single place for the upcoming multi-domain support), this changes the way fields are addressed in site check scripts: rather than providing a string like 'next_node.ip6', the path is passed as an array {'next_node', 'ip6'}. Other changes in site check scripts: * need_array and need_table now pass the full path to the sub fields to the subcheck instead of the key and value * Any check referring to a field inside a table implies that all higher levels must be tables if they exist: a check for {'next_node', 'ip6'} adds an implicit (optional) check for {'next_node'}, which allows to remove many explicit checks for such tables
2018-01-19 09:12:43 +00:00
if need_table({config}, nil, false) then
need_string(in_site({'regdom'})) -- regdom is only required when wifi24 or wifi5 is configured
gluon-core: add support for configuring the beacon interval This adds support for the beacon interval to be set on a per-band base. This has the potential to reduce the amount of airtime used up for sending beacon frames.
2020-05-21 22:24:13 +00:00
need_number({config, 'beacon_interval'}, false)
gluon-core: check_site.lua: fix indentation
2017-01-24 22:02:20 +00:00
gluon-core: improve channel and add chanlist validation
2018-02-28 01:57:12 +00:00
if config == "wifi24" then
local channels = {1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14}
need_one_of({config, 'channel'}, channels)
elseif config == 'wifi5' then
local channels = {
34, 36, 38, 40, 42, 44, 46, 48, 50, 52, 54, 56, 58, 60, 62,
treewide: fix luacheck warnings
2019-06-16 18:06:45 +00:00
64, 96, 100, 102, 104, 106, 108, 110, 112, 114, 116, 118,
120, 122, 124, 126, 128, 132, 134, 136, 138, 140, 142, 144,
gluon-core: improve channel and add chanlist validation
2018-02-28 01:57:12 +00:00
149, 151, 153, 155, 157, 159, 161, 165, 169, 173 }
need_one_of({config, 'channel'}, channels)
need_chanlist({config, 'outdoor_chanlist'}, channels, false)
gluon-core: allow presetting the outdoor mode for new installations
2018-03-01 01:21:04 +00:00
need_one_of({config, 'outdoors'}, {true, false, 'preset'}, false)
gluon-core: add outdoor support for 5 ghz radios Add the `wifi5.outdoor_chanlist` site configuration that allows specifying an outdoor channel range that can be switched to for regulatory compliance. Upon enabling the outdoor option the device will - configure the `outdoor_chanlist` on all 5 GHz radios - which may enable DFS/TPC, based on the regulatory domain - disable ibss/mesh on the 5 GHz radio, as DFS *will* break mesh connections - allow for htmode reconfiguration on 5 GHz radios The outdoor option can be toggled from - Advanced Settings - W-LAN - Outdoor Installation The `preserve_channel` flag overrules the outdoor channel selection.
2018-02-11 12:54:06 +00:00
end
gluon-core: check_site.lua: fix indentation
2017-01-24 22:02:20 +00:00
gluon-core: disable legacy_rates by default, drop support for supported and basic rates (#1716)
2019-04-28 14:47:29 +00:00
obsolete({config, 'supported_rates'}, '802.11b rates are disabled by default.')
obsolete({config, 'basic_rate'}, '802.11b rates are disabled by default.')
gluon-core: drop IBSS support
2019-11-05 19:46:19 +00:00
obsolete({config, 'ibss'}, 'IBSS support has been dropped.')
treewide: rework check_site_lib.lua In addition to significant internal differences in check_site_lib.lua (in particular unifying error handling to a single place for the upcoming multi-domain support), this changes the way fields are addressed in site check scripts: rather than providing a string like 'next_node.ip6', the path is passed as an array {'next_node', 'ip6'}. Other changes in site check scripts: * need_array and need_table now pass the full path to the sub fields to the subcheck instead of the key and value * Any check referring to a field inside a table implies that all higher levels must be tables if they exist: a check for {'next_node', 'ip6'} adds an implicit (optional) check for {'next_node'}, which allows to remove many explicit checks for such tables
2018-01-19 09:12:43 +00:00
if need_table({config, 'mesh'}, nil, false) then
gluon-core, gluon-client-bridge: allow 0-character ESSIDs/mesh IDs
2018-03-17 14:38:24 +00:00
need_string_match(in_domain({config, 'mesh', 'id'}), '^' .. ('.?'):rep(32) .. '$')
gluon-core: disable legacy_rates by default, drop support for supported and basic rates (#1716)
2019-04-28 14:47:29 +00:00
need_one_of({config, 'mesh', 'mcast_rate'}, supported_rates, false)
treewide: rework check_site_lib.lua In addition to significant internal differences in check_site_lib.lua (in particular unifying error handling to a single place for the upcoming multi-domain support), this changes the way fields are addressed in site check scripts: rather than providing a string like 'next_node.ip6', the path is passed as an array {'next_node', 'ip6'}. Other changes in site check scripts: * need_array and need_table now pass the full path to the sub fields to the subcheck instead of the key and value * Any check referring to a field inside a table implies that all higher levels must be tables if they exist: a check for {'next_node', 'ip6'} adds an implicit (optional) check for {'next_node'}, which allows to remove many explicit checks for such tables
2018-01-19 09:12:43 +00:00
need_boolean({config, 'mesh', 'disabled'}, false)
gluon-core: check_site.lua: fix indentation
2017-01-24 22:02:20 +00:00
end
end
Merge gluon-radio-config into gluon-core gluon-radio-config contained only a single file. The code has been adjusted to allow creating a Gluon configuration without WLAN support by removing the wifi24 and wifi5 sections from site.conf.
2015-10-26 19:59:56 +00:00
end
gluon-core: allow setting PoE passthrough default setting from site.conf
2016-07-29 22:00:39 +00:00
treewide: rework check_site_lib.lua In addition to significant internal differences in check_site_lib.lua (in particular unifying error handling to a single place for the upcoming multi-domain support), this changes the way fields are addressed in site check scripts: rather than providing a string like 'next_node.ip6', the path is passed as an array {'next_node', 'ip6'}. Other changes in site check scripts: * need_array and need_table now pass the full path to the sub fields to the subcheck instead of the key and value * Any check referring to a field inside a table implies that all higher levels must be tables if they exist: a check for {'next_node', 'ip6'} adds an implicit (optional) check for {'next_node'}, which allows to remove many explicit checks for such tables
2018-01-19 09:12:43 +00:00
need_boolean(in_site({'poe_passthrough'}), false)
gluon-core: add configuration that enables the next_node to be used as dns cache
2016-12-30 16:22:22 +00:00
treewide: rework check_site_lib.lua In addition to significant internal differences in check_site_lib.lua (in particular unifying error handling to a single place for the upcoming multi-domain support), this changes the way fields are addressed in site check scripts: rather than providing a string like 'next_node.ip6', the path is passed as an array {'next_node', 'ip6'}. Other changes in site check scripts: * need_array and need_table now pass the full path to the sub fields to the subcheck instead of the key and value * Any check referring to a field inside a table implies that all higher levels must be tables if they exist: a check for {'next_node', 'ip6'} adds an implicit (optional) check for {'next_node'}, which allows to remove many explicit checks for such tables
2018-01-19 09:12:43 +00:00
if need_table({'dns'}, nil, false) then
need_string_array_match({'dns', 'servers'}, '^[%x:]+$')
Revert "gluon-core: remove DNS cache feature" This reverts commit 543eb178824e8ed8a6f385fe1ebdf0d7ca709be3. Restores the dns caching configuration that should be feasible, since we now require around 8 MB of flash.
2023-01-15 19:46:23 +00:00
need_number({'dns', 'cacheentries'}, false)
gluon-core: add configuration that enables the next_node to be used as dns cache
2016-12-30 16:22:22 +00:00
end
Move wifi24/5 and mesh_on_wan/lan site validators from gluon-mesh-batman-adv-core to gluon-core These values have been in use in gluon-core for some time, the validators need to be moved as well.
2017-02-10 20:19:34 +00:00
gluon-core: allow multiple domain names for next_node-feature * change type of next_node.name * create domain entry for each entry and add to dnsmasq configuration [Matthias Schiffer: reword documentation]
2018-01-29 07:21:47 +00:00
need_string_array(in_domain({'next_node', 'name'}), false)
treewide: rework check_site_lib.lua In addition to significant internal differences in check_site_lib.lua (in particular unifying error handling to a single place for the upcoming multi-domain support), this changes the way fields are addressed in site check scripts: rather than providing a string like 'next_node.ip6', the path is passed as an array {'next_node', 'ip6'}. Other changes in site check scripts: * need_array and need_table now pass the full path to the sub fields to the subcheck instead of the key and value * Any check referring to a field inside a table implies that all higher levels must be tables if they exist: a check for {'next_node', 'ip6'} adds an implicit (optional) check for {'next_node'}, which allows to remove many explicit checks for such tables
2018-01-19 09:12:43 +00:00
need_string_match(in_domain({'next_node', 'ip6'}), '^[%x:]+$', false)
need_string_match(in_domain({'next_node', 'ip4'}), '^%d+.%d+.%d+.%d+$', false)
Move wifi24/5 and mesh_on_wan/lan site validators from gluon-mesh-batman-adv-core to gluon-core These values have been in use in gluon-core for some time, the validators need to be moved as well.
2017-02-10 20:19:34 +00:00
gluon-core: set VXLAN/legacy mode in site config In multidomain setups, VXLAN is enabled by default, but can be disabled in domain configs using the mesh/vxlan option. In single domain setups, the mesh/vxlan option is mandatory. The UCI option for legacy mode is removed. Fixes #1364
2018-04-27 15:36:47 +00:00
need_boolean(in_domain({'mesh', 'vxlan'}), false)
gluon-core: initialize interfaces role configuration The new configuration generates sections iface_single/lan/wan in /etc/config/gluon. These sections usually refer to a sysconfig-controlled interface list, but adding custom sections with verbatim interfaces names is also possible. Each interface section contains a list of roles. The supported roles are 'client', 'uplink' and 'mesh'. Multiple roles can be configured on the same interface (for example the old 'mesh_on_wan' setting would become 'uplink'+'mesh'). 'client' is subsumed by any other role configured on the same interface ('client'+'mesh' is equivalent to 'mesh'). This property is important, as it allows the Wired Mesh settings in gluon-web-network to simply add and remove the mesh role without having to care what other roles are set - so in the default setup, this would switch between 'client' and 'client'+'mesh' for the LAN interface. By default, the WAN interface has role 'uplink' and the LAN interface 'client'; if only a single interface exists, the roles from the WAN interface are used by default. The default for each of the three interfaces (WAN/LAN/single) can be changed separated in site.conf, superseding the old mesh_on_wan, mesh_on_lan and single_as_lan settings.
2022-01-23 12:39:35 +00:00
local interfaces_roles = {'client', 'uplink', 'mesh'}
for _, config in ipairs({'wan', 'lan', 'single'}) do
gluon-core: make interface roles exclusive in site config
2023-02-26 21:24:10 +00:00
local default_roles = in_site({'interfaces', config, 'default_roles'})
need_array_of(default_roles, interfaces_roles, false)
need_array_elements_exclusive(default_roles, 'client', 'mesh', false)
need_array_elements_exclusive(default_roles, 'client', 'uplink', false)
gluon-core: initialize interfaces role configuration The new configuration generates sections iface_single/lan/wan in /etc/config/gluon. These sections usually refer to a sysconfig-controlled interface list, but adding custom sections with verbatim interfaces names is also possible. Each interface section contains a list of roles. The supported roles are 'client', 'uplink' and 'mesh'. Multiple roles can be configured on the same interface (for example the old 'mesh_on_wan' setting would become 'uplink'+'mesh'). 'client' is subsumed by any other role configured on the same interface ('client'+'mesh' is equivalent to 'mesh'). This property is important, as it allows the Wired Mesh settings in gluon-web-network to simply add and remove the mesh role without having to care what other roles are set - so in the default setup, this would switch between 'client' and 'client'+'mesh' for the LAN interface. By default, the WAN interface has role 'uplink' and the LAN interface 'client'; if only a single interface exists, the roles from the WAN interface are used by default. The default for each of the three interfaces (WAN/LAN/single) can be changed separated in site.conf, superseding the old mesh_on_wan, mesh_on_lan and single_as_lan settings.
2022-01-23 12:39:35 +00:00
end
obsolete({'mesh_on_wan'}, 'Use interfaces.wan.default_roles.')
obsolete({'mesh_on_lan'}, 'Use interfaces.lan.default_roles.')
obsolete({'single_as_lan'}, 'Use interfaces.single.default_roles.')
Reference in New Issue Copy Permalink