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
Feature request: Separate MTU interface values for IPv4 and IPv6 #2643
Comments
We opted for a combined MTU solution in #2553 for 6RD and 6TO4. It's a unclear what 6in4 you mean. 6RD, 6TO4, GIF? |
Thanks for explaining. I'm unaware of how to separate IPv4 and IPv6 MTU if we use the same device for both going out? |
I have check my current configuration, and just to be able to set radvd option : AdvLinkMTU to a different value than the interface MTU should work. |
I'd opt for the radvd improvement as well. That seems doable. |
Checking the code and the new 6rd MTU feature this should start working in 18.7.2 automagically when you set your interface MTU to 1500 so it will set 1480 for 6rd and also advertise it correctly. |
Ok not quite yet, it tracks its own MTU which is different from the parent, but not unfixable :) |
Some ISPs offer IPv6 connetivity throw 6in4 and in some case the 6in4 tunnel endpoint is the box itself.
As such, in some cases PMTU discovery can fail and it is sometimes necessary to explicitly define a lower MTU interface value.
So for ip6 working we need to put on the lan MTU 1480 and have radvd advertise mtu 1480.
Shrinking the MTU to accommodate IPv6 results in poor IPv4 connectivity and vise versa.
Best regards,
The text was updated successfully, but these errors were encountered: