Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The latency setting is not accurate in clumsy. #134

Open
StephensCheng opened this issue Jun 30, 2023 · 2 comments
Open

The latency setting is not accurate in clumsy. #134

StephensCheng opened this issue Jun 30, 2023 · 2 comments

Comments

@StephensCheng
Copy link

I use the WANem to set the network latency, and use ping command to monitor the RTT value. (I only set the latency is 10ms).
The RTT value is about 20ms;
WANem

At the same time, I use the clumsy to set the network latency, use the ping command to monitor the RTT value.(only set the latency is 10ms)
The RTT value fluctuates in a large range;
clumsy

The background network condition is great, basic RTT is 2ms -5ms.
Basic

@AloisKraus
Copy link

AloisKraus commented Aug 1, 2023

I also see the same behavior. When I enable Latency with a 0 ms delay I find in Wireshark already a 20ms up to 75ms latency added by clumsy. That latency also fluctuates quite a bit.

Latency enabled
image

image

Latency disabled
image

image

@tourist1584970446
Copy link

tourist1584970446 commented Aug 29, 2023

getting same results, even completely local! Up to +80ms
turned on [x] Lag with 0ms outbound

Reply from 127.0.0.1: bytes=32 time=54ms TTL=128
Reply from 127.0.0.1: bytes=32 time=34ms TTL=128
Reply from 127.0.0.1: bytes=32 time=15ms TTL=128
Reply from 127.0.0.1: bytes=32 time=79ms TTL=128
Reply from 127.0.0.1: bytes=32 time=28ms TTL=128
Reply from 127.0.0.1: bytes=32 time=81ms TTL=128
Reply from 127.0.0.1: bytes=32 time=22ms TTL=128
Reply from 127.0.0.1: bytes=32 time=19ms TTL=128
Reply from 127.0.0.1: bytes=32 time=12ms TTL=128
Reply from 127.0.0.1: bytes=32 time=61ms TTL=128
Reply from 127.0.0.1: bytes=32 time=21ms TTL=128
Reply from 127.0.0.1: bytes=32 time=8ms TTL=128
Reply from 127.0.0.1: bytes=32 time=50ms TTL=128
Reply from 127.0.0.1: bytes=32 time=59ms TTL=128
Reply from 127.0.0.1: bytes=32 time=11ms TTL=128
Reply from 127.0.0.1: bytes=32 time=59ms TTL=128
Reply from 127.0.0.1: bytes=32 time=73ms TTL=128
Reply from 127.0.0.1: bytes=32 time=55ms TTL=128

turned off [ ] Lag

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

it behaves the same for ipv6 btw

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants