From: jugs <jugs@protonmail.ch>
Cc: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Re: wg-quick systemd service does not work directly after boot
Date: Thu, 08 Feb 2018 14:14:18 -0500 [thread overview]
Message-ID: <5KOTFDe17sagyWs3-jk_vBjCoyO5MvpXPA5Dyp6wjGl8EuDcki0nfOUxFbFpM4aPzeI93mpIdHaACKCUdB3CGQ==@protonmail.ch> (raw)
In-Reply-To: <3e901b97-c67f-728b-332b-b301bb466dba@urlichs.de>
Or just use the IP address in the config?
=E2=80=8B-jugs
=E2=80=8B
-------- Original Message --------
On February 7, 2018 1:06 PM, Matthias Urlichs <matthias@urlichs.de> wrote:
>On 07.02.2018 12:54, Mytril wrote:
>>The interface cannot resolve the dynamic domain, because the internet
>> connection is not established at this moment.
>>But i have also only a workaround to create wg0. I also start the wg at
>> a later time.
>>So i think this is not a bug, but rather a problem with the order of
>> network connection startup.
>>
>Right. There cannot be a "correct" way of ordering wireguard vs. other
> interfaces that works in all circumstances.
>
> However, instead of sleeping, a dependency on network-online.target
> might be more appropriate if wireguard needs to resolve a name.
>
>
>-- Matthias Urlichs
>
>
>WireGuard mailing list
>WireGuard@lists.zx2c4.com
>https://lists.zx2c4.com/mailman/listinfo/wireguard
>
next prev parent reply other threads:[~2018-02-08 19:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 11:54 Mytril
2018-02-07 13:06 ` Matthias Urlichs
2018-02-08 19:14 ` jugs [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-07 9:03 Henning Reich
2018-02-07 12:08 ` Celti Burroughs
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='5KOTFDe17sagyWs3-jk_vBjCoyO5MvpXPA5Dyp6wjGl8EuDcki0nfOUxFbFpM4aPzeI93mpIdHaACKCUdB3CGQ==@protonmail.ch' \
--to=jugs@protonmail.ch \
--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).