Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

push go-quic to 0.50 when you have time. thank you. #1319

Open
Smallthing opened this issue Feb 21, 2025 · 1 comment
Open

push go-quic to 0.50 when you have time. thank you. #1319

Smallthing opened this issue Feb 21, 2025 · 1 comment
Labels
enhancement New feature or request

Comments

@Smallthing
Copy link

Description
你的功能请求是否与某个问题有关?
这个版本修复了不少bug
v0.50.0
This release implements server-side path-probing (as described in section 9 of RFC 9000): quic-go/quic-go#4932, quic-go/quic-go#4933, quic-go/quic-go#4935, quic-go/quic-go#4938, quic-go/quic-go#4939, quic-go/quic-go#4940, quic-go/quic-go#4941, quic-go/quic-go#4944, quic-go/quic-go#4947, quic-go/quic-go#4959.

When the server receives a packet for an existing connection from a different IP address / port, it first needs to probe the new path before it can send packets on that path. This happens when the client experiences a NAT rebinding, and when the client attempts to migrate to a new connection. Previous versions of quic-go would accept the packets from the new path, but never switch to the new path.

use a ringbuffer to store received packets, significantly reducing memory consumption

描述你希望的解决方案
push go-quic to 0.50

@Smallthing Smallthing added the enhancement New feature or request label Feb 21, 2025
@giveup
Copy link

giveup commented Feb 21, 2025

@haruue @tobyxdd 想请教一下大佬,为什么hysteria需要自己维护一个quic-go的fork?因为quic-go的ABI不稳定吗?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants