You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: