This is the home forum for HBLink, a set of tools written in Python that allow the creation of private or area DMR networks ("lower case n"), along with ways to connect to the various national/international DMR Networks ("capital N") to access their talk groups and services. It is also useful for bridging between IPSC (Motorola) and HBP (homebrew repeaters) DMR networks.
The current version of the tool set is written in Python 3. Previously released versions of the bridges (IPSC_Bridge and HB_Bridge) are written in Python 2 and are battle-tested for interconnecting between those two DMR repeater types.
Elsewhere on the wiki, you can find Frequently Asked Questions that can hopefully prevent you from asking the same question that has been answered countless times before. Please have a look (and search) there before posing a question about your configuration.
Provide log files (no screenshots) and redact whatever you deem to be personally-identifiable-information (PII). You are responsible for not disclosing sensitive information on this forum.
|
Re: Full proof HB installation HOWTO?
Patrick Vichot <patrick.vichot@...>
Yes I know but it's not necessary translate. It's easy to understand because the most important are Linux commands. You can copy and past commands lines (from pdf to ssh terminal) to build a basic server. After, for configuration, help in Englisnh is include in configurations files. :) Ps: you can see step by step video tutorial here: Or youtube Patrick F1FQN
Le mer. 11 nov. 2020 à 23:14, Aaron Groover <k3alg@...> a écrit :
|
|
|
|
Re: Full proof HB installation HOWTO?
Demetre - M0SUY/SV1UY <demetre.sv1uy@...>
Hi Doug,
Have you still got this Rpi image please? I found an old post of yours but the link does not exist anymore! 73 de Demetre M0SUY
|
|
|
|
Re: Full proof HB installation HOWTO?
Aaron Groover
From: HBlink@DVSwitch.groups.io <HBlink@DVSwitch.groups.io> on behalf of Demetre - M0SUY/SV1UY <demetre.sv1uy@...>
Sent: Wednesday, November 11, 2020 5:13:47 PM To: HBlink@DVSwitch.groups.io <HBlink@DVSwitch.groups.io> Subject: Re: [HBlink] Full proof HB installation HOWTO? Thank you very much Doug and Patrick
Although my French is really poor, they are French I learnt at school when I were I kid, I will give it a try. Merci beaucoup Patrick 73 de Demetre M0SUY
|
|
|
|
Re: Full proof HB installation HOWTO?
Demetre - M0SUY/SV1UY <demetre.sv1uy@...>
Thank you very much Doug and Patrick
Although my French is really poor, they are French I learnt at school when I were I kid, I will give it a try. Merci beaucoup Patrick 73 de Demetre M0SUY
|
|
|
|
Re: Full proof HB installation HOWTO?
Aaron Groover
From: HBlink@DVSwitch.groups.io <HBlink@DVSwitch.groups.io> on behalf of Patrick Vichot <patrick.vichot@...>
Sent: Wednesday, November 11, 2020 4:36:29 PM To: HBlink@dvswitch.groups.io <HBlink@dvswitch.groups.io> Subject: Re: [HBlink] Full proof HB installation HOWTO? Here you are !
73's
F1FQN
Le mer. 11 nov. 2020 à 20:36, Demetre - M0SUY/SV1UY <demetre.sv1uy@...> a écrit :
Hi,
|
|
|
|
Re: Full proof HB installation HOWTO?
Patrick Vichot <patrick.vichot@...>
Here you are ! 73's F1FQN
Le mer. 11 nov. 2020 à 20:36, Demetre - M0SUY/SV1UY <demetre.sv1uy@...> a écrit : Hi,
|
|
|
|
Re: Full proof HB installation HOWTO?
Login as a sudo user. apt-get install git wget https://bootstrap.pypa.io/get-pip.py python3 get-pip.py apt-get install python3-twisted pip install dmr-utils3 git clone https://github.com/HBLink-org/hblink3.git apt-get update apt-get upgrade That is going off memory but try and see.. If you are missing something it will tell you. 73, Doug W4DBG
On Wed, Nov 11, 2020 at 1:36 PM Demetre - M0SUY/SV1UY <demetre.sv1uy@...> wrote: Hi,
|
|
|
|
Full proof HB installation HOWTO?
Demetre - M0SUY/SV1UY <demetre.sv1uy@...>
Hi,
Is there a full proof installation HOWTO for HBlink3 that I would like to install in a Rasberry Pi 3B+ please? I am no LINUX expert but I am OK with Linux commands, well sort of, hi hi hi! 73 de Demetre M0SUY
|
|
|
|
About the project https://github.com/OK-DMR/Hytera_Homebrew_Bridge
EA5GVK Joaquin
Good morning.
Someone knows how smarek is handling his big project About the project https://github.com/OK-DMR/Hytera_Homebrew_Bridge This will give the freedom to communicate hytera repeaters with servers like HBLink. Greetings and much encouragement smarek
|
|
|
|
Re: Problem with DMRlink and Hblink3
#support
DO1KBL, Kim
Today I try to analyze it.
but I see this in my HB_Bridge.py: INFO 2020-11-07 13:21:59,140 Voice Transmission Start on TS 2 and TG 9 (9) from 2623266 (2623266) INFO 2020-11-07 13:21:59,142 (Mototrbo) Seq number not found. got 3 expected 1 INFO 2020-11-07 13:21:59,147 (Mototrbo) Seq number not found. got 2 expected 1 INFO 2020-11-07 13:21:59,149 (Mototrbo) Seq number not found. got 7 expected 3 INFO 2020-11-07 13:21:59,152 (Mototrbo) Seq number not found. got 6 expected 8 INFO 2020-11-07 13:21:59,155 (Mototrbo) Seq number not found. got 5 expected 7 INFO 2020-11-07 13:21:59,157 Voice Transmission End 0.02 seconds loss rate: 62.50% (3/8) INFO 2020-11-07 13:21:59,833 Voice Transmission Start on TS 2 and TG 9 (9) from 2623266 (2623266) INFO 2020-11-07 13:21:59,837 (Mototrbo) Seq number not found. got 2 expected 1 INFO 2020-11-07 13:23:01,160 Voice Transmission End 61.33 seconds loss rate: 0.10% (1027/1028) How can I solve the problem with the Sequenz numbers? why the expected is not 1,2,3,4,5,6 I dont know now how i can solve it. Any Ideas
|
|
|
|
Problem with DMRlink and Hblink3
#support
Hello guys,
I have a small question why the first 3 seconds and on longer duration the Audio are not ok from HBlink --> Motorola SLR5500 My Hardware looks like this: Motorola SLR5500 <--->IPSC_Bridge (Version:20170620)<--->HB_Bridge<--->HBLink3<---> 2x MMDVM_Hotspots ^ Hytera RD625 <---> HytGW <---> DMRGateway----------------| The IPSC_Bridge is the Master and the SLR5500 the Slave. Connection is OK but the NF ist not working on the beginning (3-4 seconds) and on longer Duration is the Audio not ok and the Radio Lost and find the Audio. I press PTT on a hotspot and the repeater goes to TX I see very short my Callsign, then channel screen about 2-3 seconds again my callsign and then all is ok. And on longer Duration I have the Problem. Only in the Direction from from HBLink---->IPSC_Bridge Other Direction I have no problem for now. ******Infos******* MMDVM: 2020615_Pi-Star_v4 Hytera: Firmware 8.5 Hyt_GW: V1.7 Motorola: R02.10.00.11 IPSC_Bridge: Version 20170620 HB_Bridge: Version 20170620 ******UPDATES******* I create a Parrot Master and die Echo From Motorola SLR5500 is clear in bot directions. RX from Motorola is clear on all MMDVM Hotspots and Hytera Repeater RX from MMDVM is Clear on Hytera but the Problems on the Motorola TX RX from Hytera is Clear on MMDVM but the problem on the Motorola TX. RX from USRP-->AnalogBridge--->MMDVMBridge is on all Device clear. Maybe someone has an Idea how I can solve the Problem, with this "error" the Motorola Repeater is not Usable. *******Log from IPSC******** ERROR 2020-11-06 06:30:34,822 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000 ERROR 2020-11-06 06:30:49,831 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000 But I thing this is not the Problem. Maybe some parameter in my configuration is wrong, but I dont unterstand why the analogbridge ans parrot is working but not from other hotspots / repeater. Thank you 73 Do1KBL, Kim
|
|
|
|
[hblink3:master] reported: HBlink crash (memory leak)?
#github
HBlink@DVSwitch.groups.io Integration <HBlink@...>
[hblink3:master] New Comment on Issue #5 HBlink crash (memory leak)?
Another crash this afternoon. I have rolled back hblink3 to commit 08f6669bd315f8abb9bd80b5faad4cd43439c2f4 which is where I had it for some months and it was completely stable. Will monitor to see if this makes any difference.
|
|
|
|
Re: [hblink3:master] new issue: HBlink crash (memory leak)?
#github
Roby IV3JDV
|
|
|
|
[hblink3:master] new issue: HBlink crash (memory leak)?
#github
HBlink@DVSwitch.groups.io Integration <HBlink@...>
[hblink3:master] New Issue Created by K2IE:
2nd time in one week. ERROR 2020-11-02 09:49:48,212 (GLOBAL) STOPPING REACTOR TO AVOID MEMORY LEAK: Unhandled error in timed loop. [Failure instance: Traceback: : 'LAST' /usr/local/lib/python3.7/dist-packages/twisted/internet/base.py:1283:run /usr/local/lib/python3.7/dist-packages/twisted/internet/base.py:1292:mainLoop /usr/local/lib/python3.7/dist-packages/twisted/internet/base.py:913:runUntilCurrent /usr/local/lib/python3.7/dist-packages/twisted/internet/task.py:239:call --- --- /usr/local/lib/python3.7/dist-packages/twisted/internet/defer.py:151:maybeDeferred /opt/hblink3/bridge.py:203:stream_trimmer_loop ] INFO 2020-11-02 09:49:48,219 (REPORT) HBlink reporting client disconnected: IPv4Address(type='TCP', host='127.0.0.1', port=51548)
|
|
|
|
Re: The Future of HBLink3
#hblink
JJ Cummings
I’ll ping you off list - happy to add to the dev efforts.
toggle quoted messageShow quoted text
Sent from the iRoad
On Oct 21, 2020, at 12:37, Dan K2IE via groups.io <dan@...> wrote:
|
|
|
|
[hblink3:master] reported: HBlink incorrecly sees data as new group call from XLX when none sent
#github
HBlink@DVSwitch.groups.io Integration <HBlink@...>
[hblink3:master] New Comment on Issue #4 HBlink incorrecly sees data as new group call from XLX when none sent
It looks like it is problem XLXD
|
|
|
|
Updates to Github
#github
HBlink@DVSwitch.groups.io Integration <HBlink@...>
[hblink3:master] New Issue Created by K2IE:
As discussed on the groups.io mailing list and sumitted with some additional data. At the end of any transmission to a bridge group in which an XLXPEER participates, HBlink thinks the XLX is sending a brief new group call in response to the end of the original stream. I am fairly certain (through packet capture) that there are no out of sequence packets being sent back from the XLX. HBlink is somehow confused by what it thinks it sees. This results in artifacts of a new transmission in the log when none was went. It gets in the way of private calls working properly, as calls get forwarded to the XLX (where the desired recpient is not). Configs and other data follow: Log evidence: INFO 2020-10-27 09:40:24,091 (HOTSPOTS) GROUP CALL START STREAM ID: 3158937644 SUB: K2IE (3134090) PEER: 313409002 (313409002) TGID 2 (2), TS 2 INFO 2020-10-27 09:40:24,095 (HOTSPOTS) Conference Bridge: TEST BRIDGE, Call Bridged to HBP System: XLX020E TS: 2, TGID: 2 INFO 2020-10-27 09:40:29,990 (HOTSPOTS) GROUP CALL END STREAM ID: 3158937644 SUB: K2IE (3134090) PEER: 313409002 (313409002) TGID 2 (2), TS 2, Duration: 5.90 INFO 2020-10-27 09:40:30,021 (XLX020E) GROUP CALL START STREAM ID: 3158900736 SUB: K2IE (3134090) PEER: 3163081 (3163081) TGID 9 (9), TS 2 Config: [HOTSPOTS] MODE: MASTER ENABLED: True REPEAT: True MAX_PEERS: 10 EXPORT_AMBE: False IP: PORT: 54100 PASSPHRASE: passw0rd GROUP_HANGTIME: 5 USE_ACL: True REG_ACL: DENY:1 SUB_ACL: DENY:1 TGID_TS1_ACL: PERMIT:ALL TGID_TS2_ACL: PERMIT:ALL Can use to test against for this issue[XLX020E] MODE: XLXPEER ENABLED: True LOOSE: True EXPORT_AMBE: False IP: PORT: 54002 MASTER_IP: 66.175.215.217 MASTER_PORT: 62030 PASSPHRASE: passw0rd CALLSIGN: YOUR_VALID_CALL RADIO_ID: YOUR_VALID_RID RX_FREQ: 449000000 TX_FREQ: 444000000 TX_POWER: 25 COLORCODE: 1 SLOTS: 1 LATITUDE: 38.0000 LONGITUDE: -095.0000 HEIGHT: 75 LOCATION: Anywhere, USA DESCRIPTION: Test config URL: www.w1abc.org SOFTWARE_ID: 20170620 PACKAGE_ID: MMDVM_HBlink GROUP_HANGTIME: 5 XLXMODULE: 4005 USE_ACL: True SUB_ACL: DENY:1 TGID_TS1_ACL: PERMIT:ALL TGID_TS2_ACL: PERMIT:ALL Rules: BRIDGES = { 'TEST BRIDGE': [ {'SYSTEM': 'HOTSPOTS', 'TS': 2, 'TGID': 2, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': [], 'RESET': []}, xlxd.zip {'SYSTEM': 'XLX020E', 'TS': 2, 'TGID': 2, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': [], 'RESET': []}, ] } UNIT = ['HOTSPOTS', 'XLX020E'] Wireshark capture done on the XLX attached so show how the sequence numbers are being properly incremented from the XLX end. See xlxd.zip.
[hblink3:master] New Issue Created by K2IE:
As discussed on the groups.io mailing list and sumitted with some additional data. At the end of any transmission to a bridge group in which an XLXPEER participates, HBlink thinks the XLX is sending a brief new group call in response to the end of the original stream. I am fairly certain (through packet capture) that there are no out of sequence packets being sent back from the XLX. HBlink is somehow confused by what it thinks it sees. This results in artifacts of a new transmission in the log when none was went. It gets in the way of private calls working properly, as calls get forwarded to the XLX (where the desired recpient is not). Configs and other data follow: Log evidence: INFO 2020-10-27 09:40:24,091 (HOTSPOTS) GROUP CALL START STREAM ID: 3158937644 SUB: K2IE (3134090) PEER: 313409002 (313409002) TGID 2 (2), TS 2 INFO 2020-10-27 09:40:24,095 (HOTSPOTS) Conference Bridge: TEST BRIDGE, Call Bridged to HBP System: XLX020E TS: 2, TGID: 2 INFO 2020-10-27 09:40:29,990 (HOTSPOTS) GROUP CALL END STREAM ID: 3158937644 SUB: K2IE (3134090) PEER: 313409002 (313409002) TGID 2 (2), TS 2, Duration: 5.90 INFO 2020-10-27 09:40:30,021 (XLX020E) GROUP CALL START STREAM ID: 3158900736 SUB: K2IE (3134090) PEER: 3163081 (3163081) TGID 9 (9), TS 2 Config: [HOTSPOTS] MODE: MASTER ENABLED: True REPEAT: True MAX_PEERS: 10 EXPORT_AMBE: False IP: PORT: 54100 PASSPHRASE: passw0rd GROUP_HANGTIME: 5 USE_ACL: True REG_ACL: DENY:1 SUB_ACL: DENY:1 TGID_TS1_ACL: PERMIT:ALL TGID_TS2_ACL: PERMIT:ALL Can use to test against for this issue[XLX020E] MODE: XLXPEER ENABLED: True LOOSE: True EXPORT_AMBE: False IP: PORT: 54002 MASTER_IP: 66.175.215.217 MASTER_PORT: 62030 PASSPHRASE: passw0rd CALLSIGN: YOUR_VALID_CALL RADIO_ID: YOUR_VALID_RID RX_FREQ: 449000000 TX_FREQ: 444000000 TX_POWER: 25 COLORCODE: 1 SLOTS: 1 LATITUDE: 38.0000 LONGITUDE: -095.0000 HEIGHT: 75 LOCATION: Anywhere, USA DESCRIPTION: Test config URL: www.w1abc.org SOFTWARE_ID: 20170620 PACKAGE_ID: MMDVM_HBlink GROUP_HANGTIME: 5 XLXMODULE: 4005 USE_ACL: True SUB_ACL: DENY:1 TGID_TS1_ACL: PERMIT:ALL TGID_TS2_ACL: PERMIT:ALL Rules: BRIDGES = { 'TEST BRIDGE': [ {'SYSTEM': 'HOTSPOTS', 'TS': 2, 'TGID': 2, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': [], 'RESET': []}, xlxd.zip {'SYSTEM': 'XLX020E', 'TS': 2, 'TGID': 2, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': [], 'RESET': []}, ] } UNIT = ['HOTSPOTS', 'XLX020E'] Wireshark capture done on the XLX attached so show how the sequence numbers are being properly incremented from the XLX end. See xlxd.zip.
[hblink3:master] New Issue Created by K2IE:
As discussed on the groups.io mailing list and submitted with some additional data. At the end of any transmission to a bridge group in which an XLXPEER participates, HBlink thinks the XLX is sending a brief new group call in response to the end of the original stream. I am fairly certain (through packet capture) that there are no out of sequence packets being sent back from the XLX. HBlink is somehow confused by what it thinks it sees. This results in artifacts of a new transmission in the log when none was went. It gets in the way of private calls working properly, as calls get forwarded to the XLX (where the desired recpient is not). Configs and other data follow: Log evidence: INFO 2020-10-27 09:40:24,091 (HOTSPOTS) GROUP CALL START STREAM ID: 3158937644 SUB: K2IE (3134090) PEER: 313409002 (313409002) TGID 2 (2), TS 2 INFO 2020-10-27 09:40:24,095 (HOTSPOTS) Conference Bridge: TEST BRIDGE, Call Bridged to HBP System: XLX020E TS: 2, TGID: 2 INFO 2020-10-27 09:40:29,990 (HOTSPOTS) GROUP CALL END STREAM ID: 3158937644 SUB: K2IE (3134090) PEER: 313409002 (313409002) TGID 2 (2), TS 2, Duration: 5.90 INFO 2020-10-27 09:40:30,021 (XLX020E) GROUP CALL START STREAM ID: 3158900736 SUB: K2IE (3134090) PEER: 3163081 (3163081) TGID 9 (9), TS 2 Config: [HOTSPOTS] MODE: MASTER ENABLED: True REPEAT: True MAX_PEERS: 10 EXPORT_AMBE: False IP: PORT: 54100 PASSPHRASE: passw0rd GROUP_HANGTIME: 5 USE_ACL: True REG_ACL: DENY:1 SUB_ACL: DENY:1 TGID_TS1_ACL: PERMIT:ALL TGID_TS2_ACL: PERMIT:ALL Can use to test against for this issue[XLX020E] MODE: XLXPEER ENABLED: True LOOSE: True EXPORT_AMBE: False IP: PORT: 54002 MASTER_IP: 66.175.215.217 MASTER_PORT: 62030 PASSPHRASE: passw0rd CALLSIGN: YOUR_VALID_CALL RADIO_ID: YOUR_VALID_RID RX_FREQ: 449000000 TX_FREQ: 444000000 TX_POWER: 25 COLORCODE: 1 SLOTS: 1 LATITUDE: 38.0000 LONGITUDE: -095.0000 HEIGHT: 75 LOCATION: Anywhere, USA DESCRIPTION: Test config URL: www.w1abc.org SOFTWARE_ID: 20170620 PACKAGE_ID: MMDVM_HBlink GROUP_HANGTIME: 5 XLXMODULE: 4005 USE_ACL: True SUB_ACL: DENY:1 TGID_TS1_ACL: PERMIT:ALL TGID_TS2_ACL: PERMIT:ALL Rules: BRIDGES = { 'TEST BRIDGE': [ {'SYSTEM': 'HOTSPOTS', 'TS': 2, 'TGID': 2, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': [], 'RESET': []}, xlxd.zip {'SYSTEM': 'XLX020E', 'TS': 2, 'TGID': 2, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': [], 'RESET': []}, ] } UNIT = ['HOTSPOTS', 'XLX020E'] Wireshark capture done on the XLX attached so show how the sequence numbers are being properly incremented from the XLX end. See xlxd.zip.
[hblink3:master] New Issue Created by K2IE:
As discussed on the groups.io mailing list and submitted with some additional data. At the end of any transmission to a bridge group in which an XLXPEER participates, HBlink thinks the XLX is sending a brief new group call in response to the end of the original stream. I am fairly certain (through packet capture) that there are no out of sequence packets being sent back from the XLX. HBlink is somehow confused by what it thinks it sees. This results in artifacts of a new transmission in the log when none was went. It gets in the way of private calls working properly, as calls get forwarded to the XLX (where the desired recpient is not). Configs and other data follow: Log evidence: INFO 2020-10-27 09:40:24,091 (HOTSPOTS) GROUP CALL START STREAM ID: 3158937644 SUB: K2IE (3134090) PEER: 313409002 (313409002) TGID 2 (2), TS 2 INFO 2020-10-27 09:40:24,095 (HOTSPOTS) Conference Bridge: TEST BRIDGE, Call Bridged to HBP System: XLX020E TS: 2, TGID: 2 INFO 2020-10-27 09:40:29,990 (HOTSPOTS) GROUP CALL END STREAM ID: 3158937644 SUB: K2IE (3134090) PEER: 313409002 (313409002) TGID 2 (2), TS 2, Duration: 5.90 INFO 2020-10-27 09:40:30,021 (XLX020E) GROUP CALL START STREAM ID: 3158900736 SUB: K2IE (3134090) PEER: 3163081 (3163081) TGID 9 (9), TS 2 Config: [HOTSPOTS] MODE: MASTER ENABLED: True REPEAT: True MAX_PEERS: 10 EXPORT_AMBE: False IP: PORT: 54100 PASSPHRASE: passw0rd GROUP_HANGTIME: 5 USE_ACL: True REG_ACL: DENY:1 SUB_ACL: DENY:1 TGID_TS1_ACL: PERMIT:ALL TGID_TS2_ACL: PERMIT:ALL Ok to test against XLX020E for this issue [XLX020E] MODE: XLXPEER ENABLED: True LOOSE: True EXPORT_AMBE: False IP: PORT: 54002 MASTER_IP: 66.175.215.217 MASTER_PORT: 62030 PASSPHRASE: passw0rd CALLSIGN: YOUR_VALID_CALL RADIO_ID: YOUR_VALID_RID RX_FREQ: 449000000 TX_FREQ: 444000000 TX_POWER: 25 COLORCODE: 1 SLOTS: 1 LATITUDE: 38.0000 LONGITUDE: -095.0000 HEIGHT: 75 LOCATION: Anywhere, USA DESCRIPTION: Test config URL: www.w1abc.org SOFTWARE_ID: 20170620 PACKAGE_ID: MMDVM_HBlink GROUP_HANGTIME: 5 XLXMODULE: 4005 USE_ACL: True SUB_ACL: DENY:1 TGID_TS1_ACL: PERMIT:ALL TGID_TS2_ACL: PERMIT:ALL Rules: BRIDGES = { 'TEST BRIDGE': [ {'SYSTEM': 'HOTSPOTS', 'TS': 2, 'TGID': 2, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': [], 'RESET': []}, xlxd.zip {'SYSTEM': 'XLX020E', 'TS': 2, 'TGID': 2, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': [], 'RESET': []}, ] } UNIT = ['HOTSPOTS', 'XLX020E'] Wireshark capture done on the XLX attached so show how the sequence numbers are being properly incremented from the XLX end. See xlxd.zip.
|
|
|
|
[hblink3:master] reported: Problem connectig to hblink
#github
HBlink@DVSwitch.groups.io Integration <HBlink@...>
[hblink3:master] New Comment on Issue #3 Problem connectig to hblink
commit to git checkout d68241918b95944544d2ef9e661a615d98b5c92a solved my problem
|
|
|
|
Updates to Github
#github
HBlink@DVSwitch.groups.io Integration <HBlink@...>
[hblink3:master] New Issue Created by bouab002:
Hello;I have problems connecting to another Hblink server, the server restarts the authentication very 1S connection is working and I get the QSO. COFIG: [DMR-FRANCOPHONE] MODE: PEER ENABLED: True LOOSE: False EXPORT_AMBE: False IP: 10.28.200.6 PORT: 54004 MASTER_IP: 137.74.195.150 MASTER_PORT: 62030 PASSPHRASE: passw0rd CALLSIGN: FXXXX RADIO_ID: 2080XXX99 RX_FREQ: 443900000 TX_FREQ: 443900000 TX_POWER: 25 COLORCODE: 1 SLOTS: 1 LATITUDE: XX.XXXX LONGITUDE: X.XXXX HEIGHT: 75 LOCATION: XXXXXX,XXXXx DESCRIPTION: HBlink URL: XXXXXXXXXXXXXXX SOFTWARE_ID: 20170620 PACKAGE_ID: MMDVM_HBlink GROUP_HANGTIME: 5 OPTIONS: USE_ACL: True SUB_ACL: DENY:1 TGID_TS1_ACL: PERMIT:ALL TGID_TS2_ACL: PERMIT:ALL LOGS: INFO 2020-10-31 11:35:32,445 (DMR-FRANCOPHONE) Repeater Authentication Accepted INFO 2020-10-31 11:35:32,446 (DMR-FRANCOPHONE) Repeater Configuration Sent INFO 2020-10-31 11:35:32,459 (DMR-FRANCOPHONE) Repeater Configuration Accepted INFO 2020-10-31 11:35:32,460 (DMR-FRANCOPHONE) Sent options: (b'Type=HBlink;') INFO 2020-10-31 11:35:37,414 (DMR-FRANCOPHONE) Sending login request to master 137.74.195.150:62030 INFO 2020-10-31 11:35:37,429 (DMR-FRANCOPHONE) Repeater Login ACK Received with 32bit ID: 4084617675 INFO 2020-10-31 11:35:37,443 (DMR-FRANCOPHONE) Repeater Authentication Accepted INFO 2020-10-31 11:35:37,443 (DMR-FRANCOPHONE) Repeater Configuration Sent INFO 2020-10-31 11:35:37,457 (DMR-FRANCOPHONE) Repeater Configuration Accepted INFO 2020-10-31 11:35:37,458 (DMR-FRANCOPHONE) Sent options: (b'Type=HBlink;') INFO 2020-10-31 11:35:42,416 (DMR-FRANCOPHONE) Sending login request to master 137.74.195.150:62030 INFO 2020-10-31 11:35:42,431 (DMR-FRANCOPHONE) Repeater Login ACK Received with 32bit ID: 2731809743 INFO 2020-10-31 11:35:42,445 (DMR-FRANCOPHONE) Repeater Authentication Accepted INFO 2020-10-31 11:35:42,446 (DMR-FRANCOPHONE) Repeater Configuration Sent INFO 2020-10-31 11:35:42,460 (DMR-FRANCOPHONE) Repeater Configuration Accepted INFO 2020-10-31 11:35:42,462 (DMR-FRANCOPHONE) Sent options: (b'Type=HBlink;') INFO 2020-10-31 11:35:47,415 (DMR-FRANCOPHONE) Sending login request to master 137.74.195.150:62030 INFO 2020-10-31 11:35:47,430 (DMR-FRANCOPHONE) Repeater Login ACK Received with 32bit ID: 859213554 INFO 2020-10-31 11:35:47,444 (DMR-FRANCOPHONE) Repeater Authentication Accepted INFO 2020-10-31 11:35:47,445 (DMR-FRANCOPHONE) Repeater Configuration Sent INFO 2020-10-31 11:35:47,459 (DMR-FRANCOPHONE) Repeater Configuration Accepted INFO 2020-10-31 11:35:47,461 (DMR-FRANCOPHONE) Sent options: (b'Type=HBlink;') Regards, F4IRF
[hblink3:master] New Issue Created by bouab002:
Hello;I have problems connecting to another Hblink server, the server restarts the authentication very 1S connection is working and I get the QSO. COFIG: [DMR-FRANCOPHONE] MODE: PEER ENABLED: True LOOSE: False EXPORT_AMBE: False IP: PORT: 54004 MASTER_IP: 137.74.195.150 MASTER_PORT: 62030 PASSPHRASE: passw0rd CALLSIGN: FXXXX RADIO_ID: 2080XXX99 RX_FREQ: 443900000 TX_FREQ: 443900000 TX_POWER: 25 COLORCODE: 1 SLOTS: 1 LATITUDE: XX.XXXX LONGITUDE: X.XXXX HEIGHT: 75 LOCATION: XXXXXX,XXXXx DESCRIPTION: HBlink URL: XXXXXXXXXXXXXXX SOFTWARE_ID: 20170620 PACKAGE_ID: MMDVM_HBlink GROUP_HANGTIME: 5 OPTIONS: USE_ACL: True SUB_ACL: DENY:1 TGID_TS1_ACL: PERMIT:ALL TGID_TS2_ACL: PERMIT:ALL LOGS: INFO 2020-10-31 11:35:32,445 (DMR-FRANCOPHONE) Repeater Authentication Accepted INFO 2020-10-31 11:35:32,446 (DMR-FRANCOPHONE) Repeater Configuration Sent INFO 2020-10-31 11:35:32,459 (DMR-FRANCOPHONE) Repeater Configuration Accepted INFO 2020-10-31 11:35:32,460 (DMR-FRANCOPHONE) Sent options: (b'Type=HBlink;') INFO 2020-10-31 11:35:37,414 (DMR-FRANCOPHONE) Sending login request to master 137.74.195.150:62030 INFO 2020-10-31 11:35:37,429 (DMR-FRANCOPHONE) Repeater Login ACK Received with 32bit ID: 4084617675 INFO 2020-10-31 11:35:37,443 (DMR-FRANCOPHONE) Repeater Authentication Accepted INFO 2020-10-31 11:35:37,443 (DMR-FRANCOPHONE) Repeater Configuration Sent INFO 2020-10-31 11:35:37,457 (DMR-FRANCOPHONE) Repeater Configuration Accepted INFO 2020-10-31 11:35:37,458 (DMR-FRANCOPHONE) Sent options: (b'Type=HBlink;') INFO 2020-10-31 11:35:42,416 (DMR-FRANCOPHONE) Sending login request to master 137.74.195.150:62030 INFO 2020-10-31 11:35:42,431 (DMR-FRANCOPHONE) Repeater Login ACK Received with 32bit ID: 2731809743 INFO 2020-10-31 11:35:42,445 (DMR-FRANCOPHONE) Repeater Authentication Accepted INFO 2020-10-31 11:35:42,446 (DMR-FRANCOPHONE) Repeater Configuration Sent INFO 2020-10-31 11:35:42,460 (DMR-FRANCOPHONE) Repeater Configuration Accepted INFO 2020-10-31 11:35:42,462 (DMR-FRANCOPHONE) Sent options: (b'Type=HBlink;') INFO 2020-10-31 11:35:47,415 (DMR-FRANCOPHONE) Sending login request to master 137.74.195.150:62030 INFO 2020-10-31 11:35:47,430 (DMR-FRANCOPHONE) Repeater Login ACK Received with 32bit ID: 859213554 INFO 2020-10-31 11:35:47,444 (DMR-FRANCOPHONE) Repeater Authentication Accepted INFO 2020-10-31 11:35:47,445 (DMR-FRANCOPHONE) Repeater Configuration Sent INFO 2020-10-31 11:35:47,459 (DMR-FRANCOPHONE) Repeater Configuration Accepted INFO 2020-10-31 11:35:47,461 (DMR-FRANCOPHONE) Sent options: (b'Type=HBlink;') Regards, F4IRF
|
|
|
|
Re: XLX Prevents Private Calls from Working (Somtimes)
#support
Dan K2IE
@Randy (and anyone else interested in testing):
Please note that XLXMODULE in the config should be changed from 4004 to 4005 to use Module E. Thanks.
|
|
|