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

do not fragment flag #1510

Closed
sergey-safarov opened this issue Apr 24, 2018 · 4 comments
Closed

do not fragment flag #1510

sergey-safarov opened this issue Apr 24, 2018 · 4 comments

Comments

@sergey-safarov
Copy link
Member

looks as do not fragment flag is applied to TCP transport by default
Later will test on default config.

@sergey-safarov
Copy link
Member Author

example of INVITE with do not fragment flag is enabled
mtu.pcapng.gz

@miconda
Copy link
Member

miconda commented Apr 25, 2018

This is not something done in Kamailio, but more about the tcp/os stack implementation. Usually tcp sends with do not fragment flag set in order to adapt to the largest MTU that can be used on the path. Not aware if this is something that can be configured at OS level, but I checked kamailio tcp code and there is no such flag set.

If you want to discuss more, bring this topic to sr-users, there might be other people that know more about system options/how to tune this.

@miconda miconda closed this as completed Apr 25, 2018
@sergey-safarov
Copy link
Member Author

Thanks Daniel (@miconda)
Looks as this case descriptions is same

@miconda
Copy link
Member

miconda commented Apr 26, 2018

As I get it from that article, then it can be controlled at OS level via:

net.ipv4.ip_no_pmtu_disc = 1

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