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

Lower MTU in the network #72

Open
mitar opened this issue Apr 2, 2016 · 3 comments
Open

Lower MTU in the network #72

mitar opened this issue Apr 2, 2016 · 3 comments

Comments

@mitar
Copy link
Member

mitar commented Apr 2, 2016

To 1458. Because of the tunnel.

@mitar
Copy link
Member Author

mitar commented Oct 27, 2016

We can also try to increase the MTU of the tunnel.

@clonm
Copy link
Member

clonm commented Jul 9, 2019

Why 1458? And did this ever get changed?

With the built-in ping speed test, I am noticing significantly higher speeds (like, factor of 2) using 1024 as the big packet size instead of the default 1500. I'm not sure why this is or if it would hold true for servers in general, but it works for two different iperf servers, 8.8.8.8, and whatever internal google node came up when I did a traceroute for google.com from Cloyne.

Currently all the interfaces on CloyneRouter have MTU set to 1500, with L2 MTU calculated as 1520 except for the tunnel which shows up as 65535. The HE router also has the MTUs set to 1500, but L2 MTU set manually to 1598 (again, except for the tunnels).

Do you think it would be worth trying to tweak those? or is the 1598 because you already increased the MTU of the tunnel and/or should we chalk this up to measurement error with automated testing? (Vern should be proud...)

@clonm
Copy link
Member

clonm commented Nov 4, 2019

bump - is there any reason to think this is still worth tweaking?

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

No branches or pull requests

2 participants