update ping node readme

(how to run in snap)
This commit is contained in:
Dave Conway-Jones 2018-12-07 16:55:16 +00:00
parent 89d7853891
commit d0f36dcda1
No known key found for this signature in database
GPG Key ID: 9E7F9C73F5168CD4
3 changed files with 8 additions and 3 deletions

View File

@ -18,7 +18,9 @@
<p>Pings a machine and returns the trip time in mS as <code>msg.payload</code>.</p>
<p>Returns <b>false</b> if no response received within 5 seconds, or if the host is unresolveable.</p>
<p>Default ping is every 20 seconds but can be configured.</p>
<p><code>msg.topic</code> contains the target host ip.
<p><code>msg.topic</code> contains the target host ip.</p>
<p>Note: if running inside Ubuntu Snap you will need to manually start the network-observe interface.
`snap connect node-red:network-observe`</p>
</script>
<script type="text/javascript">

View File

@ -11,9 +11,12 @@ Run the following command in your Node-RED user directory - typically `~/.node-r
npm install node-red-node-ping
**Gotchas**
1 This won't run on Ubunti Snap as the strict container does not allow spawning of external commands (like ping).
1 Ubuntu Snap containers are strict and do not like giving external commands (like ping) external access. To allow ping to work you must manually add the network-observe interface
sudo snap connect node-red:network-observe
2 On some versions on Raspbian (Raspberry Pi) `ping` seems to be a root only command.
The fix is to allow it as follows

View File

@ -1,6 +1,6 @@
{
"name" : "node-red-node-ping",
"version" : "0.0.16",
"version" : "0.0.17",
"description" : "A Node-RED node to ping a remote server, for use as a keep-alive check.",
"dependencies" : {
},