TUN-8449: Add flag to control QUIC connection-level flow control limit and increase default to 30MB
This commit is contained in:
parent
d37ad42426
commit
e0b1899e97
|
@ -89,6 +89,8 @@ const (
|
||||||
// Note that this may result in packet drops for UDP proxying, since we expect being able to send at least 1280 bytes of inner packets.
|
// Note that this may result in packet drops for UDP proxying, since we expect being able to send at least 1280 bytes of inner packets.
|
||||||
quicDisablePathMTUDiscovery = "quic-disable-pmtu-discovery"
|
quicDisablePathMTUDiscovery = "quic-disable-pmtu-discovery"
|
||||||
|
|
||||||
|
quicConnLevelFlowControlLimit = "quic-connection-level-flow-control-limit"
|
||||||
|
|
||||||
// uiFlag is to enable launching cloudflared in interactive UI mode
|
// uiFlag is to enable launching cloudflared in interactive UI mode
|
||||||
uiFlag = "ui"
|
uiFlag = "ui"
|
||||||
|
|
||||||
|
@ -718,6 +720,13 @@ func tunnelFlags(shouldHide bool) []cli.Flag {
|
||||||
Value: false,
|
Value: false,
|
||||||
Hidden: true,
|
Hidden: true,
|
||||||
}),
|
}),
|
||||||
|
altsrc.NewIntFlag(&cli.IntFlag{
|
||||||
|
Name: quicConnLevelFlowControlLimit,
|
||||||
|
EnvVars: []string{"TUNNEL_QUIC_CONN_LEVEL_FLOW_CONTROL_LIMIT"},
|
||||||
|
Usage: "Use this option to change the connection-level flow control limit for QUIC transport.",
|
||||||
|
Value: 30 * (1 << 20), // 30 MB
|
||||||
|
Hidden: true,
|
||||||
|
}),
|
||||||
altsrc.NewStringFlag(&cli.StringFlag{
|
altsrc.NewStringFlag(&cli.StringFlag{
|
||||||
Name: connectorLabelFlag,
|
Name: connectorLabelFlag,
|
||||||
Usage: "Use this option to give a meaningful label to a specific connector. When a tunnel starts up, a connector id unique to the tunnel is generated. This is a uuid. To make it easier to identify a connector, we will use the hostname of the machine the tunnel is running on along with the connector ID. This option exists if one wants to have more control over what their individual connectors are called.",
|
Usage: "Use this option to give a meaningful label to a specific connector. When a tunnel starts up, a connector id unique to the tunnel is generated. This is a uuid. To make it easier to identify a connector, we will use the hostname of the machine the tunnel is running on along with the connector ID. This option exists if one wants to have more control over what their individual connectors are called.",
|
||||||
|
|
|
@ -249,6 +249,7 @@ func prepareTunnelConfig(
|
||||||
RPCTimeout: c.Duration(rpcTimeout),
|
RPCTimeout: c.Duration(rpcTimeout),
|
||||||
WriteStreamTimeout: c.Duration(writeStreamTimeout),
|
WriteStreamTimeout: c.Duration(writeStreamTimeout),
|
||||||
DisableQUICPathMTUDiscovery: c.Bool(quicDisablePathMTUDiscovery),
|
DisableQUICPathMTUDiscovery: c.Bool(quicDisablePathMTUDiscovery),
|
||||||
|
QUICConnectionLevelFlowControlLimit: c.Uint64(quicConnLevelFlowControlLimit),
|
||||||
}
|
}
|
||||||
packetConfig, err := newPacketConfig(c, log)
|
packetConfig, err := newPacketConfig(c, log)
|
||||||
if err != nil {
|
if err != nil {
|
||||||
|
|
|
@ -67,6 +67,7 @@ type TunnelConfig struct {
|
||||||
WriteStreamTimeout time.Duration
|
WriteStreamTimeout time.Duration
|
||||||
|
|
||||||
DisableQUICPathMTUDiscovery bool
|
DisableQUICPathMTUDiscovery bool
|
||||||
|
QUICConnectionLevelFlowControlLimit uint64
|
||||||
|
|
||||||
FeatureSelector *features.FeatureSelector
|
FeatureSelector *features.FeatureSelector
|
||||||
}
|
}
|
||||||
|
@ -576,6 +577,7 @@ func (e *EdgeTunnelServer) serveQUIC(
|
||||||
EnableDatagrams: true,
|
EnableDatagrams: true,
|
||||||
Tracer: quicpogs.NewClientTracer(connLogger.Logger(), connIndex),
|
Tracer: quicpogs.NewClientTracer(connLogger.Logger(), connIndex),
|
||||||
DisablePathMTUDiscovery: e.config.DisableQUICPathMTUDiscovery,
|
DisablePathMTUDiscovery: e.config.DisableQUICPathMTUDiscovery,
|
||||||
|
MaxConnectionReceiveWindow: e.config.QUICConnectionLevelFlowControlLimit,
|
||||||
}
|
}
|
||||||
|
|
||||||
quicConn, err := connection.NewQUICConnection(
|
quicConn, err := connection.NewQUICConnection(
|
||||||
|
|
Loading…
Reference in New Issue