Page MenuHomeFreeBSD

epair tests: test PCP tagged packets
ClosedPublic

Authored by kp on Apr 10 2023, 1:05 PM.
Tags
None
Referenced Files
Unknown Object (File)
May 16 2024, 3:48 PM
Unknown Object (File)
Dec 20 2023, 5:42 AM
Unknown Object (File)
Dec 12 2023, 2:43 AM
Unknown Object (File)
Nov 28 2023, 4:54 AM
Unknown Object (File)
Nov 22 2023, 6:16 PM
Unknown Object (File)
Nov 22 2023, 11:29 AM
Unknown Object (File)
Nov 22 2023, 11:14 AM
Unknown Object (File)
Nov 13 2023, 4:53 PM

Details

Summary

PR: 270736
MFC after: 1 week
Sponsored by: Rubicon Communications, LLC ("Netgate")

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

kp requested review of this revision.Apr 10 2023, 1:05 PM
This revision was not accepted when it landed; it landed in state Needs Review.Apr 10 2023, 3:56 PM
This revision was automatically updated to reflect the committed changes.
tests/sys/net/if_epair_test.sh
52

This comment is misleading. Actually same PCP can also lead the problem.

When I reported, I intended to debug / observe (via tcpdump) how the PCP is tagged. A different PCP is useful.

54

Sorry for late response.

In case the test fails (regression), does ping need a timeout option to prevent too long delay before it returns ?