-
Notifications
You must be signed in to change notification settings - Fork 46
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
Question about --allow-host-access #284
Comments
It just sets this firewall rule -
And adds it to the network namespace hosts file as vopono.host I don't see this error myself (although I normally use Wireguard) - could you post the full command and log with |
Thanks for your comments! Here goes the command:
And the log: https://pastebin.com/raw/FDH4RJdL |
I can't replicate this myself is your hostname set in Also don't run |
Oh and what does the OpenVPN .ovpn file look like? As maybe it is coming from there? As vopono doesn't use the host machine's hostname anyway as far as I can tell. |
Again, thanks for replying! As per your questions:
Yes.
It has no up / down scripts if that's what you asking. Besides, it doesn't happen with vopono v.0.10.9 :) |
And does the hosts file in The only difference was to add the host IP (from the netns perspective) there, but that should use the IP address of the host from the netns, and shouldn't trigger a DNS lookup. |
Like this:
|
With
--allow-host-access
option,vopono
tries to resolve localhost after connecting and seems to fail with this message (I used it together with--protocol openvpn --custom
):Can this be avoided or probably suppressed somehow? AFAIR, it wasn't like that in some previous versions :)
The text was updated successfully, but these errors were encountered: