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

Bug #557 Attempt to correct corrupt packets #603

Merged
merged 1 commit into from
Jun 5, 2020

Conversation

fklassen
Copy link
Member

@fklassen fklassen commented Jun 5, 2020

If packet caplen > packet len, update caplen to equal len.

Although this appears to be impossible if trace was generated from
a reliable source (i.e. libpcap), there appears to be enough pressure
from the community to allow these invalid packets to be sent.

IMHO, I think that if a pcap is invalid, tcpreplay should fail. But it
appears that this is the behavior desired by users.

If packet caplen > packet len, update caplen to equal len.

Although this appears to be impossible if trace was generated from
a reliable source (i.e. libpcap), there appears to be enough pressure
from the community to allow these invalid packets to be sent.

IMHO, I think that if a pcap is invalid, tcpreplay should fail. But it
appears that this is the behavior desired by users.
@fklassen fklassen self-assigned this Jun 5, 2020
@fklassen fklassen merged commit 5ade727 into 4.3.3 Jun 5, 2020
@fklassen fklassen deleted the Bug_#557_correct_some_invalid_packet_lengths branch June 5, 2020 00:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant