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

Name resolution not refreshed after "power hibernate-restore" on OpenVPN client PCs #561

Open
robot-dot-win opened this issue May 29, 2024 · 3 comments

Comments

@robot-dot-win
Copy link

I have an OpenVPN server inside a LAN, which accesses the Internet via a NAT router:

    Server IP: 192.168.254.254
    Router IP: 18.143.175.x
    Server domain name: vpn.foo.com

Inside the LAN, the local DNS resolves vpn.foo.com to 192.168.254.254, while all outside DNSes resolve it to 18.143.175.x. The OpenVPN client configuration is like:

    client
    remote vpn.foo.com 81 tcp4

Note that inside the LAN, computers can also access 18.143.175.x:81-->192.168.254.254:81.

All OpenVPN clients can access each other(client-to-client) whether inside or outside the LAN. But in addition when a client is outside, the server will push a route to it via the "client-connect" script. Please see:

Server configuration file
Server "client-connect" script
Clent configuration file

Now is the problem: I have a laptop PC, after connected successfully with vpn.foo.com(18.143.175.x) ouside the LAN, directly set power hibernated. Then I moved the PC inside the LAN, having its power restored, and getting a LAN IP and DNS via DHCP. Now I hope OpenVPN could use the new DNS to resolve vpn.foo.com to 192.168.254.254, but it didn't, still using the old IP 18.143.175.x to make the connection. Thus the server still pushed the route to me, which made a confusion inside the LAN.

@robot-dot-win
Copy link
Author

Server side: CentOS Stream 9, OpenVPN 2.6.10
Client side: Windows 11 23H2, OpenVPN GUI 11.48.0.0, OpenVPN 2.6.10 , DCO Virtual Adapter

@schwabe
Copy link
Contributor

schwabe commented May 29, 2024

Please include a log file.

@robot-dot-win
Copy link
Author

Connected outside the LAN, then power hibernated, then went inside the LAN, then power restored:
outside-hibernate-inside-restore.log

Inside the LAN, normally connected, the LOG should be:
inside-normal.log

@schwabe Thanks!

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

No branches or pull requests

2 participants