diff options
| author | Zeling Feng <zeling@google.com> | 2020-09-16 16:23:59 -0700 |
|---|---|---|
| committer | gVisor bot <gvisor-bot@google.com> | 2020-09-16 16:26:10 -0700 |
| commit | 64aae6bbd6ab8c23ee48fd6e7315c27c2cbf2ea4 (patch) | |
| tree | 6e08f70b058082d5a4dd025402237ea9c4b18c39 /test/fuse | |
| parent | b6d165fe98b908a7aa97e3fadd61ddd3731be915 (diff) | |
Cleanup device name confusion in packetimpact testbench
There are two device names on the test net.
- The sniffer/injector device which is always a linux device. Only the
testbench library is interested in this device.
- The device which is on the DUT. It happens to be the same device as
the former if DUT is linux. An individual test might be interested in
this device if the test cares about the device name.
PiperOrigin-RevId: 332112968
Diffstat (limited to 'test/fuse')
0 files changed, 0 insertions, 0 deletions