From: j-breyer <notifications@github.com>
To: tohojo/flent <flent@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [Flent-users] [tohojo/flent] -6 Option ignored for hosts with IPv4 and IPv6 address (#241)
Date: Thu, 30 Sep 2021 07:09:20 -0700 [thread overview]
Message-ID: <tohojo/flent/issues/241@github.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2199 bytes --]
In my current setup, I have two hosts defined in `/etc/hosts`, both capable of communicating via IPv4 and IPv6. Configuration:
`mn.h1` uses `10.0.6.1` and `a::601`
`mn.h2` uses `10.0.14.2` and `a::e02`
On `mn.h2`, netserver is listening on both addresses, and `irtt server` is started listening on all addresses.
Running `sudo flent rrul -6 -p all_scaled --local-bind mn.h1 -l 60 -H mn.h2 -o rrul6.pdf -v`
yields different results as follows:
Both hosts have their IPv4 enabled:
verbose output of flent is Error- and warning-free, however, the irtt server on mn.h2 shows:
```
[10.0.6.1:56747] [OpenClose] open-close connection
[10.0.6.1:34502] [NewConn] new connection, token=e6582ec0dc3b7161
[10.0.6.1:34942] [NewConn] new connection, token=5898db5f137d0b66
[10.0.6.1:42243] [NewConn] new connection, token=c412d2bb05eefd1d
```
Indicating that irtt is using the IPv4 despite the `-6` argument.
Removing the IPv4 resolution for `mn.h1`:
(partial) verbose output of flent:
```
which: Found irtt executable at /usr/bin/irtt
UDP RTT test: Cannot use irtt runner (Irtt connection check failed: Error: dial udp4 [a::601]:0->10.0.14.2:2112: address a::601: non-IPv4 address
). Using netperf UDP_RR
```
Removing the IPv4 from `mn.h2`, but keeping it on `mn.h1`:
(partial) verbose output of flent:
```
which: Found irtt executable at /usr/bin/irtt
UDP RTT test: Cannot use irtt runner (Irtt connection check failed: Error: dial udp6 10.0.6.1:0->[a::e02]:2112: bind: invalid argument
). Using netperf UDP_RR
```
Removing both IPv4 entries for `mn.h1` and `mn.h2`:
Flent verbose without errors, irtt server shows:
```
[[a::601]:55765] [OpenClose] open-close connection
[[a::601]:37744] [NewConn] new connection, token=df67b3a6d5892659
[[a::601]:38572] [NewConn] new connection, token=8326d482ae57f712
[[a::601]:55775] [NewConn] new connection, token=366ddbe19c620d6f
```
which is what I would expect every time, since the `-6` argument was passed.
I did not try this on too many tests, but it appears at least for `rrul` and `rrul_cs8`
--
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/241
[-- Attachment #2: Type: text/html, Size: 3764 bytes --]
next reply other threads:[~2021-09-30 14:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 14:09 j-breyer [this message]
2021-09-30 14:27 ` [Flent-users] " Toke Høiland-Jørgensen
2021-09-30 15:15 ` Pete Heist
2021-10-01 9:07 ` j-breyer
2021-10-01 12:06 ` Toke Høiland-Jørgensen
2021-10-01 12:19 ` Toke Høiland-Jørgensen
2021-10-01 13:01 ` 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=tohojo/flent/issues/241@github.com \
--to=notifications@github.com \
--cc=flent@noreply.github.com \
--cc=reply+AHVNJP46754XHFDYCOW4L6V7MGTBBEVBNHHDYVLITY@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