Flent-users discussion archives
 help / color / mirror / Atom feed
From: j-breyer <notifications@github.com>
To: tohojo/flent <flent@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [Flent-users] [tohojo/flent] Questions (and Error) regarding rrul_prio (#240)
Date: Wed, 29 Sep 2021 08:47:16 -0700	[thread overview]
Message-ID: <tohojo/flent/issues/240@github.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1922 bytes --]

Hi! I'm currently trying a couple different tests provided in flent, and stumbled across the `rrul_prio` test.

Firstly, I'm curious as to what the labels `BE`, `BE2`, `BE3` and `BE4` stand for - I suppose, the BE should be Best Effort(?)
And for the ping section - the difference between `BE1` and `PRIO`?
Further, their respective ToS or DSCP codes, as I was unable to find them in the docs, to consider them in possible network configurations.

Also, when running the test (mn.h1 and mn.h2 refering to local entries in `/etc/hosts`, connections can be established):
`sudo flent rrul_prio -p all_scaled --local-bind mn.h1 -l 60 -H mn.h2 -o rrul_prio2.pdf -v`
I find the following error:

```
Ping (ms) ICMP PRIO: Starting watchdog with timeout 71
Started TimerRunner idx 17 ('Watchdog [Ping (ms) ICMP PRIO]')
Started PingRunner idx 17 ('Ping (ms) ICMP PRIO')
WARNING: Program exited non-zero.
Runner class: IrttRunner
Command: /usr/bin/irtt client -o - --fill=rand -Q -d 70s -i 0.2s  --dscp=0x10,0x10 --local=mn.h1  mn.h2
Return code: 2
Stdout: 
Stderr: Error: strconv.ParseInt: parsing "0x10,0x10": invalid syntax

WARNING: Unable to parse irtt JSON output: Expecting value: line 1 column 1 (char 0)
WARNING: Command produced no valid data.
Runner class: IrttRunner
Command: /usr/bin/irtt client -o - --fill=rand -Q -d 70s -i 0.2s  --dscp=0x10,0x10 --local=mn.h1  mn.h2
Return code: 2
Stdout: 
Stderr: Error: strconv.ParseInt: parsing "0x10,0x10": invalid syntax
```

Searching a bit through the test config files of your other tests, I found that normally your markings would be configured with DSCP names rather than hex values, maybe there lies the problem?

The plot seems to include data from all connections, despite the Error (as far as I'm aware)

-- 
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/240

[-- Attachment #2: Type: text/html, Size: 3277 bytes --]

             reply	other threads:[~2021-09-29 15:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-29 15:47 j-breyer [this message]
2021-09-29 21:26 ` [Flent-users] " Toke Høiland-Jørgensen
2021-09-30 10:00 ` j-breyer
2021-09-30 10:10 ` j-breyer
2021-09-30 11:04 ` Toke Høiland-Jørgensen
2021-09-30 11:18 ` j-breyer
2021-09-30 11:23 ` Toke Høiland-Jørgensen
2021-09-30 11:40 ` j-breyer
2021-09-30 12:00 ` Toke Høiland-Jørgensen
2021-09-30 14:00 ` j-breyer
2021-09-30 14:04 ` j-breyer
2021-09-30 14:12 ` Toke Høiland-Jørgensen
2021-09-30 14:12 ` 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/240@github.com \
    --to=notifications@github.com \
    --cc=flent@noreply.github.com \
    --cc=reply+AHVNJP5U6Z7IPRTIIY6UZGV7MBVYJEVBNHHDYREZNM@reply.github.com \
    --cc=subscribed@noreply.github.com \
    --subject='Re: [Flent-users] [tohojo/flent] Questions (and Error) regarding rrul_prio (#240)' \
    /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