(posted comment before but didn't see it - so I'm re sending) It looks like the TAP Adapter gets its link up signal as soon as the socket is being connected. Several problems with that: - There is no actual logical connection between the parties. It could be another fake process, an intermediate proxy, or a bad version of OpenSSL, bad keys... etc. The user sees the adapter link brought up and down - and this is misleading as the user thinks that the far end was indeed connected but something happened. - As soon as the TAP adapter link is up, Windows starts to send packets. Normally this is fine, but if the other end is not yet connected (using proxy), the socket buffer starts to fill for no good reason
Looks like there needs to be a logical handshake before link is brought up. My 2 cents Moshe
