crusader: Crash with ipv6
oot@lqos:~# crusader test --stream-stagger 5 --streams 2 --load-duration 10 fd77::2
Connected to server [fd77::2]:35481
thread ‘main’ panicked at ‘called Result::unwrap() on an Err value: “Unable to measure latency to server”’, crusader-lib/src/test.rs:1304:10
stack backtrace:
0: 0x7fdf8f501ddd - <unknown>
1: 0x7fdf8f53bc0c - <unknown>
2: 0x7fdf8f4fc771 - <unknown>
3: 0x7fdf8f503335 - <unknown>
4: 0x7fdf8f503056 - <unknown>
5: 0x7fdf8f5038c6 - <unknown>
6: 0x7fdf8f5037b7 - <unknown>
7: 0x7fdf8f502294 - <unknown>
8: 0x7fdf8f5034e9 - <unknown>
9: 0x7fdf8f388103 - <unknown>
10: 0x7fdf8f3881f3 - <unknown>
11: 0x7fdf8f3e6c8a - <unknown>
12: 0x7fdf8f38e850 - <unknown>
13: 0x7fdf8f392c63 - <unknown>
Aborted (core dumped)
About this issue
- Original URL
- State: open
- Created 4 years ago
- Comments: 56 (12 by maintainers)
I just clarified the README in this PR for 0.3 documentation https://github.com/Zoxc/crusader/pull/79/commits/a1e38cc8a8fe1dc61a57c50e754ab72a2dd1e602
Yes - the throughput measurements use TCP
Hi Rich, Thanks for clearing this up! (One reason less though to take a packet capture from a crusader run though…)
I just enabled ECN on Singapore.
sysctl -w net.ipv4.tcp_ecn=1
on your machine and w/cake try crusader. All the latency spikes should vanish.
It makes me grumpy to see 8ms of latency at 4gbit. can you slap
on your Linux box and try again?
and it was an incorrect DNS record, my bad! 2600:3c15::f03c:95ff:fe7e:75a2 it is now! try again in 15 minutes or so
I filled a bug with linode
this is what my starlink looks like to Singapore:
crusader test --load-duration 60 --streams 8 --stream-stagger 4 singapore.starlink.taht.net
that is really miserable latency.
But it is probably coming from somewhere upstream of you. A simultaneous mtr would show where.
I also, on your behalf, just put up a 4Gbps capable server at singapore.starlink.taht.net
@richb-hanover @mcuee if ever you feel inspired I still maintain 6 linode servers for these sort of tests. I would love to update them to 12 and hand off further maintenance off to someone…
@mcuee - No, I don’t have an internet test setup yet. I’m looking at how to dockerize the server for minimal hassle (then I have to dragoon one of my VPS servers into running it…)
@dtaht @mcuee - If you get a chance, do try out version 0.0.12 - the master branch. It definitely got rid of the IPv6 crash for me (as well as another amusing bug (#22) if a device advertised two IPv6 addresses…)
@mcuee I am sorry but I was not paying attention to github since march…
Yeah I meant Wireshark =P
If you feel like investigating you could try to run Wireguard and see which directions send or receives UDP traffic.
Two thoughts:
I can’t easily test over IPv6 across the public internet. My ISP doesn’t provide native IPv6, and I don’t have an IPV6 tunnel set up right now. I won’t have time to set that up soon, but if I get that going, I’ll report back.
I see the log shows “Connected to server…” then the “Main thread panicked…” message. Has anyone looked at the code to see if you can winkle out what exactly is happening? Thanks.
I re-ran my experiment at https://github.com/Zoxc/crusader/issues/9#issuecomment-1890951312 ensuring that both server and client were the current commit - a89abd26a. It ran successfully without an error/crash. I think this issue can be closed.