Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SCTP: Support printing some latest chunk types #994

Closed

Conversation

CacheUseOnly
Copy link

Some new SCTP chunk types are implemented in Linux kernel but not yet supported by tcpdump to print them appropriately. These patches add corresponding supports for chunks below:

Reviewers: marcelo.leitner@gmail.com, lucien.xin@gmail.com
Sign-off-by: luoyuxuan.carl@gmail.com

Yuxuan Luo added 5 commits July 5, 2022 14:29
Add support for printing SCTP I-DATA chunk based on RFC8260 section 2.1

Prints payload when vflag leve is greater than 1.
Add support for printing I-FORWARD chunk based on RFC8260 section 2.3.

Remove REL_CTL (RFC3758) since it is obsolete and it uses the value '0xc2'
of I-FORWARD for CNTL_ACK.

Print stream IDs and message IDs with `-vv` set.
Add support for printing RE-CONFIG chunk based on RFC6525 section3.1.

Prints all optional parameters when `-vv` is set.

Example:
[RE-CONFIG] [OUT SSN RESET: REQ SEQ:, RES SEQ:, Last TSN:, SID 0 1]
Add support for printing ASCONF and ASCONF-ACK chunk based on RFC5061.

Remove REL_CNTL(0xc1) because it's obsolete and conflicts with ASCONF.

Prints all ASCONF parameters with `-vv` set.

`-vv` Example:
[ASCONF] [SEQ: .., ADDR: 192...] [DEL ADDR: C-ID: 0, ADDR: 192...]
[ASCONF-ACK] [SEQ: 4161214189]

`-v` Example:
[ASCONF] [SEQ: .., ADDR: 192...] [DEL ADDR]
Add support for printing PAD chunk based on RFC4820 section3.

Example:
[PAD]
@guyharris
Copy link
Member

Presumably this was replaced by #995, just as #993 was replaced by this.

There's probably some way to update your fork and the pull request made from the fork, so that you don't have to keep creating new fork requests in the process of fixing the Windows build of your change.

Closing.

@guyharris guyharris closed this Jul 6, 2022
@CacheUseOnly CacheUseOnly deleted the revision4.1 branch May 3, 2024 00:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants