Destination host unreachable - not working

[GermanBluefox]

My english windows returns following if destination not reachable:
'''
C:>ping 192.168.1.72

Pinging 192.168.1.72 with 32 bytes of data:
Reply from 192.168.1.69: Destination host unreachable.
Reply from 192.168.1.69: Destination host unreachable.
Reply from 192.168.1.69: Destination host unreachable.
Reply from 192.168.1.69: Destination host unreachable.

Ping statistics for 192.168.1.72:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
'''
And
lines[t].indexOf ('(0%')>0
returns true on the "Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),"

[mondwan]

Hi,

Do window prints summary about the round-trip-time for either or both of success or failure cases? If so, please paste them here.

[GermanBluefox]

D:>ping 140.80.159.35

Pinging 140.80.159.35 with 32 bytes of data:
Reply from 140.80.159.35: bytes=32 time<1ms TTL=128
Reply from 140.80.159.35: bytes=32 time<1ms TTL=128
Reply from 140.80.159.35: bytes=32 time<1ms TTL=128
Reply from 140.80.159.35: bytes=32 time<1ms TTL=128

Ping statistics for 140.80.159.35:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

[mondwan]

It should return false for unreachable host after this patch :D

[danielzzz]

thanks a lot!

[GermanBluefox]

it is wrong solution.

_Russian output windows_:
Ответ от 80.91.249.69: число байт=32 время=447мс TTL=240
Ответ от 80.91.249.69: число байт=32 время=411мс TTL=240
Ответ от 80.91.249.69: число байт=32 время=422мс TTL=240
Ответ от 80.91.249.69: число байт=32 время=414мс TTL=240

Статистика Ping для 80.91.249.69:
Пакетов: отправлено = 250, получено = 214, потеряно = 36 (14% потерь)
Приблизительное время приема-передачи в мс:
Минимальное = 182мсек, Максимальное = 547 мсек, Среднее = 292 мсек

_German_
Ping wird ausgeführt für 140.80.159.35 mit 32 Bytes Daten:
Antwort von 140.80.159.35: Bytes=32 Zeit<1ms TTL=128
Antwort von 140.80.159.35: Bytes=32 Zeit<1ms TTL=128
Antwort von 140.80.159.35: Bytes=32 Zeit<1ms TTL=128
Antwort von 140.80.159.35: Bytes=32 Zeit<1ms TTL=128

Ping-Statistik für 140.80.159.35:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 0ms, Maximum = 0ms, Mittelwert = 0ms

_English_:
Pinging 140.80.159.35 with 32 bytes of data:

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

Ping statistics for 140.80.159.35:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Chinese:???

We discussed just on other ping project the windows outputs:
node-red/node-red-nodes#80 (comment)

The solution with

works good even for linux.

[mondwan]

Oops. I will write another patch for that issue. Thanks for the explanation.

[mondwan]

I call search() instead of match() since we don't care the TTL contents atm.

Let me know whether this patch works or not.

[mondwan]

Please fire another ticket if there are any new problems. close #17