Jason c18a52bd74 core: process refused TCP data immediately once the connection is ready
If the first TCP data chunk was refused, perhaps due to the
connection was under connecting state (it's almost always the
case), waiting for timers to process the refused data would
introduce a ~250ms (TCP_FAST_INTERVAL) delay for the connection.
(from eycorsican/go-tun2socks)
2019-10-04 21:12:00 +08:00
2019-08-19 17:45:19 +08:00
2019-08-16 14:15:01 +08:00
2019-08-14 23:15:49 +08:00
2019-08-14 23:24:55 +08:00
2019-09-23 17:17:20 +08:00
2019-08-19 14:53:09 +08:00
2019-07-16 11:34:59 +08:00
2019-09-23 17:24:12 +08:00
2019-09-23 17:24:12 +08:00
2019-07-16 11:25:41 +08:00
2019-08-20 16:54:51 +08:00
2019-08-20 16:54:51 +08:00
2019-08-20 16:54:51 +08:00
2019-08-20 16:55:44 +08:00
2019-07-16 15:43:00 +08:00

tun2socks

forked from eycorsican/go-tun2socks

A tun2socks implementation written in Go.

Languages
Go 95.4%
Makefile 3%
Shell 1.2%
Dockerfile 0.4%