Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bwtester: enhancements #210

Open
matzf opened this issue Nov 19, 2021 · 0 comments
Open

bwtester: enhancements #210

matzf opened this issue Nov 19, 2021 · 0 comments

Comments

@matzf
Copy link
Contributor

matzf commented Nov 19, 2021

Possible bwtester enhancements, extracted from discussion in #209:

  • Improve parameter parsing to allow to properly specify zero duration tests (currently, can only specify zero bandwidth). At the same time, support for fractional seconds should be added by using time.Duration types throughout.

  • Infinite test duration; at the moment we can only pick <= MaxDuration (now 5 minutes)

  • Fine tune reporting: report inter packet delays over certain threshold.

  • Instant reporting. Configure reporting every N seconds.

  • Allow to specify pattern for packets to easily identify them in packet traces etc. More generally, do not require each packet to be full of AES counter mode PRG data. This is overkill (and not "secure" anyway as the key is transmitted in plaintext). Suggested structure for a test data packet:

    • session identifier (not strictly necessary, but might be helpful)
    • packet index
    • user chosen pattern
    • a fixed, repeated byte value (e.g. 0xca) to detect truncation

    Possibly, including a timestamp could also be useful to correlate send with receive times.

  • Require round trip confirmation before starting test -- it's a bit too easy for a client to spoof its source address and so abuse the bwtestserver to blast at a different host. Maybe even better / simpler would be to just use quic for the control channel.

matzf added a commit that referenced this issue Nov 19, 2021
Burster and cbrtester, while useful at the time for debugging specific
issues with the routers, are somewhat redundant with the functionality
of the bwtester applications.
Moving forward, the idea to integrate the useful bits of these two tools
into the bwtester instead; see #210.
matzf added a commit that referenced this issue Dec 3, 2021
Burster and cbrtester, while useful at the time for debugging specific
issues with the routers, are somewhat redundant with the functionality
of the bwtester applications.
Moving forward, the idea to integrate the useful bits of these two tools
into the bwtester instead; see #210.
matzf added a commit that referenced this issue Dec 3, 2021
Burster and cbrtester, while useful at the time for debugging specific
issues with the routers, are somewhat redundant with the functionality
of the bwtester applications.
Moving forward, the idea to integrate the useful bits of these two tools
into the bwtester instead; see #210.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant