Skip to content

Use the configured MTU for veth and loopback - #16984

Open
tamird wants to merge 1 commit into
google:masterfrom
tamird:proposal/veth-network-mtu
Open

tamird wants to merge 1 commit into
google:masterfrom
tamird:proposal/veth-network-mtu

Conversation

@tamird

@tamird tamird commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

The Sentry configures veth and loopback with the maximum IP packet size.
Since 66defd3, the Ethernet wrapper treats that value as a complete
frame budget and subtracts the header. A veth MTU of 1500 consequently
becomes 1486 for both netlink and the TCP route. Setting the loopback
MTU has the same discrepancy that 35d3c6e originally fixed.

Register both virtual devices with an Ethernet wrapper that uses the
network MTU from the underlying endpoint. Both devices pass complete
frames to the receiving stack and have no separate frame-size limit.

The Sentry configures veth and loopback with the maximum IP packet size.
Since 66defd3, the Ethernet wrapper treats that value as a complete
frame budget and subtracts the header. A veth MTU of 1500 consequently
becomes 1486 for both netlink and the TCP route. Setting the loopback
MTU has the same discrepancy that 35d3c6e originally fixed.

Register both virtual devices with an Ethernet wrapper that uses the
network MTU from the underlying endpoint. Both devices pass complete
frames to the receiving stack and have no separate frame-size limit.

@aaltinaydev aaltinaydev left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[🤖] Review agent has no findings.


Automated review agent. Please address valid findings before human review, or close them with a reason.

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

Successfully merging this pull request may close these issues.

2 participants