Re: Ordering wireguard interface init and daemon start

Vincent Lee (HE12026-08-27):
> Thanks for pointing this out. I noticed I had allow-hotplug on enp1s0
> and auto on wg0, which imposes no ordering constraint.
> 
> I tried again with both interfaces configured as auto, which from my
> understanding means they should start one after another. However, it
> still didn't work (logs below)

I do not think that having the interfaces both enables orders them in
any way.

To raise a VPN after a physical interface, I have resolved to add
`post-up ifup VPN` to the configuration of the physical interface.
Another solution would be `pre-up /usr/local/sbin/wait_for_network` in
the configuration of the VPN.

> In the meantime, the IP address of the WG peer is fixed, so I'm just
> going to hardcode it in the config, but I'm curious how you fixed it in
> your case.

As I said: post-up ifup.

Regards,