You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some keywords, like VLAN and MPLS, implicitly adjust offsets. New protocols not
yet handled by pcap-filter may also require offset jumping, but are not part of
the existing known protocol code. Allowing arbitrary offset adjustments by users
supports overcoming long standing "vlan X or vlan Y" issues, albeit with awkward
syntax, and for jumping over new protocols not yet handled explicitly, like
VNTag.
This second attempt switches from adjusting compile time static offsets to using
the variable arguments already baked into the offset structs to allow use with
nvarg to generate either fixed or dynamically computed jumps. There is no
support for "set to X"; all actions are increment or decrement. There is also no
support at this time for selecting which offsets to adjust. That can be added
once the basic concept is flushed out and there's some agreement on if this is a
desired feature, syntax, and implementation approach.
Initially my thoughts for a next commit to support selecting offset are
something like `off-linkhdr` or `off-nl` or `off-linkpl` for each type of offset
that might be reasonable for an end user to want to adjust themseleves.
0 commit comments