Fix ARP lookups for gateway address when destination is outside of subnet #1248
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 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.