Network & Infrastructure / Linux Networking & Host Performance
Veth and bridge MTU consistency for an overlay workload
A container reaches nearby services but loses large packets through an overlay. Host uplinks may have the correct MTU while one veth or bridge boundary remains inconsistent.
Environment and inputs: Linux network namespaces, host routing and network drivers; availability and semantics depend on kernel and driver versions. Diagnostic/design example; not tested on production equipment.
Collect the evidence
Inventory workload interface, veth peer, bridge, tunnel and physical uplink MTUs. Trace a failing packet's actual egress rather than assuming every container shares the same path.
Explain the result
The effective path includes virtual interfaces and encapsulation as well as physical links. A host-wide uplink setting cannot prove that every namespace path carries the intended size.
Plan the fix
Set a coherent workload-to-underlay size budget in the orchestration configuration. Correct generated interfaces at their provisioning source so replacements do not reintroduce the mismatch.
Check the result and rollback
Test new and existing workloads across local, remote and failover paths. Revert if larger settings exceed an underlying segment or smaller settings unnecessarily reduce throughput for unaffected traffic.