(py2_dmr) ➜ HBlink git:(master) python hblink.py
DEBUG 2018-07-09 17:45:39,910 Logging system started, anything from here on gets logged
INFO 2018-07-09 17:45:39,910 HBlink TCP reporting server configured
DEBUG 2018-07-09 17:45:39,910 Periodic reporting loop started
INFO 2018-07-09 17:45:39,910 HBlink 'HBlink.py' (c) 2016 N0MJS & the K0USY Group - SYSTEM STARTING...
DEBUG 2018-07-09 17:45:39,910 (HOTSPOT-dev) Client maintenance loop started
INFO 2018-07-09 17:45:39,911 (HOTSPOT-dev) Sending login request to master 194.146.121.130:62031
DEBUG 2018-07-09 17:45:39,911 CLIENT instance created: HOTSPOT-dev, <__main__.HBSYSTEM instance at 0x7fe2cae29ea8>
INFO 2018-07-09 17:45:39,967 (HOTSPOT-dev) Repeater Login ACK Received with 32bit ID: 497425309
INFO 2018-07-09 17:45:40,016 (HOTSPOT-dev) Repeater Authentication Accepted
INFO 2018-07-09 17:45:40,017 (HOTSPOT-dev) Repeater Configuration Sent
WARNING 2018-07-09 17:45:40,076 (HOTSPOT-dev) MSTNAK Received. Resetting connection to the Master.
DEBUG 2018-07-09 17:45:44,915 (HOTSPOT-dev) Client maintenance loop started
INFO 2018-07-09 17:45:44,916 (HOTSPOT-dev) Sending login request to master 194.146.121.130:62031
INFO 2018-07-09 17:45:45,007 (HOTSPOT-dev) Repeater Login ACK Received with 32bit ID: 1757719149
INFO 2018-07-09 17:45:45,057 (HOTSPOT-dev) Repeater Authentication Accepted
INFO 2018-07-09 17:45:45,057 (HOTSPOT-dev) Repeater Configuration Sent
WARNING 2018-07-09 17:45:45,112 (HOTSPOT-dev) MSTNAK Received. Resetting connection to the Master.
Anyone could guess what's wrong with my config file? Tried various master servers. All same behaviour
using Git master with last commit 416ab12c5ff582665c2e5af994c4bea6b024de0d
# PROGRAM-WIDE PARAMETERS GO HERE
# PATH - working path for files, leave it alone unless you NEED to change it
# PING_TIME - the interval that clients will ping the master, and re-try registraion
# - how often the Master maintenance loop runs
# MAX_MISSED - how many pings are missed before we give up and re-register
# - number of times the master maintenance loop runs before de-registering a client
[GLOBAL]
PATH: ./
PING_TIME: 5
MAX_MISSED: 3
# NOT YET WORKING: NETWORK REPORTING CONFIGURATION
# Enabling "REPORT" will configure a socket-based reporting
# system that will send the configuration and other items
# to a another process (local or remote) that may process
# the information for some useful purpose, like a web dashboard.
#
# REPORT - True to enable, False to disable
# REPORT_INTERVAL - Seconds between reports
# 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. Entering a * will allow all.
#
# ****FOR NOW MUST BE TRUE - USE THE LOOPBACK IF YOU DON'T USE THIS!!!****
[REPORTS]
REPORT: True
REPORT_INTERVAL: 60
REPORT_PORT: 4321
REPORT_CLIENTS: 127.0.0.1
# SYSTEM LOGGER CONFIGURAITON
# This allows the logger to be configured without chaning the individual
# python logger stuff. LOG_FILE should be a complete path/filename for *your*
# system -- use /dev/null for non-file handlers.
# LOG_HANDERLS may be any of the following, please, no spaces in the
# list if you use several:
# null
# console
# console-timed
# file
# file-timed
# syslog
# LOG_LEVEL may be any of the standard syslog logging levels, though
# as of now, DEBUG, INFO, WARNING and CRITICAL are the only ones
# used.
#
[LOGGER]
LOG_FILE: /tmp/hblink.log
LOG_HANDLERS: console-timed
LOG_LEVEL: DEBUG
LOG_NAME: HBlink
# DOWNLOAD AND IMPORT SUBSCRIBER, PEER and TGID ALIASES
# Ok, not the TGID, there's no master list I know of to download
# This is intended as a facility for other applcations built on top of
# HBlink to use, and will NOT be used in HBlink directly.
# STALE_DAYS is the number of days since the last download before we
# download again. Don't be an ass and change this to less than a few days.
[ALIASES]
TRY_DOWNLOAD: True
PATH: ./
PEER_FILE: peer_ids.csv
SUBSCRIBER_FILE: subscriber_ids.csv
TGID_FILE: talkgroup_ids.csv
PEER_URL: http://dmr-marc.net/static/rptrs.csv
SUBSCRIBER_URL: http://dmr-marc.net/static/users.csv
STALE_DAYS: 7
# EXPORT AMBE DATA
# This is for exporting AMBE audio frames to an an "external" process for
# decoding or other nefarious actions.
[AMBE]
EXPORT_IP: 127.0.0.1
EXPORT_PORT: 1234
# MASTER INSTANCES - DUPLICATE SECTION FOR MULTIPLE MASTERS
# HomeBrew Protocol Master instances go here.
# IP may be left blank if there's one interface on your system.
# Port should be the port you want this master to listen on. It must be unique
# and unused by anything else.
# Repeat - if True, the master repeats traffic to clients, False, it does nothing.
[MASTER-1]
MODE: MASTER
ENABLED: False
REPEAT: True
EXPORT_AMBE: False
IP:
PORT: 54000
PASSPHRASE: s3cr37w0rd
GROUP_HANGTIME: 5
# CLIENT INSTANCES - DUPLICATE SECTION FOR MULTIPLE CLIENTS
# There are a LOT of errors in the HB Protocol specifications on this one!
# MOST of these items are just strings and will be properly dealt with by the program
# The TX & RX Frequencies are 9-digit numbers, and are the frequency in Hz.
# Latitude is an 8-digit unsigned floating point number.
# Longitude is a 9-digit signed floating point number.
# Height is in meters
# Setting Loose to True relaxes the validation on packets received from the master.
# This will allow HBlink to connect to a non-compliant system such as XLXD, DMR+ etc.
[HOTSPOT-dev]
MODE: CLIENT
ENABLED: True
LOOSE: True
EXPORT_AMBE: False
IP:
PORT: 54001
MASTER_IP: master.ham-dmr.be
MASTER_PORT: 62031
PASSPHRASE: passw0rd
CALLSIGN: <<<<used my callsign here, 7-digits>>>>>>
RADIO_ID: <<<<used my DMR ID here, 7-digits>>>>>>
RX_FREQ: 435400000
TX_FREQ: 435400000
TX_POWER: 1
COLORCODE: 1
SLOTS: 2
LATITUDE: 46.9854
LONGITUDE: 7.4703
HEIGHT: 101
LOCATION: Anywhere, CH
DESCRIPTION: My Callsign here
URL: http://www.hb9fxq.ch
SOFTWARE_ID: 20170620
PACKAGE_ID: MMDVM_HBlink
GROUP_HANGTIME: 5
OPTIONS:
Best 73
HB9FXQ, Frank
