-
Notifications
You must be signed in to change notification settings - Fork 19
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
Set the same MTU for the NSC internal interface as the base interface has #514
Comments
… has Closes: networkservicemesh#514 Signed-off-by: Laszlo Kiraly <[email protected]>
@ljkiraly Last I checked... the MTU on the interface in the NSC was set as the smallest MTU along the path, where the MTU for tunneled interfaces was calculated by subtracting overhead from the underlying interface. What are you seeing that differs from that? |
@edwarnicke Yes, for vxlan mechanism the MTU is set correctly. I missed to adjust the MTU in case of remote vlan mechanism. I'm unsure if the MTU should be decreased by the VLAN tag size (4 bytes) for the interface injected in NSC Pod. |
Based on kernel documentation the MTU does not include link layer header overhead. |
@ljkiraly You are correct. |
… has Closes: networkservicemesh#514 Signed-off-by: Laszlo Kiraly <[email protected]>
… has (#515) Closes: #514 Signed-off-by: Laszlo Kiraly <[email protected]>
Description
In case of vlan remote mechanism the MTU of the interface injected in NSC Pod is not adjusted.
Possible solution
Fetch the base interface MTU and include it into the connection.Context.
The text was updated successfully, but these errors were encountered: