From: "Toke Høiland-Jørgensen" <notifications@github.com>
To: tohojo/flent <flent@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [Flent-users] Re: [tohojo/flent] How to create two simultaneous tests with different bandwidth in both hosts? (#217)
Date: Tue, 08 Dec 2020 05:54:43 -0800 [thread overview]
Message-ID: <tohojo/flent/issues/217/740632941@github.com> (raw)
In-Reply-To: <tohojo/flent/issues/217@github.com>
[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]
lealog <notifications@github.com> writes:
> Hi,
>
> I'm trying to test a scenario where I have two PCs connected to the router on LAN side. 1 PC will create congestion and another PC simulating a Gaming console.
> I would like to know if flent was any way to create two simultaneous streams with different bandwidths.
>
> Example:
> PC Congestion will use test rrul_be to try force the Bufferbloat issue.
> PC Gaming will have a TCP stream with 15Mbps Download and 1Mbps Upload and measuring the latency and jitter.
>
> Any possibility to execute this scenario?
There's not really any 'fixed bandwidth' tests like you're describing
available in Flent, no. You could perhaps simulate it by putting a
shaper on the network interface of the gaming PC enforcing the
bandwidth, and then just running a TCP test. The traffic won't look like
gaming traffic, but you can get the bandwidth you want, and you can
still measure the impact on cross-traffic on that traffic...
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/217#issuecomment-740632941
[-- Attachment #2: Type: text/html, Size: 2184 bytes --]
next prev parent reply other threads:[~2020-12-08 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 18:29 [Flent-users] " lealog
2020-12-08 13:54 ` Toke Høiland-Jørgensen [this message]
2020-12-08 16:33 ` [Flent-users] " lealog
2020-12-08 16:45 ` Toke Høiland-Jørgensen
2020-12-08 23:36 ` lealog
2020-12-17 14:40 ` Toke Høiland-Jørgensen
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=tohojo/flent/issues/217/740632941@github.com \
--to=notifications@github.com \
--cc=flent@noreply.github.com \
--cc=reply+AHVNJP6TPPV377UU5B7OTO553NTKHEVBNHHC2LQFSM@reply.github.com \
--cc=subscribed@noreply.github.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox