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

Probe not visible on the webapp #21

Closed
Albonycal opened this issue Jun 12, 2023 · 15 comments
Closed

Probe not visible on the webapp #21

Albonycal opened this issue Jun 12, 2023 · 15 comments

Comments

@Albonycal
Copy link

Error logs: https://paste.debian.net/1282752/

@jimaek
Copy link
Member

jimaek commented Jun 12, 2023

Can you try running these commands on some linux machine a few times and tell me if they fail or not?

ping -4 -c 6 -i 0.2 -w 15 k.root-servers.net
ping -4 -c 6 -i 0.2 -w 15 j.root-servers.net
ping -4 -c 6 -i 0.2 -w 15 l.root-servers.net

Additionally you can try some other root servers from here https://root-servers.org/ and tell me if some other is more stable for you

@Albonycal
Copy link
Author

image
image
image
The l root server is dropping packets

@jimaek
Copy link
Member

jimaek commented Jun 12, 2023

In your logs all of them seem to be doing it, so you need to run these commands a few times to be sure.

Also try this and let me know if it improves things or not:

ping -4 -c 6 -i 0.3 -w 15 l.root-servers.net
@Albonycal
Copy link
Author

Albonycal commented Jun 12, 2023

ping -4 -c 6 -i 0.3 -w 15 l.root-servers.net

Still dropping packets, other ones are not (tested multiple times)

@jimaek
Copy link
Member

jimaek commented Jun 12, 2023

What about this endpoint?

a.root-servers.net

@Albonycal
Copy link
Author

In your logs all of them seem to be doing it,

No they aren't, only l rootserver is dropping packets.

a root server is fine, no packetloss

@jimaek
Copy link
Member

jimaek commented Jun 12, 2023

Please send the latest logs from your probe

@jimaek
Copy link
Member

jimaek commented Jun 13, 2023

I pushed another update, check if your probe now passes the test

@Albonycal
Copy link
Author

still fails

@jimaek
Copy link
Member

jimaek commented Jun 14, 2023

So far it seems that your internet is indeed unstable. I even included an endpoint by an Indian provider.

The only other potential problem I see is the "-i 0.2 " parameter. So please run many pings over the period of an hour to the failing endpoints in your logs using different values of that parameter to compare if there is a difference. e.g. 0.2, 0.3, 0.4, 0.5

@Albonycal
Copy link
Author

I don't think my network is unstable.

@Albonycal
Copy link
Author

Oh wait, I restarted the probe and it downloaded the latest update. And the probe is up now

@Albonycal
Copy link
Author

Also, I think using geoip database for the location of the probe is not a good idea, there should be a way to hardcode the city. It's not correct.
image

@jimaek
Copy link
Member

jimaek commented Jun 14, 2023

Oh wait, I restarted the probe and it downloaded the latest update. And the probe is up now

Great!

Also, I think using geoip database for the location of the probe is not a good idea, there should be a way to hardcode the city. It's not correct.

You will get this option once our dashboard goes live. You will also get stats and other features

@jimaek jimaek closed this as completed Jun 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants