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

need_string_array(in_domain({'mesh_vpn', 'tunneldigger', 'brokers'}))
need_number({'mesh_vpn', 'tunneldigger', 'mtu'})
gluon-mesh-vpn-tunneldigger: only allow in domain config Signed-off-by: Jan-Tarek Butt <tarek@ring0.de> 2018-03-28 15:55:26 +00:00			`need_string_array(in_domain({'mesh_vpn', 'tunneldigger', 'brokers'}))`
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', 'tunneldigger', 'mtu'})`