From: Joakim Sindholt <opensource@zhasha.com>
To: Kalin KOZHUHAROV <me.kalin@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] What is a good way to ingrate (as of now) wireguard into openrc in Gentoo?
Date: Mon, 21 Nov 2016 15:06:53 +0100 [thread overview]
Message-ID: <a63dbd90.dNq.dMV.H.oxNDgt@mailjet.com> (raw)
In-Reply-To: <CAKXLc7fQmf=LVrkJ3C5XAYRdimjxNT=xGey9W+qivqLpV+XO7A@mail.gmail.com>
On Mon, Nov 21, 2016 at 6:15 AM, Kalin KOZHUHAROV <me.kalin@gmail.com>
wrote:
> config_wg0="192.168.13.12/24"
> wireguard_wg0="/etc/wireguard/wg0.conf"
>
> Finally, symlink to net.lo:
>
> ln -nfs net.lo /etc/init.d/net.wg0
>
> Then `/etc/init.d/net.wg0 start` and `/etc/init.d/net.wg0 stop` work
> as expected.
Yep, that's how it's supposed to be used
> EDIT: Add this to /etc/rc.conf to make things run smoothly:
> rc_hotplug="!net.wg?"
I have not experienced any issues like this.
> However `/etc/init.d/net.wg0 restart` sometimes fails silently...
> I am trying to reproduce it, but cannot get the pattern of failures.
> It outputs all fine to the console, but there is no actual interface
> created...
>
> [...]
>
> I tried to debug a few things and my observation is that "sometimes",
> interface is reappearing after `ip link delete dev wg0`...
> Any ideas? I thought am not running any automagic daemons (systemd,
> networkmanager, etc.).
> But... there is some systemd code lurking may be.
> Anyway, I added it to be NOT hotplugged:
> $ grep wg /etc/rc.conf
> rc_hotplug="pcscd !net.wg?"
>
> And it seems to work! Otherwise the interface gets marked as
> hotpluggable and is being recreated/killed (see the first number on
> `ip link show dev wg0` constantly growing)
Interesting. I've had problems with other programs interfering in the
past,
most notably dhcpcd which would nuke my routing rules, but never this.
The script is basically just a whittled down version of the pppd.sh
script
and should work in much the same way. I just hacked it up rather quickly
so it's very possible that I missed something really important.
I'm running an otherwise bog-standard clean gentoo install with pretty
much
nothing installed and this issue hasn't presented itself so far.
It's being updated today so I'll get on it if I can reproduce it.
Pretty weird though...
next prev parent reply other threads:[~2016-11-21 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 11:42 Kalin KOZHUHAROV
2016-11-19 1:14 ` Jason A. Donenfeld
2016-11-21 5:15 ` Kalin KOZHUHAROV
2016-11-21 14:06 ` Joakim Sindholt [this message]
2016-11-21 13:55 ` Joakim Sindholt
2016-11-21 17:00 ` Jason A. Donenfeld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a63dbd90.dNq.dMV.H.oxNDgt@mailjet.com \
--to=opensource@zhasha.com \
--cc=me.kalin@gmail.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).