-
Notifications
You must be signed in to change notification settings - Fork 36
VPN-4511 allow custom dns #4123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
* Remove legacy call to ConnectTunnel * Rename connect_v2 to connect * Update changelog * tauri: fix
Co-authored-by: NYM_bot <_@_>
Co-authored-by: NYM_bot <_@_> Co-authored-by: Karol Sawicki <[email protected]>
pronebird
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: 0 of 78 files reviewed, 1 unresolved discussion (waiting on @agentpietrucha)
nym-vpn-core/crates/nym-vpnd/src/service/config/legacy.rs line 13 at r1 (raw file):
#[serde(rename_all = "snake_case")] pub(crate) struct VpnServiceConfig { pub(crate) entry_point: EntryPoint,
This looks like a rebase issue?
|
Please |
|
@pronebird I moved to a new PR due to time consuming conflicts here. #4128 |
Ticket
JIRA-VPN-4511
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
Checklist:
Screenshots (optional, if UI related)
This change is