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] ATSAME5x network interface not detecting ICMP packets correctly #1193

Closed
cruxic opened this issue Sep 27, 2024 · 3 comments
Closed

[BUG] ATSAME5x network interface not detecting ICMP packets correctly #1193

cruxic opened this issue Sep 27, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@cruxic
Copy link
Contributor

cruxic commented Sep 27, 2024

The example network interface for ATSAME5x does not correctly detect ICMP packets. The codes checks the protocol byte but fails to also check the Ethernet frame type. This causes it to get false-positive matches for frames which happen to have an 0x01 byte at a certain offset.

The same bug exists in two places in the code: xATSAM5x_NetworkInterfaceOutput() and prvEMACDeferredInterruptHandlerTask(). I will be submitting a pull-request which fixes it.

@jasonpcarroll
Copy link
Member

Hi @cruxic,
Thank you for bringing this to our attention. I will review your PR.

@htibosch
Copy link
Contributor

Good catch, thank you!

In the driver for Zynq, the ICMP packets are detected correctly, both for IPv4 and for IPv6.

The MSP432 driver has same problem and needs correction too.

@aggarg
Copy link
Member

aggarg commented Oct 1, 2024

Thank you for your contribution!

@aggarg aggarg closed this as completed Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants