just to insert my 2p.
Provided the service manager is installed whilst the tunnel will not
appear in the list of tunnels you can view the logfile which will assist
with diagnosis.
From my perspective I set up exactly the same set-up myself at the
weekend and it is behaving as advertised (exc
Hi,
> The problem still is occurring, the service seems to get torn down never
> to come back again once the user comes back to the office and connects
> back into the main network with ethernet. When the user is on the main
> network the VPN host address will not get resolved by DNS by design. We
Hi,
> From this description, it seems that there's room for improvement.
>
> It doesn't seem reasonable for the WireGuard service to stop. Log and
> perhaps display an error, sure. But stopping seems harsh, and would
> prevent other tunnel endpoints from working - not a good user
> experience.
On 17-Jan-22 05:51, Simon Rozman wrote:
Hi,
WireGuard services start early on boot - sometimes even before the DNSCache
(DNS Client). If the service can't resolve hostnames used in the config file,
it will stop. But it will log this. Resolution to this problem is:
- Use IPs rather than hostna
Hi,
> I believe there's a bug in the Windows service implementation, if this
> issue is by design, it's problematic.
>
> I have non-admin users were when I initially set them up with wireguard,
> I configured it to use the service, using the command:
>
> wireguard /installtunnelservice "C:\Progr
I believe there's a bug in the Windows service implementation, if this issue is
by design, it's problematic.
I have non-admin users were when I initially set them up with wireguard, I
configured it to use the service, using the command:
wireguard /installtunnelservice "C:\Program
Files\WireGua
