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
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: