-
Notifications
You must be signed in to change notification settings - Fork 85
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
port-forwarding takes time to be stable with MTU > 49192 on kernel >= 4.20 #128
Labels
Comments
It is weird that the issue only happens in kernel >= 4.20, but as the |
https://kernelnewbies.org/Linux_4.20#Networking Suspicious commit (unconfirmed): |
AkihiroSuda
added a commit
to AkihiroSuda/slirp4netns
that referenced
this issue
Aug 20, 2019
…l 4.20 The kernel 4.20 bumped up the default value of `/proc/sys/net/ipv4/tcp_rmem` from 87380 to 131072. This is known to slow down slirp4netns port forwarding: rootless-containers#128 As a workaround, it is recommended to modify `/proc/sys/net/ipv4/tcp_rmem` inside the namespace manually. (No real root privilege is needed) Update rootless-containers#128 Signed-off-by: Akihiro Suda <[email protected]>
AkihiroSuda
added a commit
to AkihiroSuda/slirp4netns
that referenced
this issue
Aug 20, 2019
…l 4.20 The kernel 4.20 bumped up the default value of `/proc/sys/net/ipv4/tcp_rmem` from 87380 to 131072. This is known to slow down slirp4netns port forwarding: rootless-containers#128 As a workaround, it is recommended to modify `/proc/sys/net/ipv4/tcp_rmem` inside the namespace manually. (No real root privilege is needed) Update rootless-containers#128 Signed-off-by: Akihiro Suda <[email protected]>
AkihiroSuda
added a commit
to AkihiroSuda/slirp4netns
that referenced
this issue
Aug 20, 2019
…l 4.20 The kernel 4.20 bumped up the default value of `/proc/sys/net/ipv4/tcp_rmem` from 87380 to 131072. torvalds/linux@a337531 This is known to slow down slirp4netns port forwarding: rootless-containers#128 As a workaround, it is recommended to modify `/proc/sys/net/ipv4/tcp_rmem` inside the namespace manually. (No real root privilege is needed) Update rootless-containers#128 Signed-off-by: Akihiro Suda <[email protected]>
AkihiroSuda
added a commit
to AkihiroSuda/slirp4netns
that referenced
this issue
Aug 20, 2019
The kernel 4.20 bumped up the default value of `/proc/sys/net/ipv4/tcp_rmem` from 87380 to 131072. torvalds/linux@a337531 This is known to slow down slirp4netns port forwarding: rootless-containers#128 As a workaround, it is recommended to modify `/proc/sys/net/ipv4/tcp_rmem` inside the namespace. The file is automatically modified when running with `--configure`. Update rootless-containers#128 Signed-off-by: Akihiro Suda <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bad bandwidth in the first few seconds when MTU > 49192.
This seems related to
#define TCP_MAXSEG_MAX 32768
slirp4netns/vendor/libslirp/src/tcp.h
Line 46 in ed51817
Modifying the
TCP_MAXSEG_MAX
value affects the threshold MTU to hit this issue.Tested commit: ed51817
Reproducible envs:
4.20.0-1.fc30.x86_64 #1
(VirtualBox)5.0.0-23-generic #24-Ubuntu
(VMware Fusion)5.0.0-1011-gcp #11-Ubuntu
(GCE n1-standard-2)5.0.9-301.fc30.x86_64 #1
(VirtualBox)5.1.20-300.fc30.x86_64 #1
(VirtualBox)Unreproducible envs:
4.4.0-101-generic
(Travis)4.9.0-8-amd64 #1
(GCE n1-standard-2)4.15.0-1037-gcp #39-Ubuntu
(GCE n1-standard-2)4.18.16-300.fc29.x86_64 #1
(VirtualBox)4.19.0-5-cloud-amd64 #1
(GCE n1-standard-2)Seems related to the kernel version (>= 4.20)
The text was updated successfully, but these errors were encountered: