An ARP Request message is sent to the DUT, but its Hardware address space (or type) field is set to an unassigned value (42). A check of that field is the first test performed by the pseudo code on page 5 of RFC 826. Therefore no reply should be sent nor any updates made to the DUT's translation table. To verify that the DUT did not update the translation table, an IPv4 packet with its source address set to the value in the ARP Request's Protocol Sender Address field is sent to the DUT.
test is Fail on Zephyr3.2.0 on qemu_x86
References
RFC 826: page 5
Results
b'FAIL: icmp.v4 DUT did not send an IP datagram response.'
b'FAIL: udp.v4 DUT did not send an IP datagram response.'
Environment (please complete the following information):
OS: (e.g. Linux )
Toolchain (e.g Zephyr SDK)
Commit SHA or Version used: Zephyr3.2-rc1
hakehuang
commented
2 years ago
Describe the bug
An ARP Request message is sent to the DUT, but its Hardware address space (or type) field is set to an unassigned value (42). A check of that field is the first test performed by the pseudo code on page 5 of RFC 826. Therefore no reply should be sent nor any updates made to the DUT's translation table. To verify that the DUT did not update the translation table, an IPv4 packet with its source address set to the value in the ARP Request's Protocol Sender Address field is sent to the DUT.
test is Fail on Zephyr3.2.0 on qemu_x86
References
RFC 826: page 5
Results
b'FAIL: icmp.v4 DUT did not send an IP datagram response.' b'FAIL: udp.v4 DUT did not send an IP datagram response.'
Environment (please complete the following information):
OS: (e.g. Linux ) Toolchain (e.g Zephyr SDK) Commit SHA or Version used: Zephyr3.2-rc1