ping node supports only "english" os. about node-red-nodes HOT 9 CLOSED

Aha - indeed... Though TTL is not the ping time, and Linux reports them the other way round...
64 bytes from 173.194.65.106: icmp_req=1 ttl=40 time=59.8 ms
so yes more thought required...

from node-red-nodes.

Just add "i" (case-insensitive) and that should work.

from node-red-nodes.

yes - but TTL is not the ping time... in your examples the ping time is the "<1" part, not the "=128" part

from node-red-nodes.

I checked all 4 types of outputs on http://regex101.com/
And it is valid (with "i"). In my examples I check the "bytes=32" and not the time.

from node-red-nodes.

I think @dceejay means that the order of the fields changes with different languages so we can't extract the correct response time with just one regex

from node-red-nodes.

Sorry, I did not notice, that the response time was extracted. I just tried
to extract positive or negative answer.
Because for Home-Automation (where I am active) it is not important how
many milliseconds. it is important if the device ON or OFF.
Can we process that with 2 steps: first one extract Yes/No (res=true) and
the second (if Yes) the response time?

2014-11-06 13:39 GMT+01:00 Ben Hardill [email protected]:

I think @dceejay https://github.com/dceejay means that the order of the
fields changes with different languages so we can't extract the correct
response time with just one regex

—
Reply to this email directly or view it on GitHub
#80 (comment)
.

from node-red-nodes.

I think...

 
    =.*[<|=]([0-9]*).*TTL|ttl..*=([0-9]*)

may do the magic...
actually then needs to handle both m[1] and m[2] but hey...

from node-red-nodes.

Ping node now updated. @GermanBluefox can you check ? Comment ? Close ?

from node-red-nodes.

Closing as I think it's fixed. please re-open if not.

from node-red-nodes.