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)
Sat, Oct 11, 5:59 AM
Unknown Object (File)
Fri, Oct 10, 5:01 PM
Unknown Object (File)
Fri, Oct 10, 5:01 PM
Unknown Object (File)
Fri, Oct 10, 5:01 PM
Unknown Object (File)
Fri, Oct 10, 11:40 AM
Unknown Object (File)
Wed, Oct 8, 7:08 AM
Unknown Object (File)
Mon, Oct 6, 5:38 PM
Unknown Object (File)
Mon, Oct 6, 2:26 AM

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 ?