XLX to HBlink issues. #214
Comments
|
One of the mechanism to ensure a valid DMR id to user mapping is to use
an registered ID.
Isn't it correct to expect a registered ID of the DMR side?
The only workaround should be to use a valid, registered DMR id on the
XLX side and to prevent DMR communications for unregistered callsigns.
Otherwise we will end to have a ban on XLX nodes in DMR networks for not
ensuring valid user identification.
Just my 2c...
Marius, YO2LOJ
…On 06/03/2022 20:21, Jay wrote:
When connecting XLX to HBlink as XLXPEER. If a user on the XLX side
does NOT have a registered DMR id then XLX presents the DMR id of "0"
to HBlink which breaks the DMR side. Need a way to specify/present
alternate DMR ID to HBlink if the XLX user is not registered on DMR.
|
|
There not on the DMR side. They are on the D-STAR side hence the problem. Not all D-STAR users have DMR or DMR id's. Brandmeister fixes this issue by converting the "0" talkgroup through there system to your Group Talkgroup ie: 310441 for us. So if a user on D-STAR dont have a DMR ID it will come through to the DMR side as 310441.
From: "Marius Petrescu, YO2LOJ" ***@***.***>
To: "LX3JL/xlxd" ***@***.***>
Cc: "Jay" ***@***.***>, "Author" ***@***.***>
Sent: Sunday, March 6, 2022 3:16:42 PM
Subject: Re: [LX3JL/xlxd] XLX to HBlink issues. (Issue #214)
One of the mechanism to ensure a valid DMR id to user mapping is to use
an registered ID.
Isn't it correct to expect a registered ID of the DMR side?
The only workaround should be to use a valid, registered DMR id on the
XLX side and to prevent DMR communications for unregistered callsigns.
Otherwise we will end to have a ban on XLX nodes in DMR networks for not
ensuring valid user identification.
Just my 2c...
Marius, YO2LOJ
On 06/03/2022 20:21, Jay wrote:
When connecting XLX to HBlink as XLXPEER. If a user on the XLX side
does NOT have a registered DMR id then XLX presents the DMR id of "0"
to HBlink which breaks the DMR side. Need a way to specify/present
alternate DMR ID to HBlink if the XLX user is not registered on DMR.
—
Reply to this email directly, [ #214 (comment) | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/AFRLALM6MX5IWQY5WX6ES3TU6UHCVANCNFSM5QBOECMA | unsubscribe ] .
Triage notifications on the go with GitHub Mobile for [ https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 | iOS ] or [ https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub | Android ] .
You are receiving this because you authored the thread. Message ID: ***@***.***>
|
|
Yes, this is exactly what I was talking about. A user on the D-star side
without a DMR ID should NOT have access to DMR, since on the DMR network
the user is uniquely, and i think legally, identified by his DMR id.
IMHO the same should apply to any D-Star/C4FM to DMR gateways (e.g. on
my reflectors, this is enforced in the YSF2DMR), converting to a
"generic" node ID being actually identity spoofing, circumventing user
identification.
…On 06/03/2022 22:25, Jay wrote:
There not on the DMR side. They are on the D-STAR side hence the
problem. Not all D-STAR users have DMR or DMR id's. Brandmeister fixes
this issue by converting the "0" talkgroup through there system to
your Group Talkgroup ie: 310441 for us. So if a user on D-STAR dont
have a DMR ID it will come through to the DMR side as 310441.
From: "Marius Petrescu, YO2LOJ" ***@***.***>
To: "LX3JL/xlxd" ***@***.***>
Cc: "Jay" ***@***.***>, "Author" ***@***.***>
Sent: Sunday, March 6, 2022 3:16:42 PM
Subject: Re: [LX3JL/xlxd] XLX to HBlink issues. (Issue #214)
One of the mechanism to ensure a valid DMR id to user mapping is to use
an registered ID.
Isn't it correct to expect a registered ID of the DMR side?
The only workaround should be to use a valid, registered DMR id on the
XLX side and to prevent DMR communications for unregistered callsigns.
Otherwise we will end to have a ban on XLX nodes in DMR networks for not
ensuring valid user identification.
Just my 2c...
Marius, YO2LOJ
On 06/03/2022 20:21, Jay wrote:
> When connecting XLX to HBlink as XLXPEER. If a user on the XLX side
> does NOT have a registered DMR id then XLX presents the DMR id of "0"
> to HBlink which breaks the DMR side. Need a way to specify/present
> alternate DMR ID to HBlink if the XLX user is not registered on DMR.
—
Reply to this email directly, [
#214 (comment) |
view it on GitHub ] , or [
https://github.com/notifications/unsubscribe-auth/AFRLALM6MX5IWQY5WX6ES3TU6UHCVANCNFSM5QBOECMA
| unsubscribe ] .
Triage notifications on the go with GitHub Mobile for [
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
| iOS ] or [
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub
| Android ] .
You are receiving this because you authored the thread. Message ID:
***@***.***>
—
Reply to this email directly, view it on GitHub
<#214 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABIRKWDEEPW2IAKJQ2NEB23U6UICVANCNFSM5QBOECMA>.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When connecting XLX to HBlink as XLXPEER. If a user on the XLX side does NOT have a registered DMR id then XLX presents the DMR id of "0" to HBlink which breaks the DMR side. Need a way to specify/present alternate DMR ID to HBlink if the XLX user is not registered on DMR.
Thx
73
The text was updated successfully, but these errors were encountered: