14 Commits (ae2fa30e01fceb2d4565ca1320d00e2515399f05)

Author	SHA1	Message	Date
RPRX	6d4194415d	Clean unnecessary code in Trojan	1 year ago
RPRX	be23d5d3b7	XUDP protocol: Add Global ID & UoT Migration ... The first UoT protocol that supports UoT Migration Thank @yuhan6665 for testing	2 years ago
yuhan6665	9e5bc07bf2	Legends never die (#1725)	2 years ago
yuhan6665	84537e98c4	Update xtls and go to 1.19	2 years ago
yuhan6665	578d903a9e	Quic related improvements (#915) ... * DialSystem for Quic DialSystem() is needed in case of Android client, where the raw conn is protected for vpn service * Fix client dialer log Log such as: tunneling request to tcp:www.google.com:80 via tcp:x.x.x.x:443 the second "tcp" is misleading when using mKcp or quic transport Remove the second "tcp" and add the correct logging for transport dialer: - transport/internet/tcp: dialing TCP to tcp:x.x.x.x:443 - transport/internet/quic: dialing quic to udp:x.x.x.x:443 * Quic new stream allocation mode Currently this is how Quic works: client muxing all tcp and udp traffic through a single session, when there are more than 32 running streams in the session, the next stream request will fail and open with a new session (port). Imagine lineup the session from left to right: | | | | | | As the streams finishes, we still open stream from the left, original session. So the base session will always be there and new sessions on the right come and go. However, either due to QOS or bugs in Quic implementation, the traffic "wear out" the base session. It will become slower and in the end not receiving any data from server side. I couldn't figure out a solution for this problem at the moment, as a workaround: | | | | | | | | I came up with this new stream allocation mode, that it will never open new streams in the old sessions, but only from current or new session from right. The keeplive config is turned off from server and client side. This way old sessions will natually close and new sessions keep generating. Note the frequency of new session is still controlled by the server side. Server can assign a large max stream limit. In this case the new allocation mode will be similar to the current mode.	3 years ago
yuhan6665	e93da4bd02	Fix some tests and format code (#830) ... * Increase some tls test timeout * Fix TestUserValidator * Change all tests to VMessAEAD Old VMess MD5 tests will be rejected and fail in 2022 * Chore: auto format code	3 years ago
yuhan6665	e286cdcaa8	Style: format code by gofumpt (#761)	3 years ago
Arthur Morgan	24b637cd5e	Fix: CounterConnection with ReadV/WriteV (#720) ... Co-authored-by: JimhHan <50871214+JimhHan@users.noreply.github.com>	3 years ago
RPRX	7427a55ef1	Adjust Trojan Outbound postRequest	4 years ago
RPRX	2e942e0303	Fix Trojan XTLS	4 years ago
RPRX	f8faf3c8b8	Removal: confonly	4 years ago
RPRX	b4e84603a2	Add XTLS Splice to Trojan Outbound	4 years ago
RPRX	16544c18ab	v1.1.0	4 years ago
RPRX	c7f7c08ead	v1.0.0	4 years ago