This repository has been archived by the owner on May 10, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 448
Brave VPN should use WireGuard by default #6646
Milestone
Comments
11 tasks
soner-yuksel
added a commit
that referenced
this issue
Apr 6, 2023
iccub
added a commit
that referenced
this issue
Apr 14, 2023
11 tasks
iccub
added a commit
that referenced
this issue
Apr 14, 2023
iccub
added a commit
that referenced
this issue
Apr 14, 2023
11 tasks
11 tasks
soner-yuksel
added a commit
that referenced
this issue
Apr 25, 2023
soner-yuksel
added a commit
that referenced
this issue
Apr 25, 2023
Verified on Using Test Plan in PR - #7125 (comment) Fresh User
Existing Plan
|
arthuredelstein
pushed a commit
to brave/brave-core
that referenced
this issue
Feb 13, 2024
arthuredelstein
pushed a commit
to brave/brave-core
that referenced
this issue
Feb 13, 2024
arthuredelstein
pushed a commit
to brave/brave-core
that referenced
this issue
Feb 13, 2024
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
Problem Description
Our current VPN integration (using GuardianConnect library) is using IKEv2 protocol. This can be problematic for some folks who are connected to VPN while on WiFi. The root cause is unknown, but their WiFi connection will drop. Please see #6645
Feature Overview
GuardianConnect has the ability to use WireGuard as the protocol. We'd need to make some changes to our code-base
Design
We shouldn't need a design unless we wanted to let the user choose. If we let the user choose, we may want to default to WireGuard.
The text was updated successfully, but these errors were encountered: