Closed data-sync-user closed 6 months ago
➤ Naomi Kirby commented:
Bringing this one into the Zapdos sprint, because it kind of came along for free with VPN-4227
➤ Raluca Monica Ilban commented:
Hi Naomi Kirby , could you please let us know how we can test this? As mentioned in https://mozilla-hub.atlassian.net/browse/VPN-4227 ( https://mozilla-hub.atlassian.net/browse/VPN-4227|smart-link ) , we cannot use the 'force_daemon_crash' command in Inspector, only restart the vpn broker from windows service manager.
➤ Naomi Kirby commented:
My steps to test this:
➤ Raluca Monica Ilban commented:
Hi Naomi Kirby ,
Thank you! We've verified this while using build 2.21.0 (2.202403072017) in Windows 10/11, following the steps provided and we confirm that the VPN can be turned on successfully after the Mozilla VPN (tunnel) service was stopped. Marking this as fixed.
The windows tunnel broker service acts as a middle-man between the client GUI and the wireguard-go tunnel device, while we hope that the wireguard-go code is stable and free of crashes, we should ensure that a crash of the wireguard-go tunnel device does not result in a broken network connection. In the event of a crash:
┆Issue is synchronized with this Jira Task ┆Reporter: Naomi Kirby