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

Issue for ethr latency test of AWS EC2 in two different regions #173

Open
terrificdm opened this issue May 19, 2022 · 0 comments
Open

Issue for ethr latency test of AWS EC2 in two different regions #173

terrificdm opened this issue May 19, 2022 · 0 comments

Comments

@terrificdm
Copy link

If you set up two EC2 in tow AWS regions, and test latency between them, there is no any result comes out. Even though the connection is valid, but sees all of packages are dropped by some reason.
For instance: one EC2 in us-east-1, and the other in ap-southeast-1, you run command like below:

for server EC2:
./ethr -s --port 5023.
for client EC2:
./ethr -c xxxx.xxxx.xxxx.xxxx -n 16 --port 5023 -p tcp -t l

And you got nothing related to valid result, but the connection is ok.
Screen Shot 2022-05-19 at 19 25 23

If you put two EC2 in the same region, and do the same test, and you will get the expected result..
Screen Shot 2022-05-19 at 19 27 17

I noticed that AWS has a MTU 1500 bytes restriction for traffic over an internet gateway, so my question is does ethr latency test will send a package over the 1500 bytes size? And how can I solve this issue

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

1 participant