Skip to content

Conversation

@tony-josi-aws
Copy link
Member

Description

While egress packets that are destined to addresses outside of the endpoint's subnet are routed to the gateway, and, if the gateway address happens to be missing from the ARP cache, the ARP lookup for the gateway was performed on incorrect address (the original address to which the packet was destined) instead of the gateway address, leading to the ARP lookup to fail as the target address is outside of the subnet.

Thanks @nwf for reporting this issue in #1244.

This issue is now fixed by passing the correct address to the code that performs the ARP lookup of the gateway.

Test Steps

Tested on STM32F4 by verifying whether the ARP table gets populated with gateway address entry when a packet is sent outside of the subnet.

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

#1244

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

@tony-josi-aws tony-josi-aws requested a review from a team as a code owner May 6, 2025 16:00
@nwf
Copy link

nwf commented May 6, 2025

LGTM. Thank you!

@tony-josi-aws tony-josi-aws merged commit 2091e15 into FreeRTOS:main May 13, 2025
10 checks passed
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.

4 participants