Windows11 connects but will not pass traffic

[cheffcook]

Hi again.
After post above my friend who belong VPN server told me what he not set up server to working with IPv6. And we together tried to test it and switched off IPv6 on my PC.
When IPv6 on

Code: Select all

C:\WINDOWS\system32>tracert google.com
Tracing route to google.com [2a00:1450:4010:c06::71]
over a maximum of 30 hops:
  1    <1 мс    <1 мс    <1 мс  2a00:1370:8188:c5b:72f8:2bff:fe3c:ad40
  2     6 ms     6 ms     6 ms  2a00:1370:8088::
  3    15 ms     9 ms     9 ms  a197-cr04-as25513.msk.mts-internet.net [2a02:28:1:2::42:2]
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     6 ms     *        *     mag9-cr02-be10.77.msk.mts-internet.net [2a02:28:1::12b:1]
  7     *        *        *     Request timed out.
  8     7 ms     7 ms     *     mag9-cr02-be13.77.msk.mts-internet.net [2a02:28:1::19b:1]
  9     *        *        7 ms  a197-cr01-ae10.77.msk.mts-internet.net [2a02:28:1::12b:2]
 10     9 ms     6 ms     9 ms  a197-cr04-be31.77.msk.mts-internet.net [2a02:28:1::1b7:2]
 11     7 ms    10 ms     7 ms  a197-cr03-ae0.16.msk.mts-internet.net [2a02:28:1::e3:62]
 12     7 ms     6 ms     6 ms  2a02:28:1::e3:102
 13     9 ms     6 ms     7 ms  a197-cr04-be18.10.msk.mts-internet.net [2a02:28:1::e3:72]
 14     8 ms     *        7 ms  2a02.0028.000100000000000001b70001.bbn.ip6.mtsws.net [2a02:28:1::1b7:1]
 15     8 ms     7 ms     7 ms  mag9-cr02-be10.77.msk.mts-internet.net [2a02:28:1::12b:1]
 16     *        *        *     Request timed out.
 17    23 ms    21 ms    21 ms  2001:4860::cc:4001:16c7
 18    22 ms    23 ms    20 ms  2001:4860:0:1::38f3
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28    20 ms    20 ms    20 ms  lj-in-x71.1e100.net [2a00:1450:4010:c06::71]

And after IPv6 off

Code: Select all

C:\WINDOWS\system32>tracert google.com
Tracing route to к google.com [64.233.163.139]
over a maximum of 30 hops:
  1    45 ms    41 ms    41 ms  192.168.63.1
  2    48 ms    44 ms    45 ms  gw.bacloud.info [85.206.160.1]
  3    42 ms    42 ms    41 ms  3-240-206-85.bacloud.info [85.206.240.3]
  4    41 ms    42 ms    42 ms  1-240-206-85.bacloud.info [85.206.240.1]
  5    42 ms    47 ms    43 ms  et002.RT.OMT.SQQ.LT.retn.net [87.245.242.233]
  6    52 ms    52 ms    52 ms  ae0-13.RT.LDC.WAW.PL.retn.net [87.245.233.56]
  7    53 ms    53 ms    58 ms  72.14.203.82
  8    52 ms    54 ms    54 ms  108.170.250.217
  9    67 ms    65 ms    65 ms  209.85.142.125
 10    65 ms    65 ms    65 ms  142.251.238.70
 11    67 ms    64 ms    65 ms  216.239.62.15
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21    85 ms    84 ms    85 ms  lj-in-f139.1e100.net [64.233.163.139]

All worked now. But the question remained: why did everything stop working the day before yesterday? Maybe some Windows update forced pass traffic via IPv6? I dont know. I'm very bad at networking.

[AlexAT]

+1 there
Experiencing similar symptoms on one of client machines with OpenVPN Connect (3.3.6 (2752)).
Symptom reasons are: connection to OpenVPN server is ok and Connect client shows IP address assigned, but there is no IP address on TAP interface, it stays 169.254.x.x. Tried reinstalling OpenVPN Connect, deleting driver and reinstalling, to no avail.

Don't exactly have the logs, but there is one strange thing I've noticed:
- netsh command that sets interface IP address takes several seconds to execute, with no errors -

(the command in question is netsh interface ip set address <ifnum> static <ip> <mask> gateway=<gw> store=active)

After netsh execution, IP address on TAP interface still remains autoconfiguration one (169.254.)

I have copied netsh command from logs and tried executing it again both under user and administrator privileges, to no avail. Same stuff - no error, no output, takes several seconds to execute, no effect on interface. Checking Windows event logs gave absolutely nothing.

I also noticed TAP driver in Connect is from 2019. Any chances it's missing something from newer TAP driver versions that makes it Windows 11 netsh-incompatible?

It seems Connect client does not allow to use IPAPI or DHCP for autoconfiguration either instead of netsh, changing ip-win32 setting has no effect.

[pormiston]

Hello pormiston, and others,

Can you give any information on what for example the routing table looks like when it is working correctly and when it has stopped working? There may be a clue in there. Something might be removing routes. To be honest we're just guessing at this point. Our tests work but we see people reporting issues but we are not getting any logs or data that indicates where the problem might be. If the logs contain any sensitive data submit a ticket on https://openvpn.net/support instead.

Kind regards,
Johan

Ok sorry slow response, but still happening will log a case.

[Michiganbb]

I just logged in and see this routing table question.
I will do as requested.

Please keep in mind that it does not simply "stop working"
It never works for the first 60 seconds exactly of the session.
After 60 seconds it begins to pass traffic.

I will tape snapshots if the routing table both before and after as you have asked.
Also can you or the other person update here if a case was submitted as indicated above?
And any progress? Thanks.


--------------------------------------------------------------------------------------------------------------------
Same problem remains one full year later, there have been no software updates to the V3 release version client in all this time.

I have since tried on many different systems computers and firewalls..
And with PFSense OpenVPN server 2.6.0 and 2.7 beta
Same problem.
Client connects but does not pass any traffic through VPN.
EXACTLY one minute (60 seconds) later it begins to pass traffic and works.

Frustrating enough that I have put everyone on the old V2 client that actually works properly.

[NikolayK]

Hi guys,
I also had a problem: after installing updates on February 2023, the openvpn client stopped working (the connection is established but the traffic does not pass).
Solution: disable virtual network adapter "OpenVPN Data Channel Offload" in windows device manager

[sniperkitten]

Frustrating enough that I have put everyone on the old V2 client that actually works properly.

Hi Michiganbb

Does it work for you with Windows 11 and the v2.7.1 OpenVPN connect client which is still available for download on this url?

https://openvpn.net/client-connect-vpn-for-windows/

Thanks

[altitude]

I've seen this problem on both Windows 10 (for years) and 11. On some computers it always works fine and on some others there is always a delay. With both OpenVPN Connect clients v2 and v3. Looks like it takes Windows 60 or 70 seconds to route the traffic correctly.

Try this: disable IPv6 on the TAP adapter (or even on all adapters)

Never seen this issue when using OpenVPN Community build

[Michiganbb]

It looks like a new Windows client was recently released as I just now saw a notification from the software itself.
This prompted me to uninstall the client and go get the latest and install it.
And I have never before seen a notification from the client like this that there is a new version available.
Installed the new client on a windows 11 machine and it connects to a distant PFSense 2.6.0 openvpn server and passes traffic right away.
It's my first test but it looks like this very long ongoing issue with Win11 might be fixed in this release.
I have been meaning to file a bug report on this versus just living with it or installing the older V2 client to get around it.
Sorry for being so lazy on my end.
I am looking around for release notes for the new 3.3.7 (2979)
Not found them yet.
No "about" or links within the software client itself.
Here's the link to release notes.
No fixes or anything are mentioned.
Only changes since Feb. 2022 are "Updated information exchange for OpenVPN Cloud users."

https://openvpn.net/vpn-server-resource ... hange-log/

[Michiganbb]

I mispoke, it still does not work and has the problem.
And I don't know why I thought it might be fixed.
It seems that immediately after install it worked, giving me an impression it may have been fixed.

I have since tested on three different systems and locations.
Same exact problem persists.
I guess after two years I should actually gather details and file a bug report on this.

[Sappin]

Hello,
I'm new to this forum, but I want to try to add some light to this post.

In a nutshell. When I go to look at the traffic on the interfaces I can't see any inbound, only outbound, so, I do an experiment. I don't know why I have 4 VPN adapter connections on my windows.

• OpenVPN Data Channel Offload (what is this...)
  OpenVPN TAP-Windows6 (TAP-Windows V9 Adapter)
  OpenVPN Wintun
  VPN - VPN Client

So, I've disabled all networks except the main one, and tried to enable one by one. If I leave only the OpenVPN TAP-Windows6 network along with the main Ethernet the VPNs work normally again.

I hope this helps someone.