The byte ordering of the ARP Response NF was correctly getting MAC address, but would get the IP address backwards. With a quick one line fix using rte_cpu_to_be_32 the MAC address and IP address are both correct.
Before:
As you can see the IP address reported by the ARP response is 1.1.10.10, when in fact the correct IP is 10.10.1.1.
We can see here that the HWAddress of onvm-link-0 is incomplete.
After:
We can see that ARP was giving a response and finding it at onvm-link-0.
I was able to verify that onvm-link-0 is the correct hostname from arp -v as well as using arping
Summary:
Usage:
This PR includes
Resolves issues
Breaking API changes
Internal API changes
Usability improvements
Bug fixes
X
New functionality
New NF/onvm_mgr args
Changes to starting NFs
Dependency updates
Web stats updates
Merging notes:
Dependencies: None
TODO before merging :
[X] PR is ready for review
Test Plan:
The change was tested using arping, tcpdump, arp -v, and route -n to ensure correct MAC and IP.
The byte ordering of the ARP Response NF was correctly getting MAC address, but would get the IP address backwards. With a quick one line fix using
rte_cpu_to_be_32
the MAC address and IP address are both correct.Before:
As you can see the IP address reported by the ARP response is 1.1.10.10, when in fact the correct IP is 10.10.1.1.
We can see here that the HWAddress of
onvm-link-0
is incomplete.After:
We can see that ARP was giving a response and finding it at
I was able to verify that
onvm-link-0
.onvm-link-0
is the correct hostname fromarp -v
as well as usingarping
Summary:
Usage:
Merging notes:
TODO before merging :
Test Plan:
The change was tested using
arping
,tcpdump
,arp -v
, androute -n
to ensure correct MAC and IP.