Full network redirect initial delay... (wodVPN)
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
Complete thread:
- Full network redirect initial delay... - buruss, 2014-12-11, 10:33
- Full network redirect initial delay... - wodSupport, 2014-12-11, 16:24