Darlan Ullmann

Hi Sal, Sorry for taking that long to get back to you, I was out of the office for the last few days. I've tested the new version yesterday for about 4 hours non stop, and I got no problems with it. I believe that the issue is solved, as the library would throw an exception in a few seconds after running, on the last version. Thank you very much. Best regards, Darlan.

Thank you Sal. I'm gonna test it and I get back to you in a couple days. Darlan

Here's the output: darlan@darlan-pc ~> ping -c 1 -s 56 -w 1 192.168.32.9 PING 192.168.32.9 (192.168.32.9) 56(84) bytes of data. From 177.84.139.27 icmp_seq=1 Destination Host Unreachable --- 192.168.32.9 ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms I just changed the end of the IP address cause 192.168.32.16 is replying now in my network, but, for this tests, it's the same behaviour. I've recorded the pings and posted it on youtube, if you want to check...

Hello Sal, Here's the output: darlan@darlan-pc ~> ping -c 1 -s 56 -w 5 www.google.com PING www.google.com (172.217.30.36) 56(84) bytes of data. 64 bytes from gru10s10-in-f4.1e100.net (172.217.30.36): icmp_seq=1 ttl=121 time=17.2 ms --- www.google.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 17.298/17.298/17.298/0.000 ms I forgot to mention in my last reply that the problem only occurs on timeouts, it works without any problem when the...

Hello, I know this is an old thread, but I had this problem in the last few days, and managed to track it down. I'm running Linux Mint 19.3, and LinuxProcessNativeBridge. Sometimes - can't figure out why (maybe multiple requests to the same network, with one of them failing, don't have time to test now) - the ping process takes less time than the timeout to end, and the LinuxProcessNativeBridge.executePingRequest(request) doesn't mark it as a timeout, throwing the exception. I've attached the changes...

Hey guys, So, build 1019 and so on is requires libc-2.14 to run the JNI, but Debian...