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

Configurable TCP max seg size #40

Open
mwindower opened this issue Dec 21, 2020 · 2 comments
Open

Configurable TCP max seg size #40

mwindower opened this issue Dec 21, 2020 · 2 comments

Comments

@mwindower
Copy link
Contributor

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"
@mwindower
Copy link
Contributor Author

needs validation from a real cluster

@majst01
Copy link
Contributor

majst01 commented Apr 29, 2021

Is this still a valid issue

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