I like to say that hblink.py itself is mostly just a protocol stack – like an IP stack. It does very little on it’s own – other applications like HB_Bridge and hb_confbridge are build on top of that stack.
On May 29, 2018, at 2:50 PM, Steve N4IRS <szingman@...
The trick is to not think of it as hblink. Though hblink provides
the connectivity to the CLIENTS and MASTERS and the config file is
called hblink.cfg, forget hblink.py exists. We are discussing
hb_confbridge and HB_Bridge.
hb_confbridge will face your MMDVM CLIENTS and HB_Bridge will face
it's Partner, IPSC_Bridge. Your hb_confbridge would be 3 masters and
client. The rules, hb_confbridge_rules would control the traffic
On 5/29/2018 3:44 PM, James - K4JK
Aha. So I in
essence would have the "outside facing" HBLink instance running
with three masters and a client. (For the MMDVM Devices)
Then I would have a "inside" HBLink instance running that has one
master. (It allows the client mentioned above to connect to it.)
These are called by hb_confbridge, and HB_Bridge, respectively.
Am I on the right track?