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

IPOptions_Timestamp does not support multiple IP Address and Timestamp fields #4513

Open
cosmin-ionut opened this issue Aug 30, 2024 · 0 comments

Comments

@cosmin-ionut
Copy link
Contributor

Brief description

When the IPv4 Timestamp option is added to an IP packet, "the originating host must compose this option with a large enough timestamp data area to hold all the timestamp information expected." This involves multiple timestamp fields (and IP addresses fields, based on flag) initialized to 0 / 0.0.0.0.
Currently, scapy supports only one timestamp field within IPOptions_Timestamp(), which means the target host is unable to add any timestamp to the packet, and will reply with an IP Option Timestamp having the overflow flag set to 1.

Scapy version

2.5.0

Python version

3.9.2

Operating system

Linux 5.15.0-118

Additional environment information

No response

How to reproduce

No specific steps. Refer to issue description

Actual result

No response

Expected result

No response

Related resources

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants