Closed #242 via 5527b187bd4b8c9b3f6d919891f0b97a89edf000.
--
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/242#event-5395660127___
Flent-users
j-breyer ***@***.***> writes:
> When starting the `rrul46compete` test, I noticed some weird behavior:
>
> With defined hosts `mn.h1` and `mn.h2`, each having an IPv4 as well as an
> IPv6 address, the command
> `sudo flent rrul46compete -p all_scaled -l 60 -H mn.h2 -o rrul46_nolocal.pdf
> -v`
>
When starting the `rrul46compete` test, I noticed some weird behavior:
With defined hosts `mn.h1` and `mn.h2`, each having an IPv4 as well as an IPv6
address, the command
`sudo flent rrul46compete -p all_scaled -l 60 -H mn.h2 -o rrul46_nolocal.pdf -v`
runs error free with complete graph output.
I never noticed this, actually. The standard net.Dial(), for "historical
reasons", just prefers IPv4 instead of relying on the local resolver. This
prompted a "Wow, okay" from B. Fitzpatrick.
(https://github.com/golang/go/issues/20911).
It looks like one can get around that by using the Lookup*
Closed #241 via 76c96e66f1dfb75bfa2c90f8aea414b91a911b68.
--
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#event-5394030111___
Flent-users
j-breyer ***@***.***> writes:
>>I also wonder what happens if you don't use --local-bind.
>
> irtt connection no longer fails, as there's no mismatch in address
> families. However, as long as `mn.h2` has an IPv4 defined, it uses
> IPv4 to connect, disregarding the `-6` param
Hmm, I guess maybe t
>Hmm, could you please post a full debug log (from --log-file),
Running the exact same command as posted with `--log-file` appended and
scrolling a bit through the file, I found the following lines interesting:
```
2021-10-01 08:51:02,954 [flent.runners] DEBUG: Forked /usr/bin/netperf as pid
415
