4ffe32fd89
Improve: add default mtu for fd device
3 years ago
8fcd8fee85
Fix(fd): compile error
3 years ago
f6ba31f121
Feature: support fd device
Experimental support for file descriptor based device, may be used like `fd://3`
3 years ago
bf3f4599cc
Chore(tun): remove with options
3 years ago
dc8e4f1ba1
Feature: new fd driver
3 years ago
c478adee34
Fix: rwbased interface implementation
3 years ago
525d424fca
Chore: go1.17 build constraints
3 years ago
94c0b4a873
Chore: rename SetForwarding to SetForwardingDefaultAndAllNICs
4 years ago
70afaf3d55
Fix(stack): update udp transport
4 years ago
b51ad6feb1
Fix(rwbased): endpoint interface
4 years ago
1bd8029562
Optimize: use gvisor tun for linux
4 years ago
a1847d7153
Fix: udp for gvisor stack
4 years ago
82ac59b0f2
Fix: invalid argument when set MTU ( https://github.com/xjasonlyu/tun2socks/issues/33 )
4 years ago
b2b7e8bc46
Chore(tun): minor changes
4 years ago
0e1e04acc7
Fix: avoid extra copy on windows
4 years ago
3f73becd66
Fix: ignore static check
4 years ago
14b905c125
Feature: full 64bit support
4 years ago
e849c9a451
Fix(stack/udp): shadow variables
4 years ago
ae77a8a009
Refactor: autonomize core package
4 years ago
ace24826d2
Chore: move stack & device to core
4 years ago
6f89409a03
remove v1
4 years ago
34377270a3
update core
4 years ago
9f38062a41
sync with eycorsican/go-tun2socks
5 years ago
4d70042a38
tune ttl and mtu
5 years ago
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)
5 years ago
8d6508c52f
update core
5 years ago
757fd11af5
fix buffer pool
5 years ago
51e02d0236
Delete buffer_pool.go
5 years ago
92a111440e
format code
5 years ago
c1740d8704
resize core bufsize
5 years ago
6d01dec5a4
add go-tun2socks code
5 years ago
xjasonlyu