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)
Wed, Mar 18, 3:13 PM
Unknown Object (File)
Wed, Mar 18, 8:42 AM
Unknown Object (File)
Wed, Mar 18, 2:48 AM
Unknown Object (File)
Tue, Mar 10, 10:09 PM
Unknown Object (File)
Sat, Feb 28, 11:00 PM
Unknown Object (File)
Sat, Feb 28, 3:41 AM
Unknown Object (File)
Feb 8 2026, 2:23 PM
Unknown Object (File)
Feb 7 2026, 6:39 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 ?