Opened 6 years ago

Last modified 6 years ago

#507 assigned defect

missmatch between dual interface mode & meaning

Reported by: aturner Owned by: aturner
Priority: high Milestone: 3.5.0
Component: tcpprep Version: 3.4.4
Keywords: Cc:
Operating System: Add to FAQ?: yes
Hardware: All
Output of tcpreplay -V:

Description (last modified by aturner)

Looking through the docs and code, there seems to be a miss-match in meaning regarding dual interface mode in tcpreplay and using tcpprep cache files. Specifically which interface is "client" traffic and what that means (to the client? from the client?). And what does "primary" or "secondary" interface mean?

Anyways, here's my proposal for dual nic mode:

  • -i (aka primary interface)
    • traffic that client(s) send
    • "matched" when using manual filters like --cidr or --regex
    • RX for khial interfaces (/dev/char/testpacketsX)
  • -I (aka secondary interface)
    • traffic that server(s) send
    • "not-matched" when using manual filters like --cidr or --regex
    • TX for khial interfaces

Change History (2)

comment:1 Changed 6 years ago by aturner

  • Description modified (diff)
  • Status changed from new to assigned

comment:2 Changed 6 years ago by aturner

(In [2621]) Change which interface tcpprep will send "client" and "server"
traffic to. Now traffic client->server will be the primary
interface and server->client traffic will be secondary interface.
refs #507

Note: See TracTickets for help on using tickets.