Network & Infrastructure / IPv6, TCP & Transport Engineering
IPv6 extension headers and inconsistent forwarding policy
An application using IPv6 works across one provider but fails across another when additional headers are present. Hardware parsing limits or explicit policy can produce path-specific behavior.
Environment and inputs: Dual-stack routed networks and transport endpoints; validate the complete path and the active operating-system version. Diagnostic/design example; not tested on production equipment.
Collect the evidence
Record the actual extension-header chain, packet size, fragmented state and drop counters at each administrative boundary. Compare an otherwise equivalent packet without the extra headers.
Explain the result
IPv6 extension headers change how downstream devices locate transport information. Support and filtering policy vary; a generic IPv6 permit does not guarantee identical handling of every header chain.
Plan the fix
Use the minimum headers required by the application and align permitted traffic with documented network support. Correct a demonstrated policy mismatch rather than allowing arbitrary malformed chains.
Check the result and rollback
Validate the required packet form over each normal and backup path. Revert if policy changes weaken intended controls or unsupported packet parsing pushes excessive traffic to the control plane.