From 65df5a2ab761dacea6c5f7c17a8b01862cb3bea2 Mon Sep 17 00:00:00 2001 From: Cort Buffington Date: Mon, 1 May 2017 16:44:28 -0500 Subject: [PATCH] update sample for network reporting --- dmrlink_SAMPLE.cfg | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/dmrlink_SAMPLE.cfg b/dmrlink_SAMPLE.cfg index e9072b3..f6f2368 100644 --- a/dmrlink_SAMPLE.cfg +++ b/dmrlink_SAMPLE.cfg @@ -19,24 +19,34 @@ PATH: /opt/dmrlink/ # specifiec by "REPORT_INTERVAL" in seconds. Possible values # for "REPORT_NETWORKS" are: # PICKLE - a Python pickle file of the network's data structure -# (JSON DOES NOT WORK RNIGHT NOW) JSON - a JSON file of the network's data structure -# (REDIS DOES NOT WORK RIGHT NOW) REDIS - send JSON format data structure to a local|remote -# redis server +# # PRINT - a pretty print (STDOUT) of the data structure # "PRINT_PEERS_INC_MODE" - Boolean to include mode bits # "PRINT_PEERS_INC_FLAGS" - Boolean to include flag bits # +# NETWORK - This is the right way to do it. Opens a TCP socket +# listener. The protocol is still in its infancy, but the +# idea is that dmrlink will talk to another application +# to send event and status updates. Of course, the big +# goal here is a web dashboard that doesn't live on the +# dmrlink machine itself. +# # PRINT is the odd man out because it sends prettily formatted stuff # to STDOUT. The others send the internal data structure of the IPSC # instance and let some program on the other end sort it out. # # REPORT_INTERVAL - Seconds between reports # REPORT_PATH - Absolute path save data (pickle and json) +# REPORT_PORT - TCP port to listen on if "REPORT_NETWORKS" = NETWORK +# REPORT_CLIENTS - comma separated list of IPs you will allow clients +# to connect on. # [REPORTS] REPORT_NETWORKS: REPORT_INTERVAL: 60 REPORT_PATH: +REPORT_PORT: 4321 +REPORT_CLIENTS: 127.0.0.1, 164.113.199.2 PRINT_PEERS_INC_MODE: 0 PRINT_PEERS_INC_FLAGS: 0