Netherlands Server Time-Outs.

[Indingo]

Just an FYI as well, I reported it to customer support but I don't think its being looked into. I strongly believe BolehVPN is leaking on the "CLASSIC-STUN" protocol. I have been able to see BolehVPN Fully-Routed servers with DNS leak enabled leaking through CLASSIC-STUN. "Simple Traversal of UDP Through NAT" Anything we can do to fix that? I can replicated it very easy in wireshark.

[Indingo]

I found NL better, but still have some time-out issues, any word on the CLASSIC-STUN? as well? Also any thing found on the server?

[Indingo]

I'm still having issues with NL.

[Indingo]

Yep.. Just logged on and getting the NL issues again, pages not loading etc etc, I had to turn it off to post.

[Indingo]

bump.

[Chris]

Could we have your latest log? I'd already mentioned your reply to my superior, think he missed it

[Indingo]

Could we have your latest log? I'd already mentioned your reply to my superior, think he missed it

Just made a new one, came to post here on the NL connection, waited a few minutes and gave up, here's the log anyway.

Version Server:  2.3.6

Version Current:  2.3.6

Run script:  0

Checking installed tap driver...

ROOT\NET\0000                                               : TAP-Windows Adapter V9
1 matching device(s) found.

Use port 44358 as management port

Fri Nov 08 20:53:31 2013 OpenVPN 2.2.2 i686-pc-mingw32 [SSL] [LZO2] [OBFUSCATION] [PKCS11] built on Mar 12 2013
Fri Nov 08 20:53:31 2013 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables

Fri Nov 08 20:53:31 2013 Control Channel Authentication: using 'C:/Users/User1/AppData/Local/BolehVPN/cfg/OpenVPN/ta.key' as a OpenVPN static key file
Fri Nov 08 20:53:31 2013 LZO compression initialized
Fri Nov 08 20:53:31 2013 UDPv4 link local: [undef]
Fri Nov 08 20:53:31 2013 UDPv4 link remote: 62.212.85.79:443

Fri Nov 08 20:53:33 2013 write UDPv4: No Route to Host (WSAEHOSTUNREACH) (code=10065)

Fri Nov 08 20:53:35 2013 [server] Peer Connection Initiated with 62.212.85.79:443

Fri Nov 08 20:53:37 2013 TAP-WIN32 device [TAP-Win32 Adapter V9] opened: \\.\Global\{9C7AFA12-3625-4C14-A590-18CBCF21EE1B}.tap
Fri Nov 08 20:53:37 2013 Notified TAP-Win32 driver to set a DHCP IP/netmask of 10.10.10.198/255.255.255.252 on interface {9C7AFA12-3625-4C14-A590-18CBCF21EE1B} [DHCP-serv: 10.10.10.197, lease-time: 31536000]
Fri Nov 08 20:53:37 2013 Successful ARP Flush on interface [19] {9C7AFA12-3625-4C14-A590-18CBCF21EE1B}

OK!

OK!

OK!
Fri Nov 08 20:53:47 2013 WARNING: potential route subnet conflict between local LAN [192.168.0.0/255.255.255.0] and remote VPN [0.0.0.0/0.0.0.0]

OK!

OK!
Fri Nov 08 20:53:47 2013 Initialization Sequence Completed

Run script:  1

I hope the CLASSIC-STUN issue gets looked into as well.

[Chris]

Did you try the winsock reset as pit boss posted ? It's not an issue with the server according to him.

[PitBoss]

Please check on my previous posting to reset your winsock and see if it resolve the issue.
As for CLASSIC-STUN, please elaborate what is your concern on classic STUN as Openvpn uses its own nat transversal and not based on STUN.

[PitBoss]

I found NL better, but still have some time-out issues, any word on the CLASSIC-STUN? as well? Also any thing found on the server?

Just an FYI as well, I reported it to customer support but I don't think its being looked into. I strongly believe BolehVPN is leaking on the "CLASSIC-STUN" protocol. I have been able to see BolehVPN Fully-Routed servers with DNS leak enabled leaking through CLASSIC-STUN. "Simple Traversal of UDP Through NAT" Anything we can do to fix that? I can replicated it very easy in wireshark.

Appreciate if you can forward wireshark report on this as wireshark can identify them as Openvpn but for DNS queries, this is something else. Openvpn only passes or push the DNS to the OS network stack. It is the OS layer that supposed to receive the DNS and add them to the tap adapters. It does not remove the pre-connected DNS from the main adapter. BUT in some cases, especially Windows, it removes them which is quite baffling to most people and when you do a lot of connect and disconnect, it will also corrupt the network registry by not removing certain network information which will cause issue like the one you are facing.

[Indingo]

Did you try the winsock reset as pit boss posted ? It's not an issue with the server according to him.

I did, I mentioned that I tried the winsock reset in my previous postings. I did not find it helped.

I will also attach the wire-shark CLASSIC-STUN log. I will also put a screenshot for you, Its the same on all servers and the one I was using this time was Sweden-FullyRouted.

[Indingo]

In my last post changed .rar of my file to .zip as the web forum does not let me upload .rar files, so just change it if you cant open it.

[PitBoss]

Hmm, appreciate if you can run the same wireshark without VPN connected and after connected.

Looking at your result, seems like those STUN were initiated before the VPN is connected and this connection is persistent on its pre-VPN routing. Those are applications running on UDP with point to point connection. Most probably steam UDP services.

[Indingo]

Hmm, appreciate if you can run the same wireshark without VPN connected and after connected.

Looking at your result, seems like those STUN were initiated before the VPN is connected and this connection is persistent on its pre-VPN routing. Those are applications running on UDP with point to point connection. Most probably steam UDP services.

Nope. I already mentioned to your staff which got ignored in a support ticket. I have tested thoroughly. I have already run tests where the VPN is already active before any steam processes are loaded into memory. I then launch a game Age of Empires 2 HD from steam, and join a multiplayer lobby. While in the lobby players who join connect to my computer directly by-passing the VPN and the same happens in reverse, my computer contacts them outside of the VPN tunnel. I know that this bug/leak happens with AOE2 HD on steam, and its probably not just AOE2 HD, I am pretty sure all CLASSIC-STUN traffic would leak in this manner, I am just not aware/wish to put time into finding other products that use the CLASSIC-STUN protocol. I'm not stupid, if it was a connection initiated before VPN connection, I would have ruled the leak out ages ago. I also wish to report the "Mullvad" VPN I used to test after finding this issue, does not leak. I do not get the same direct requests while using Mullvad VPN. I also wish to point out Mullvad use 128 Blowfish, which is what you used before changing the algorithm. I had this issue before you changed to AES 128 so its not anything to do which that, I had the issue on Blowfish 128 / AES 128 on BolehVPN on all Fully-Routed servers.

I also wish to report my problem with the NL server still persists for what ever reason.

If you want to TeamView me and see the live capture for yourself, you can be my guest.

[Indingo]

I also notice leaks while windows update runs of a similar manner, I think they may just be DNS, but still... should not be happening with DNS leak fix enabled.