Full network redirect initial delay... - WeOnlyDo Discussion board

Full network redirect initial delay... (wodVPN)

by buruss, Thursday, December 11, 2014, 10:33 (3396 days ago)
edited by buruss, Thursday, December 11, 2014, 10:51

Hi,

I'm testing "VB\Component\2.full network redirection" sample.
And it's working quite well.

Searching and connecting succeed immediately after click those buttons.
But After checking "redirect to remote peer" checkbox on both peers, It takes about 50 to 60 seconds for pinging each other peer to succeed. and then everything works smoothly.

This happens especially after change wod adapter's IP address.

How can I shorten this delay time?

Here's my configuration.

wodVPN.dll version: 2.3.2.143 (32bit)
wod0205.sys version: 2.0.0.5 (64bit)

[Computer1]
os: windows 7 64bit
wod IP: 10.60.0.1
wod subnet: 255.255.255.0

[Computer2]
os: windows 7 64bit
wod IP: 10.60.0.2
wod subnet: 255.255.255.0

Thanks in advance.

Full network redirect initial delay...

by wodSupport, Thursday, December 11, 2014, 16:24 (3395 days ago) @ buruss

Hi.

I'm aware that sometimes this is the problem, but I don't think we can solve it at application level. Problem is that socket stack sends ARP requests with 'who has IP 10.x.x.x' on his own timing, and wodVPN cannot answer them since.. well, it's not yet running, and you have started 'pinging' remote side before that point.

When wodVPN starts and connection is established, from this point forward he does answer them so ping (and other TCP/IP packets) starts getting replies, but question is how long it will take until next time Windows asks for it.

When connection is established with remote peer, we try to 'inject' this ARP entry to arp table, but obviously this doesn't work in all cases.

This delay happens when you change IPs often (during tests, most commonly). Once it is in the ARP table, it usually works almost immediately.

Hope this helps!
Kreso