Edex-ui: ping test fails on non-english Windows 10

[rinku98]

I installed the exe for windows and selected my Wi-Fi interface, the globe and the traffic shows offline, it can't ping 1.1.1.1 or any other, I can successfully ping to 1.1.1.1 on my cmd.

[GitSquared]

This sounds like a firewall-related issue. Could you please check that you're not blocking eDEX from accessing the network?

[rinku98]

I checked the firewall and eDex has access to private and public networks, maybe I'm missing something?

[GitSquared]

Are you sure that you selected the right interface?

[rinku98]

Yes, I selected the Wi-Fi interface.

[GitSquared]

I'm not really sure what's wrong. Could you send a screenshot of the available network interfaces in the Settings window? What shell are you using inside edex?

[rinku98]

I'm using the windows' subsystem (ubuntu) but i have the same issue using powershell.

[GioF]

Same here, but i've tried it on both my Windows 10 pc through ethernet and a Debian live usb on a notebook's WLAN, and none worked.

Could it be related to the router blocking something?

[rinku98]

I have this problem only on Windows, I installed it on Manjaro and work everything.

[RangerCD]

Same problem even if I change "pingAddr" to someone in my local network. But it does recognize my public IP address.

[RangerCD]

Just realized that inetLatency which is used here
https://github.com/GitSquared/edex-ui/blob/6b063257dc1b9442ac37f0a2163547d4ce4071ee/src/classes/netstat.class.js#L117
only supports English version of ping by parsing stdout of ping(check here).
So it might fail if your system language is not English.
It works by changing system language into en-US, but that's not a good solution at all.

[GitSquared]

@RangerCD Thanks for finding the problem. I'll report the problem to systeminformation... I'm also kind of looking for a way to replace inetLatency with something on top of Node.js sockets that could also respect the network interface choice. More on that if I can make a working prototype.

[GitSquared]

@rinku98 Could you give me the output of running ping in a regular cmd/powershell window on your system?

[RangerCD]

A quick fix is to parse by "ms" rather than "min" in inetLatency, but not pretty sure whether it works on any other language.
And maybe net-ping is what you are looking for. Hope it would help.😃

[rinku98]

@GitSquared Sure, the first is ping on my cmd and the second on the windows subsystem.

[GitSquared]

Thank you @rinku98 and @RangerCD, issue was reported upstream - and I'm going to look into net-ping next.

[RangerCD]

systeminformation v4.0.8 has been released, which fixed remaining Chinese problem related to this issue. Could you please upgrade the dependency? Thank you.

[GitSquared]

@RangerCD Will do in a few hours.

Edit in case I come back to this issue again: dropped the idea of replacing systeminformation by net-ping because np requires elevated privileges