This repository has been archived by the owner on Feb 1, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 237
Direct route to VPN gateway not set #5
Comments
That could be an issue in the script, as it should always be called on disconnection. I'll try to check it this week. |
The script configures the TAP interface first, then sets up the direct route to the VPN gateway. Because the interface configuration automatically includes the new default gateway there is a brief moment where traffic loops and DTLS setup can fail. After moving the direct route creation command up, to be executed prior to the interface configuration, my problem was solved. |
Could you send your changes as a patch or pull request? |
|
Hm. I think my patch will undo your own most recent patch as I based it on a version downloaded earlier today. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
These are actually two separate issues:
On Windows 8 the TAP interface is setup correctly. A new default route is also created correctly. A direct route to the VPN gateway however is not. Traffic loops/stops flowing and causes the second error below.
The GUI correctly detects DTLS setup failed and shows a red traffic sign/disconnected state. It forgets however to remove the default route to the VPN and bring down the TAP interface. This leaves the computer unable to access the Internet.
The text was updated successfully, but these errors were encountered: