Hi,
> + if [ -z "$public_key" ]; then
> + echo "Skipping peer config $peer_config because public key is
> not defined."
> + return 0
> + fi
I guess there will be other error conditions that could cause the wg
setup to fail... is there any more robust way to check
On 05/12/2019 11:33, Florian Eckert wrote:
If a config section of a peer does not have a public key defined, the
whole interface does not start. The following log is shown
daemon.notice netifd: test (21071): Line unrecognized: `PublicKey='
daemon.notice netifd: test (21071): Configuration
If a config section of a peer does not have a public key defined, the
whole interface does not start. The following log is shown
daemon.notice netifd: test (21071): Line unrecognized: `PublicKey='
daemon.notice netifd: test (21071): Configuration parsing erro
The command 'wg show' does only show
