Quickstart needs more details

[chrispsommers]

The Quickstart leaves much to the imagination concerning what should be connected to eth1 in order to get "good" test results. What kind of DUT setup make sense? Explain the test a little better (we send x frames of length Y...) and show representative output.

Use of eth1 should be stated as an assumption - many Linux PCs come up with different device names e.g. eno1, enp0s3, etc.). Inform the user to change as needed.

[Alestrix]

No only that, but it completely leaves out the architecture. There is an architecture picture, but no explanation what each element does. E.g. what does the protocol-engine do (compared to the traffic-engine)? If I want to do a network connection test, what are the source and destination endpoints?