From: Pete Heist <pete@heistp.net> To: Dave Taht <dave.taht@gmail.com> Cc: flent-users <flent-users@flent.org> Subject: Re: [Flent-users] irtt on flent-london Date: Fri, 11 Jan 2019 17:31:29 +0100 [thread overview] Message-ID: <095D8EA2-8670-4D6C-93A6-7DE5CDEAF47D@heistp.net> (raw) In-Reply-To: <CAA93jw4mX64VEjdTzSPaLTBTAwY3eATgvEpvCrED4HOy-Y0Xag@mail.gmail.com> > On Jan 11, 2019, at 5:00 PM, Dave Taht <dave.taht@gmail.com> wrote: > > I just turned it on again (I think it had crashed). Interesting, afaik I don’t think there’s a code path by which you wouldn’t get an error message in case of a socket or related error, and malformed packets should just result in drop and log. A native crash, I’m not sure what you’d see, but I’ve never seen that after dozens of testing hours. I’d _love_ to know what happened. It might be worth compiling from HEAD using Go 1.11.4, in case there was some compiler or runtime bug with whatever it was compiled with. > I would like to enable irtt fully across the flent network, and with > liberal defaults (longer tests, shorter intervals). Can you suggest a > useful set of defaults to use? Maybe just: irtt server -i 1ms plus whatever bind option is needed. Unlimited length tests and packet sizes are the default, and less than 1ms isn’t likely to be useful on the open Internet, I suppose? > Another option is to make several versions available on different port > numbers with different default dscp markings. I'd get a kick out of > being to test udp-lite, as another example. DSCP marking can currently only be selected by the client, and the server can disallow that if it wants. It could be possible as a new flag to set a default on the server, which is passed to the client during its opening handshake. I think I could do that without a protocol version bump. Feature request? _______________________________________________ Flent-users mailing list Flent-users@flent.org http://flent.org/mailman/listinfo/flent-users_flent.org
next prev parent reply other threads:[~2019-01-11 16:32 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-01-11 9:29 Pete Heist [not found] ` <87tvif4dsz.fsf@toke.dk> [not found] ` <CAA93jw4mX64VEjdTzSPaLTBTAwY3eATgvEpvCrED4HOy-Y0Xag@mail.gmail.com> 2019-01-11 16:31 ` Pete Heist [this message] 2019-01-25 8:26 ` Pete Heist 2019-01-26 5:07 ` Dave Taht 2019-02-01 2:47 ` Pete Heist 2019-02-05 13:46 ` Pete Heist
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://lists.flent.org/postorius/lists/flent-users.flent.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=095D8EA2-8670-4D6C-93A6-7DE5CDEAF47D@heistp.net \ --to=pete@heistp.net \ --cc=dave.taht@gmail.com \ --cc=flent-users@flent.org \ --subject='Re: [Flent-users] irtt on flent-london' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox