Skip to content

Conversation

@ActoryOu
Copy link
Member

[IPv6] Revert PR#927 "Allow buffer length to be greater than IP packet in IPv6"

Description

Revert #927 because we're failing one critical test case in protocol tester.

Test Steps

Run test case IPv6/Datagram/009

Checklist:

  • I have tested my changes. No regression in existing tests.
  • I have modified and/or added unit-tests to cover the code changes in this Pull Request.

Related Issue

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@ActoryOu ActoryOu requested a review from shubnil June 28, 2023 09:47
Copy link
Contributor

@htibosch htibosch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The packet length in IPv6 seems to be more critical than in IPv4, I didn't know that.
Note that we'll have to change the reception in the SAM driver: subtract 2 bytes from the received length.

@ActoryOu
Copy link
Member Author

The packet length in IPv6 seems to be more critical than in IPv4, I didn't know that. Note that we'll have to change the reception in the SAM driver: subtract 2 bytes from the received length.

It's good to see your comment here.
Yeah it's better to handle this kind of "extra length" in network interface itself.

@shubnil
Copy link
Contributor

shubnil commented Jun 28, 2023

The check for packet payload greater than the header length is specific to a particular SKU of SAM board. Hence, the decision to revert this change, so that the particular Network Interface can take the necessary active and pass the buffer to the FreeRTOS-plus-TCP stack in the standard form where the payload size matches with the header payload length.

@ActoryOu ActoryOu merged commit 63651d0 into FreeRTOS:dev/IPv6_integration Jun 28, 2023
@ActoryOu ActoryOu deleted the RevertLength branch June 28, 2023 10:10
@shubnil
Copy link
Contributor

shubnil commented Jun 28, 2023

The packet length in IPv6 seems to be more critical than in IPv4, I didn't know that. Note that we'll have to change the reception in the SAM driver: subtract 2 bytes from the received length.

Do we know why we have those 2 extra bytes and if we will ever need them in the stack for any future processing.

@htibosch
Copy link
Contributor

The patch #950 should correct the number of bytes received.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants