Topics

user blocked

Charles Wiant
 

After a few quick keys I get user blocked then no traffic passes. Is there a fix to to this because I cannot control all who comes in. thank you




Scanned by McAfee and confirmed virus-free.

Mike KB8JNM
 

Guessing you are referring to DMR,

AB

set minTxTimeMS =    higher ,  2000 works for me but I think you may need 2500 (miliseconds)

It says that if it is shorter, it will be at least that.


On 5/26/2019 8:02 PM, Charles Wiant via Groups.Io wrote:

After a few quick keys I get user blocked then no traffic passes. Is there a fix to to this because I cannot control all who comes in. thank you




Scanned by McAfee and confirmed virus-free.

Charles Wiant
 

Thank you will give it a try and yes dmr bridge .

 

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Mike KB8JNM
Sent: Sunday, May 26, 2019 8:10 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] user blocked

 

Guessing you are referring to DMR,

AB

set minTxTimeMS =    higher ,  2000 works for me but I think you may need 2500 (miliseconds)

It says that if it is shorter, it will be at least that.

 

On 5/26/2019 8:02 PM, Charles Wiant via Groups.Io wrote:

After a few quick keys I get user blocked then no traffic passes. Is there a fix to to this because I cannot control all who comes in. thank you

 


Scanned by McAfee and confirmed virus-free.

Roland W9HPX
 

This is an older post, but it the same thing I am experiencing on the Carolina Link bridge between C4FM and BM TG 31374.  The answers to the post do not exactly apply to our configuration.  The Carolina Link bridge is a single instance of MMDVM_Bridge between YSFreflector #79602 and BM TG 31374.  I understand the User Blocked message is BM's automatic Loop Detection and blocks the TG for an hour before being lifted.  Here is a log excerpt from today where a user on a FT-2D keyed more than 5 times in a row for about a second, triggering the block.  This has occurred a few times over last month, but otherwise the bridge seems to work OK.  

M: 2019-10-03 14:52:38.712 Received data from BMF        to *****E5Itr at NC4CL    
M: 2019-10-03 14:52:40.114 Received end of transmission
M: 2019-10-03 14:52:43.110 Received data from BMF        to *****E5Itr at NC4CL    
M: 2019-10-03 14:52:44.013 Received end of transmission
M: 2019-10-03 14:52:50.817 Received data from BMF        to *****E5Itr at NC4CL    
M: 2019-10-03 14:52:52.413 Received end of transmission
M: 2019-10-03 14:53:02.226 Received data from BMF        to *****E5Itr at NC4CL    
M: 2019-10-03 14:53:03.628 Received end of transmission
M: 2019-10-03 14:53:11.170 Received data from BMF        to *****E5Itr at NC4CL    
M: 2019-10-03 14:53:12.572 Received end of transmission
M: 2019-10-03 14:53:15.971 Received data from BMF        to *****E5Itr at NC4CL    
M: 2019-10-03 14:53:16.873 Received end of transmission
M: 2019-10-03 14:53:18.715 Currently linked repeaters/gateways:
M: 2019-10-03 14:53:18.715     NC4CL     : 127.0.0.1:3200 3/60
M: 2019-10-03 14:53:18.715     KM4NMW    : 174.99.205.58:42000 3/60
M: 2019-10-03 14:53:18.715     AJ4RC     : 47.133.184.2:42000 0/60
M: 2019-10-03 14:53:18.715     KN4MGS    : 71.76.120.46:42000 0/60
M: 2019-10-03 14:53:18.715     K9VMY     : 67.184.245.24:1024 3/60
M: 2019-10-03 14:53:18.715     K4WSC     : 71.75.100.129:57352 4/60
M: 2019-10-03 14:53:18.715     NC4CL     : 208.104.55.181:22694 5/60
M: 2019-10-03 14:53:18.715     N8TA      : 71.194.103.93:44809 4/60
M: 2019-10-03 14:53:18.715     K2CPR     : 173.94.224.95:62831 3/60
M: 2019-10-03 14:53:18.715     AE9EE     : 69.245.172.148:42000 3/60
M: 2019-10-03 14:53:18.715     KD8AGO    : 72.11.7.43:49418 4/60
M: 2019-10-03 14:53:18.715     K4WSC     : 71.75.100.129:49554 4/60
M: 2019-10-03 14:53:18.715     KN4HND    : 174.80.206.103:42000 1/60
M: 2019-10-03 14:53:18.715     KD8AGO    : 72.11.7.43:63146 2/60
M: 2019-10-03 14:53:18.715     AE4BT     : 96.33.4.193:42000 1/60
M: 2019-10-03 14:53:18.715     KI4BWS    : 75.89.69.22:42000 1/60
M: 2019-10-03 14:53:20.149 Received data from      31374 to        ALL at NC4CL    
M: 2019-10-03 14:53:21.221 Received end of transmission
M: 2019-10-03 14:53:51.687 Received data from BMF        to *****E5Itr at NC4CL    
M: 2019-10-03 14:53:53.089 Received end of transmission
M: 2019-10-03 14:53:56.385 Received data from      31374 to        ALL at NC4CL    
M: 2019-10-03 14:53:57.466 Received end of transmission
M: 2019-10-03 14:55:18.727 Currently linked repeaters/gateways:
M: 2019-10-03 14:55:18.727     NC4CL     : 127.0.0.1:3200 3/60
M: 2019-10-03 14:55:18.727     KM4NMW    : 174.99.205.58:42000 3/60
M: 2019-10-03 14:55:18.728     AJ4RC     : 47.133.184.2:42000 0/60
M: 2019-10-03 14:55:18.728     KN4MGS    : 71.76.120.46:42000 0/60
M: 2019-10-03 14:55:18.728     K9VMY     : 67.184.245.24:1024 2/60
M: 2019-10-03 14:55:18.728     K4WSC     : 71.75.100.129:57352 4/60
M: 2019-10-03 14:55:18.728     NC4CL     : 208.104.55.181:22694 1/60
M: 2019-10-03 14:55:18.728     N8TA      : 71.194.103.93:44809 4/60
M: 2019-10-03 14:55:18.728     K2CPR     : 173.94.224.95:62831 3/60
M: 2019-10-03 14:55:18.728     AE9EE     : 69.245.172.148:42000 3/60
M: 2019-10-03 14:55:18.728     KD8AGO    : 72.11.7.43:49418 4/60
M: 2019-10-03 14:55:18.728     K4WSC     : 71.75.100.129:49554 3/60
M: 2019-10-03 14:55:18.728     KN4HND    : 174.80.206.103:42000 0/60
M: 2019-10-03 14:55:18.728     KD8AGO    : 72.11.7.43:63146 2/60
M: 2019-10-03 14:55:18.728     AE4BT     : 96.33.4.193:42000 1/60
M: 2019-10-03 14:55:18.728     KI4BWS    : 75.89.69.22:42000 11/60
M: 2019-10-03 14:56:38.706 Received data from BMF        to *****E5Itr at NC4CL    
M: 2019-10-03 14:56:40.108 Received end of transmission
M: 2019-10-03 14:56:43.367 Received data from      31374 to        ALL at NC4CL    
M: 2019-10-03 14:56:44.443 Received end of transmission

As can be seen, the user does not have a proper callsign entered into his radio.  What can be done to fix this somewhat infrequent blocking occurrence?

73, Roland Kraatz W9HPX
Manager for the NC4CL Carolina Link Bridge