gluon/package/gluon-mesh-vpn-fastd/check_site.lua

local fastd_methods = {'salsa2012+umac', 'null+salsa2012+umac', 'null@l2tp', 'null'}
need_array_of({'mesh_vpn', 'fastd', 'methods'}, fastd_methods)
need_boolean(in_site({'mesh_vpn', 'fastd', 'configurable'}), false)
need_number({'mesh_vpn', 'fastd', 'mtu'})

need_one_of(in_site({'mesh_vpn', 'fastd', 'syslog_level'}),
	{'error', 'warn', 'info', 'verbose', 'debug', 'debug2'}, false)

local function check_peer(k)
	need_alphanumeric_key(k)

	need_string_match(in_domain(extend(k, {'key'})), '^%x+$')
	need_string_array(in_domain(extend(k, {'remotes'})))
end

local function check_group(k)
	need_alphanumeric_key(k)

	need_number(extend(k, {'limit'}), false)
	need_table(extend(k, {'peers'}), check_peer, false)
	need_table(extend(k, {'groups'}), check_group, false)
end

need_table({'mesh_vpn', 'fastd', 'groups'}, check_group)
gluon-{,web-}mesh-vpn-fastd: add support for null@l2tp method THe "null" and "null@l2tp" methods are considered equivalent and always added and removed together when the method list is "configurable". "null@l2tp" is added before "null", so it is preferred when the peer supports both. 2021-03-07 19:13:41 +00:00			`local fastd_methods = {'salsa2012+umac', 'null+salsa2012+umac', 'null@l2tp', 'null'}`
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_array_of({'mesh_vpn', 'fastd', 'methods'}, fastd_methods)`
			`need_boolean(in_site({'mesh_vpn', 'fastd', 'configurable'}), false)`
gluon-mesh-vpn-*: make vpn MTU provider specific If a community uses different vpn providers, they typically assume the same MTU for the wan device underneath the VPN. As different VPN providers however have different overhead, the MTU of the VPN device differs for each provider. Therefore this commit makes the MTU of the VPN device provider specific. This has two advantages: 1. The same site.conf can used to bake firmwares for different VPN providers (only by selecting a diferent vpn feature in the site.mk). 2. We are coming closer to the option of integrating multiple VPN providers into one firmware. 2021-12-28 21:50:18 +00:00			`need_number({'mesh_vpn', 'fastd', 'mtu'})`
Validate site.conf 2014-07-05 00:48:56 +00:00
treewide: fix luacheck warnings 2019-06-16 18:06:45 +00:00			`need_one_of(in_site({'mesh_vpn', 'fastd', 'syslog_level'}),`
			`{'error', 'warn', 'info', 'verbose', 'debug', 'debug2'}, false)`
Validate site.conf 2014-07-05 00:48:56 +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			`local function check_peer(k)`
			`need_alphanumeric_key(k)`
Validate section names from site.conf in various packages 2015-10-11 17:31:44 +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_match(in_domain(extend(k, {'key'})), '^%x+$')`
			`need_string_array(in_domain(extend(k, {'remotes'})))`
Validate site.conf 2014-07-05 00:48:56 +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			`local function check_group(k)`
			`need_alphanumeric_key(k)`
gluon-mesh-vpn-fastd: extend site configuration to allow multiple and nested peer groups 2015-04-30 11:05:15 +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_number(extend(k, {'limit'}), false)`
			`need_table(extend(k, {'peers'}), check_peer, false)`
			`need_table(extend(k, {'groups'}), check_group, false)`
gluon-mesh-vpn-fastd: extend site configuration to allow multiple and nested peer groups 2015-04-30 11:05:15 +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_table({'mesh_vpn', 'fastd', 'groups'}, check_group)`