Anyway to have env variables in the single config file (without wg wgconf
blaming), but not in two files per connection? For ex. make wg wgconf redirect
variables from . config file to wg-config to deal with.
Using two files will make wireguard configuration even harder to understand,
and this
Hi David,
On Thu, Dec 8, 2016 at 1:37 AM, David Miller wrote:
> You really have to land the IP header on a proper 4 byte boundary.
>
> I would suggest pushing 3 dummy garbage bytes of padding at the front
> or the end of your header.
Are you sure 3 bytes to get 4 byte
Hey guys,
The primary means of configuring wireguard is wg(8) for the
wireguard-specific stuff and ip(8) for the rest. The eventual goal has
always been to fold the wg(8) functionality into ip(8) upstream. This
goal still remains, but the time for that is not yet now. Because of
that, wg(8)
It will be super cool if ip/netmask functionality will be addressed by wgconf
Currently we testing this systemd units for wireguard ppa:
: wireguard.service
# This service is actually a systemd target,
# but we are using a service since targets cannot be reloaded.
[Unit]
Description=WireGuard
"Jason A. Donenfeld" on Thu, 2016/12/08 12:18:
> I like this, but two questions.
>
> 1. Why did you get rid of the ExecStop config saving line?
I do not like units altering configuration. If you want to save configuration
on stop create a second unit with correct dependencies
I like this, but two questions.
1. Why did you get rid of the ExecStop config saving line?
2. You're not planning to actually package this unit file, are you?
___
WireGuard mailing list
WireGuard@lists.zx2c4.com
From: Christian Hesse
Signed-off-by: Christian Hesse
---
contrib/examples/systemd/README| 5 +++--
contrib/examples/systemd/example.address | 1 +
contrib/examples/systemd/example.conf | 8
contrib/examples/systemd/wgserver.service