We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There may exist network paths that can't handle jumbo frames correctly. The default metal-stack MTU is 9000.
Currently it is investigated if nftables rules like this fix the problem for TCP by setting the max seg size with TCP SYN:
ip saddr 100.127.0.0/17 oifname vlan<PRIVATE_NET_ID> flags syn tcp option maxseg size set 1460 counter comment "mangle maxseg size in" ip daddr 100.127.0.0/17 oifname vlan104010 flags syn tcp option maxseg size set 1460 counter comment "mangle maxseg size out"
The text was updated successfully, but these errors were encountered:
needs validation from a real cluster
Sorry, something went wrong.
Is this still a valid issue
No branches or pull requests
There may exist network paths that can't handle jumbo frames correctly.
The default metal-stack MTU is 9000.
Currently it is investigated if nftables rules like this fix the problem for TCP by setting the max seg size with TCP SYN:
The text was updated successfully, but these errors were encountered: