Updates to Github #github


HBlink@DVSwitch.groups.io Integration <HBlink@...>
 

[hblink3:master] New Issue Created by K2IE:
#4 HBlink incorrecly sees data as new stream from XLX when none sent

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:
#4 HBlink incorrecly sees data as new group call from XLX when none sent

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:
#4 HBlink incorrecly sees data as new group call from XLX when none sent

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:
#4 HBlink incorrecly sees data as new group call from XLX when none sent

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.


HBlink@DVSwitch.groups.io Integration <HBlink@...>
 

[hblink3:master] New Issue Created by bouab002:
#3 Problem connectig to hblink

Hello;I have problems connecting to another Hblink server, the server restarts the authentication very 1S connection is working and I get the QSO.

http://137.74.195.150:8080

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:
#3 Problem connectig to hblink

Hello;I have problems connecting to another Hblink server, the server restarts the authentication very 1S connection is working and I get the QSO.

http://137.74.195.150:8080

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