"Blocked" Message on Brandmeister


Steve N4IRS
 

Well,
Then I don't know what to tell ya.

On 06/09/2018 07:33 PM, Mike Swiatkowski via Groups.Io wrote:
Not that I know of....


Mike, AA9VI
 

Not that I know of....


Steve N4IRS
 

I: 2018-06-08 19:08:24.977 DMR Network Parameters
I: 2018-06-08 19:08:24.977     Address: 104.236.174.109
I: 2018-06-08 19:08:24.977     Port: 55555
I: 2018-06-08 19:08:24.977     Local: 62032
I: 2018-06-08 19:08:24.977     Jitter: 360ms
I: 2018-06-08 19:08:24.977     Slot 1: disabled
I: 2018-06-08 19:08:24.977     Slot 2: enabled
I: 2018-06-08 19:08:24.977     Mode Hang: 3s
I: 2018-06-08 19:08:24.977     Options: StartRef=4649;RelinkTime=0;UserLink=1
I: 2018-06-08 19:08:24.977 Info Parameters
I: 2018-06-08 19:08:24.978     Callsign: N4IRS
I: 2018-06-08 19:08:24.978     RX Frequency: 222340000Hz
I: 2018-06-08 19:08:24.978     TX Frequency: 224940000Hz
I: 2018-06-08 19:08:24.978     Power: 1W
I: 2018-06-08 19:08:24.978     Latitude: 41.733299deg N
I: 2018-06-08 19:08:24.978     Longitude: -50.399899deg E
I: 2018-06-08 19:08:24.978     Height: 0m
I: 2018-06-08 19:08:24.978     Location: "Iceberg, North Atlantic"
I: 2018-06-08 19:08:24.978     Description: "MMDVM_Bridge"
I: 2018-06-08 19:08:24.978     URL: "https://groups.io/g/DVSwitch"
M: 2018-06-08 19:08:24.978 DMR, Opening DMR Network
I: 2018-06-08 19:08:24.978 RSSI
I: 2018-06-08 19:08:24.978     Mapping File: RSSI.dat
W: 2018-06-08 19:08:24.978 Cannot open the RSSI data file - RSSI.dat
I: 2018-06-08 19:08:24.978 DMR Id Lookups
I: 2018-06-08 19:08:24.978     File: /var/lib/mmdvm/DMRIds.dat
I: 2018-06-08 19:08:24.978     Reload: 24 hours
I: 2018-06-08 19:08:25.062 Loaded 57133 Ids to the DMR callsign lookup table
I: 2018-06-08 19:08:25.062 DMR RF Parameters
I: 2018-06-08 19:08:25.062 Started the DMR Id lookup reload thread
I: 2018-06-08 19:08:25.062     Id: 3112138
I: 2018-06-08 19:08:25.062     Color Code: 1
I: 2018-06-08 19:08:25.062     Self Only: no
I: 2018-06-08 19:08:25.062     Embedded LC Only: yes
I: 2018-06-08 19:08:25.062     Dump Talker Alias Data: no
I: 2018-06-08 19:08:25.062     Prefixes: 0
I: 2018-06-08 19:08:25.062     Call Hang: 3s
I: 2018-06-08 19:08:25.063     TX Hang: 3s
I: 2018-06-08 19:08:25.063     Mode Hang: 10s
M: 2018-06-08 19:08:25.063 DMR, Opening INI file: DVSwitch.ini
M: 2018-06-08 19:08:25.063 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2018-06-08 19:08:25.063 DMR, Setting [DMR] TXPort -> 31100
M: 2018-06-08 19:08:25.063 DMR, Setting [DMR] RXPort -> 31103
M: 2018-06-08 19:08:25.063 DMR, Setting [DMR] Slot -> 1
M: 2018-06-08 19:08:25.063 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
M: 2018-06-08 19:08:25.063 MMDVM_Bridge-20180526 is running
D: 2018-06-08 19:08:35.153 DMR, Sending authorisation
D: 2018-06-08 19:08:35.245 DMR, Sending configuration
D: 2018-06-08 19:08:35.337 DMR, Sending options
M: 2018-06-08 19:08:35.429 DMR, Logged into the master successfully
M: 2018-06-08 19:09:26.536 DMR Slot 2, received network voice header from 4649 to TG 9
M: 2018-06-08 19:09:33.274 DMR Slot 2, received network end of voice transmission, 6.6 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-08 19:23:50.143 DMR Slot 2, received network late entry from WB9PZM to TG 9
D: 2018-06-08 19:23:51.145 DMR Slot 2, lost audio for 408ms filling in
D: 2018-06-08 19:23:51.553 DMR Slot 2, lost audio for 408ms filling in
D: 2018-06-08 19:23:51.962 DMR Slot 2, lost audio for 409ms filling in
M: 2018-06-08 19:23:52.237 DMR Slot 2, network watchdog has expired, 2.2 seconds, 50% packet loss, BER: 0.0%

As you can see, I connected to the Master at 19:08Z and the last traffic I saw was at 19:23Z As of right now, (19:51Z) I'm still connected. I think there may be a keep alive being missed. Are there any firewall rules involved?

73, Steve N4IRS

On 6/8/2018 3:03 PM, Mike Swiatkowski via Groups.Io wrote:
attached...


Mike, AA9VI
 

attached...


Steve N4IRS
 

Mike,
Please post your MMDVM_Bridge.ini


On 06/07/2018 11:08 PM, Mike Swiatkowski via Groups.Io wrote:
Steve,
I don't have a "blocked message" but I do have DMR disconnecting every 2 minutes on DMR+.  The login to the MMDVM server is successful but exactly 2 minutes later it says Closing DMR Network.  Then immediately it Opens DMR Network.  This cycle repeats every 2 mins.

Mike


Mike, AA9VI
 

Steve,
I don't have a "blocked message" but I do have DMR disconnecting every 2 minutes on DMR+.  The login to the MMDVM server is successful but exactly 2 minutes later it says Closing DMR Network.  Then immediately it Opens DMR Network.  This cycle repeats every 2 mins.

Mike


Steven Blackford
 

Hey Steve,
    We have had this problem on 2 ASL<->DMR bridges when there was a lot of traffic going on. iE, nets on TheGuild TG & ASL node 47374. I installed a the bridge in a secondary node that’s connected most of the time. but several times when the Morning Net was going on that’s attached to EchoLink & IRLP besides ALS, they were having the problem with being blocked on DMR. The loopban tool took it as too many key ups on n a short amount of time, you’d have to shutdown the MMDVM side of the bridge for an hour. I’ve also had the same problem on TG 31444 with a similar problem.  Jason talked to Corey about it. Since making the changes to both bridges, the problem hasn’t returned yet. Just passing on the info while waiting for an array to boot up. 73 de K4SQI!

Steve, K4SQI 

On Tue, Jun 5, 2018 at 22:51 Steve N4IRS <szingman@...> wrote:
So,
I have a couple of questions:
1: What type of bridges are experiencing the problem? Analog to digital? digital to digital?
The default hang value is 2000 ms in Analog_Bridge.ini Which equates to the minimum time presented to BM. A signal can not be less then this value. This was implemented to alleviate the loop detector issue.

Here is the default output from MMDVM Bridge:
I: 2018-06-06 01:57:23.512 DMR Network Parameters
I: 2018-06-06 01:57:23.512     Mode Hang: 3s
I: 2018-06-06 02:26:55.222 DMR RF Parameters
I: 2018-06-06 01:57:23.558     Call Hang: 3s
I: 2018-06-06 01:57:23.558     TX Hang: 3s
I: 2018-06-06 01:57:23.558     Mode Hang: 10s

I won't paste the default MMDVM_Bridge.ini but you will find that the values already mirror the suggested values.
We appreciate your efforts, however since we already dealt with the loop detector we could have helped trouble shoot this.

73, Steve N4IRS


On 06/05/2018 09:35 PM, Steven Blackford wrote:
Try these settings for a way to deal with the loop fixer on the BM Network. We have noticed it on a couple of bridges & has solved the issue so far for us.  Hope it helps. 73 de K4SQI!

Steve @ work. :-)



---------- Forwarded message ---------
From: Jason Ford <w4jmf@...>
Date: Wed, May 30, 2018 at 13:57
Subject: "Blocked" Message on Brandmeister
To: Steven Blackford <kb7sqi@...>, Wayne Cornish <g7oki@...>, Jeffrey Lehman, KC8QCH <kc8qch@...>


Greetings Gents:
After much research and a chat with the BM Admins, I have discovered the source of the problem for the blocked message.

All BM Masters run LoopBan.  If the server sees 5 calls shorter than 2 seconds over a 1 minute time, it will think it is a loop and place a 10 minute ban on the call.  LoopBans are in place for 1 hour automatically.  

With this in mind I went into the MMDVM_Bridge settings and made a couple of adjustments to the settings:
[General]
RFModeHang=0 . changed to 10
NetModeHang=0, changed to 3
[DMR]
CallHang=0, changed to 3
TXHang=0, changed to 3

My thought process here is that if the 2 second mark is key, just make all TX's at least 2 secs.  So far today, I have not seen the issues from before.

Just sharing my experiments for future reference.

Jason Ford, W4JMF
Executive Director
World Wide Amateur Radio Guild Inc.

CONFIDENTIALITY NOTICE:
The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message or their agent, or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. 

--
-----
Steve, kb7sqi@...

--
-----
Steve, kb7sqi@...


Steve N4IRS
 

So,
I have a couple of questions:
1: What type of bridges are experiencing the problem? Analog to digital? digital to digital?
The default hang value is 2000 ms in Analog_Bridge.ini Which equates to the minimum time presented to BM. A signal can not be less then this value. This was implemented to alleviate the loop detector issue.

Here is the default output from MMDVM Bridge:
I: 2018-06-06 01:57:23.512 DMR Network Parameters
I: 2018-06-06 01:57:23.512     Mode Hang: 3s
I: 2018-06-06 02:26:55.222 DMR RF Parameters
I: 2018-06-06 01:57:23.558     Call Hang: 3s
I: 2018-06-06 01:57:23.558     TX Hang: 3s
I: 2018-06-06 01:57:23.558     Mode Hang: 10s

I won't paste the default MMDVM_Bridge.ini but you will find that the values already mirror the suggested values.
We appreciate your efforts, however since we already dealt with the loop detector we could have helped trouble shoot this.

73, Steve N4IRS

On 06/05/2018 09:35 PM, Steven Blackford wrote:
Try these settings for a way to deal with the loop fixer on the BM Network. We have noticed it on a couple of bridges & has solved the issue so far for us.  Hope it helps. 73 de K4SQI!

Steve @ work. :-)



---------- Forwarded message ---------
From: Jason Ford <w4jmf@...>
Date: Wed, May 30, 2018 at 13:57
Subject: "Blocked" Message on Brandmeister
To: Steven Blackford <kb7sqi@...>, Wayne Cornish <g7oki@...>, Jeffrey Lehman, KC8QCH <kc8qch@...>


Greetings Gents:
After much research and a chat with the BM Admins, I have discovered the source of the problem for the blocked message.

All BM Masters run LoopBan.  If the server sees 5 calls shorter than 2 seconds over a 1 minute time, it will think it is a loop and place a 10 minute ban on the call.  LoopBans are in place for 1 hour automatically.  

With this in mind I went into the MMDVM_Bridge settings and made a couple of adjustments to the settings:
[General]
RFModeHang=0 . changed to 10
NetModeHang=0, changed to 3
[DMR]
CallHang=0, changed to 3
TXHang=0, changed to 3

My thought process here is that if the 2 second mark is key, just make all TX's at least 2 secs.  So far today, I have not seen the issues from before.

Just sharing my experiments for future reference.

Jason Ford, W4JMF
Executive Director
World Wide Amateur Radio Guild Inc.

CONFIDENTIALITY NOTICE:
The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message or their agent, or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. 

--
-----
Steve, kb7sqi@...


Steven Blackford
 

Try these settings for a way to deal with the loop fixer on the BM Network. We have noticed it on a couple of bridges & has solved the issue so far for us.  Hope it helps. 73 de K4SQI!

Steve @ work. :-)



---------- Forwarded message ---------
From: Jason Ford <w4jmf@...>
Date: Wed, May 30, 2018 at 13:57
Subject: "Blocked" Message on Brandmeister
To: Steven Blackford <kb7sqi@...>, Wayne Cornish <g7oki@...>, Jeffrey Lehman, KC8QCH <kc8qch@...>


Greetings Gents:
After much research and a chat with the BM Admins, I have discovered the source of the problem for the blocked message.

All BM Masters run LoopBan.  If the server sees 5 calls shorter than 2 seconds over a 1 minute time, it will think it is a loop and place a 10 minute ban on the call.  LoopBans are in place for 1 hour automatically.  

With this in mind I went into the MMDVM_Bridge settings and made a couple of adjustments to the settings:
[General]
RFModeHang=0 . changed to 10
NetModeHang=0, changed to 3
[DMR]
CallHang=0, changed to 3
TXHang=0, changed to 3

My thought process here is that if the 2 second mark is key, just make all TX's at least 2 secs.  So far today, I have not seen the issues from before.

Just sharing my experiments for future reference.

Jason Ford, W4JMF
Executive Director
World Wide Amateur Radio Guild Inc.

CONFIDENTIALITY NOTICE:
The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message or their agent, or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. 

--
-----
Steve, kb7sqi@...