Skip to content
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

DNS not configured for internal use, after connecting to the VPN? #53

Open
coleshaw opened this issue Aug 3, 2022 · 2 comments
Open

Comments

@coleshaw
Copy link

coleshaw commented Aug 3, 2022

Hello, thank you for this great tool!

I am using version 5.5.0 with openconnect 8.20-1, on PopOS 22.04. Sporadically, it seems like after I connect to the VPN, I do not have the internal DNS entries on my computer, and thus I can only access internal sites if I know their IP addresses. Have you seen this issue before, and if so, do you have any suggestions for how to address it?

Please let me know if I can supply any other debug information.

Thanks!

@coleshaw
Copy link
Author

coleshaw commented Aug 3, 2022

Note that this happens even though ucsf-vpn details shows an internal IP and network access.

@HenrikBengtsson
Copy link
Owner

If I understand this correctly, you want to preserve the local nameserver when connected to the VPN. The default behavior of the VPN is to drop that. See #64 for how to preserve it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants