Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

connection.switch.arp_inspection potential spurious result #1145

Open
duncangreene opened this issue Feb 19, 2025 · 1 comment
Open

connection.switch.arp_inspection potential spurious result #1145

duncangreene opened this issue Feb 19, 2025 · 1 comment

Comments

@duncangreene
Copy link

Describe the bug
Conducted separate 2 tests on the same DUT, from separate Tetsrun machines (not sure whether this makes a difference, as the machine hardware/spec for both machines is identical).

Test 1
Image

Test 2
Image

For test 2 this was shown in the logs.
Image

However at the same timestamp in connection.pcap, the DUT can clearly be seen announcing that 10.10.10.12 is at 00:60:74:f0:29:90.
Image

Is this a race condition?

Additionally, an ARP packet pertaining to 10.10.10.14 doesn't appear in connection.pcap until 7 minutes later at 15:45:07. How can this be reported/inferred at 15:38:11 in the log file above?
Image

Expected behavior
Identical results should occur on identical tests of the same DUT.

Error logs
QSC QIO-L4O v9.13.0-2412.002 (test 1).zip
QSC QIO-L4O v9.13.0-2412.002 (test 2).zip

Environment (please provide the following information about your setup):

  • Version 2.1
@duncangreene
Copy link
Author

Same "Device is sending false ARP response" observed on this completely different device.

RDL DDS-RN42 v4.1.4.2.zip

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

No branches or pull requests

1 participant