On Wed 2017-08-09 13:16:45 +0200, Egbert Verhage wrote:
> Ow, that it is a common problem.
> I think your patch is a nice updated.
> So I got some time left and build a patch (pull request) on github
> here: https://github.com/EggieCode/wireguard-ppa/pull/24
thanks for writing this notification, Jason, and for including it in
your ubuntu ppa, Egbert.
I'm wondering whether the advice it gives is correct and thorough enough
for non-gentoo users, though.
If i "rmmod wireguard && modprobe wireguard" won't my configuration be
lost? You point out that you might want to tear them down gracefully
first. But then no mention of needing to bring them up again later?
Aren't there additional commands that the admin will have to do to have
a *functional* wireguard implementation, and those commands might
differe based on their userspace layout/configuration/policy?
The simplest instruction for the upgrade (which is probably offensive to
all of us here) is to say "you should reboot your machine for the
wireguard upgrade to take effect" -- that gets us the benefit of any
userspace wireguard configuration that happens during system
initialization to happen, without having to guess/poke/prod at the
user's networking config while live.
Also, for an administrator doing this over ssh, we might want to warn
them that taking these steps will lock them out if they're connecting
via ssh on top of wireguard, right?
WireGuard mailing list