Repository navigation
fix(link): L2TPv2 and OSPF drop the octets past their own Length field on rebuild #1455
Description
Bug. L2TPv2 and OSPF have no trailer key, so octets captured past their own Length field are lost on rebuild. IPv4 and IPv6 keep these as trailer (#1209/#1431), and IPX does the same (#1435).
Repro on main (b14d676c5):
raw = bytes.fromhex('4002000800010002') + b'pp' # L2TPv2 with Length=8, 10 octets captured
L2TPv2.from_data(L2TPv2(raw, 10).info).data # 4002000800010002: 8 of 10 octetsOSPF behaves the same way: a Packet Length of 24 followed by b'zz' rebuilds 24 of 26 octets. I reproduced the L2TPv2 case myself; the OSPF case comes from the #1454 worker.
Activity
test(protocols): edge-case round trips for every layer family (#1202)
JarryShaw commentedon Oct 9, 2026
A worker is on it now, on branch
fix/1455-l2tpv2-ospf-trailer.fix(l2tpv2,ospf)!: keep the octets past the Length field as captured (#…
test(protocols): edge-case round trips for every layer family (#1202)
test(protocols): edge-case round trips for every layer family (#1202) (…
fix(l2tpv2,ospf)!: keep the octets past the Length field as captured (#…
test(roundtrip): drop the edge-case gaps that #1460, #1462 and #1463 …
fix(schema): a header cut inside a fixed-width field rebuilds as capt…