Date   

Re: Unable to connect to Brandmeister using HBlink #hblink

Doug
 

Unfortunately I cannot test to see if I could ping the master as I deleted the original server when the new one was going.

But as I was receiving back from the master - Repeater Authentication Accepted - I would assume that pinging it would not be a problem.
its something that happens in the next 2 lines  -
Repeater Configuration Sent - MSTCL Recieved.
I tried searching to see what
MSTCL Recieved means and come up with absolutely nothing.
All I know for certain is the same setup from a different IP works and you do not get back from the master
MSTCL Recieved and everything connects as normal.
Doug ZL3DMH


Re: Unable to connect to Brandmeister using HBlink #hblink

Steve N4IRS
 

Can you ping the master from the IP address you think is blocked?

On 2/11/21 10:00 PM, Doug wrote:
I have a HBLink server thats been running for many months now on a cloud server, about 2 weeks ago it just stopped connecting to brandmeister.
On starting it manualy I noticed an error coming back MSTCL Recieved the same as in your posting.
I have repeater freqs set in the connectors to BM and also my own Password login set as it allways has been  and was running.
The only way I could get my system back going was to image the server, start a new server with a different IP address and put the image back on the new server start it and it all worked instantly.
From this I got that  
MSTCL Recieved means the IP address has been blocked.


Doug ZL3DMH


Re: Unable to connect to Brandmeister using HBlink #hblink

Doug - W4DBG
 

If you are connecting via a peer in hbklink.cfg to Brandmeister you should disconnect it and request an OpenBridge. 



On Thu, Feb 11, 2021 at 9:33 PM Doug <zl3dmh@...> wrote:
I have a HBLink server thats been running for many months now on a cloud server, about 2 weeks ago it just stopped connecting to brandmeister.
On starting it manualy I noticed an error coming back MSTCL Recieved the same as in your posting.
I have repeater freqs set in the connectors to BM and also my own Password login set as it allways has been  and was running.
The only way I could get my system back going was to image the server, start a new server with a different IP address and put the image back on the new server start it and it all worked instantly.
From this I got that  
MSTCL Recieved means the IP address has been blocked.


Doug ZL3DMH

--
Doug Gooden
troytrojan@...


Re: Unable to connect to Brandmeister using HBlink #hblink

Doug
 

I have a HBLink server thats been running for many months now on a cloud server, about 2 weeks ago it just stopped connecting to brandmeister.
On starting it manualy I noticed an error coming back MSTCL Recieved the same as in your posting.
I have repeater freqs set in the connectors to BM and also my own Password login set as it allways has been  and was running.
The only way I could get my system back going was to image the server, start a new server with a different IP address and put the image back on the new server start it and it all worked instantly.
From this I got that  
MSTCL Recieved means the IP address has been blocked.


Doug ZL3DMH


Re: New Install of DVSwich

Steve N4IRS
 
Edited

I can't find a problem. Fresh Debian 10 64 bit.

apt update
apt upgrade
reboot

I won't paste results too much text. No errors

wget http://dvswitch.org/buster
chmod +x buster
./buster

I won't paste results too much text. No errors

At this point I installed DVSwitch Server then AllStar
I won't paste results too much text. No errors

reboot.

szingman@nuc:~$ ssh szingman@...
szingman@...'s password:
Linux debian 4.19.0-14-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30) x86_64

root@debian:~# cat /var/log/netcheck
Starting md380-emu: [01:42:52.457]
Starting NetCheck in systemd: [01:42:54.242]

NetCheck starting: [01:42:54.306]

wget returned: No problems occurred (0) [01:42:55.070]

Starting Analog_Bridge: [01:42:55.076]
Starting YSFGateway: [01:42:55.078]
Starting ircDDBGateway: [01:42:55.081]
NetCheck: Success [01:42:55.082]
Starting MMDVM_Bridge: [01:42:55.092]
Starting NXDNGateway: [01:42:55.093]
Starting P25Gateway: [01:42:55.102]
Starting YSFParrot: [01:42:55.108]
Starting Web Proxy: [01:42:55.114]
Starting P25Parrot: [01:42:55.124]
Starting NXDNParrot: [01:42:55.129]

root@debian:~# lsmod | grep dahdi
dahdi_dummy            16384  0
dahdi                 245760  27 dahdi_dummy
crc_ccitt              16384  1 dahdi

root@debian:~# asterisk -r

AllStarLink Asterisk Version 1.01 2/13/2018 GIT Version 004b9dd
Copyright (C) 1999 - 2018 Digium, Inc. Jim Dixon, AllStarLink Inc. and others.
Created by Mark Spencer <markster@...>
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type 'core show license' for details.
=========================================================================
Connected to Asterisk GIT Version 004b9dd currently running on debian (pid = 420)
debian*CLI> exit

root@debian:~# /opt/MMDVM_Bridge/dvswitch.sh version all
dvswitch.sh version 1.6.0
Analog_Bridge version 1.6.0
MMDVM_Bridge version 20201129_V1.6.2 git #89f8998
P25Gateway version 20200824
NXDNGateway version 20200824
YSFGateway version 20200908

root@debian:~# ps ax
  PID TTY      STAT   TIME COMMAND
  375 ?        Ssl    0:01 /usr/bin/qemu-arm-static /opt/md380-emu/md380-emu -S 2470
  383 ?        Sl     0:00 /usr/bin/monit -c /etc/monit/monitrc
  417 ?        Ss     0:00 /bin/bash /usr/local/bin/rc.updatenodelist &
  420 ?        Ssl    0:01 /usr/sbin/asterisk -g -f -C /etc/asterisk/asterisk.conf
  509 ?        Ssl    0:01 /usr/bin/ircddbgatewayd -logdir:/var/log/ircddbgateway
  510 ?        Ss     0:00 /opt/YSFGateway/YSFGateway /opt/YSFGateway/YSFGateway.ini
  511 ?        Ssl    0:00 /opt/Analog_Bridge/Analog_Bridge /opt/Analog_Bridge/Analog_Bridge.ini
  513 ?        Ssl    0:02 /opt/MMDVM_Bridge/MMDVM_Bridge /opt/MMDVM_Bridge/MMDVM_Bridge.ini
  515 ?        Ssl    0:00 /opt/NXDNGateway/NXDNGateway /opt/NXDNGateway/NXDNGateway.ini
  517 ?        Ssl    0:00 /opt/P25Gateway/P25Gateway /opt/P25Gateway/P25Gateway.ini
  518 ?        Ss     0:00 /opt/YSFParrot/YSFParrot 42012
  521 ?        Ssl    0:01 /usr/bin/node /opt/Web_Proxy/proxy.js 8080 2222
  522 ?        Ss     0:00 /opt/P25Parrot/P25Parrot 42011
  525 ?        Ss     0:00 /opt/NXDNParrot/NXDNParrot 42021
  533 ?        Ss     0:00 /usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf
root@debian:~#

root@debian:~# host-info 
 
Host information script v .1.6.0 10/27/2020
 
=== Intel-AMD ===
Node name = debian
Host name = debian
Machine = x86_64
CPU model = Intel(R) Xeon(R) CPU E5645 @ 2.40GHz
Operating system = GNU/Linux
ID = Debian
Release = 10
Codename = buster
Debian package architecture = amd64
Kernel name = Linux
Kernel release = 4.19.0-14-amd64
Kernel version = #1 SMP Debian 4.19.171-2 (2021-01-30)
Data width (bits) = 64
Memory = 180 MB used of 986 MB (18.26%)
Disk = 2 GB used of 62 GB (4%)
CPU load = 0.06
IP Address = Internal: 192.168.160.172 MAC Address: 00:50:56:9c:3d:1c
 
I did not get any errors during install(s)
All programs installed and running.

Steve N4IRS


On 2/11/21 12:11 AM, Mike KB8JNM wrote:
Steve, you might want to revisit this method.
While it did work, I just tried a fresh install today and there were debian buster updates and now broken dependent packages.
I did not have time to sort it out. But it's there. I will revisit in a few days.


Re: New Install of DVSwich

Mike KB8JNM
 

Steve, you might want to revisit this method.
While it did work, I just tried a fresh install today and there were debian buster updates and now broken dependent packages.
I did not have time to sort it out. But it's there. I will revisit in a few days.


Re: banned DVSwitch

Wolfgang DK5UF
 

Thank you very much Steve for the hint. That was exactly my problem.
After changing the Frequencies to Simplex Frequencies I am reaccepted
by Brandmeister and dvswitch is working as perfect as it was before.
Many thanks for a great job you are doing and  I'm waiting impatiently for
the browser interface.
vy 73s and 55s from Wolfgang, DK%UF


Re: Setup of a Bridge YSF to DMR - Anyone out there who can solve this mystery ? #mmdvm_bridge

Uli
 

Thanks Steve,
I did and it works again

Uli


Re: Brandmeister block DVSwitch

Pierre Martel
 

100% and BTW did I say thanks for all the great jobs you all doing here? if not, big thanks !!!!


Le mar. 9 févr. 2021 à 21:10, Steve N4IRS <szingman@...> a écrit :
True, I don't like everything I have to do, but I sure do what it takes to help extend things. I think this thread has run it's course.

73, Steve N4IRS

On 2/9/21 9:07 PM, Pierre Martel wrote:
There is a saying, if you don't do politics, politics will do with you. :-) Catch 22... We are doomed to have some politics in our life.





Le mar. 9 févr. 2021 à 20:53, Steve N4IRS <szingman@...> a écrit :
I don't see where the multilink come into play. As far as frequency, unless it's a hotspot, the frequencies are not used. The only reason the frequencies need to be adjusted is that BM is leveraging the frequencies selected to protect from a misconfigured hotspot. We are providing the data the protocol needs in the format it expects it in. There is nothing fake about it. I don't like the politics either but I deal in the real world where politics play a part. 

On 2/9/21 8:46 PM, Pierre Martel wrote:
Steve, 
I am with you on this, but the BM team see the MMDVM protocol as a repeater or hotspot client, not as a multilink system. 
And when you put a frequency that is not really in use, for them you are faking it. 

I also don't like all this politics. but I am just a small admin of a small server.. 




Le mar. 9 févr. 2021 à 17:52, Steve N4IRS <szingman@...> a écrit :
It is not a FAKE repeater connection. It is a MMDVM connection. I've made my feelings clear on the subject and as I've said, we will be supporting ODMRTP in the near future for single user configurations. For multi-user bridges we will continue as we are. If someone needs to add a instance of HB3 between MB and BM, so be it. I will post this again.

If you are connecting to BM, make sure your RX and TX frequency are set to a single frequency.

This is the default:
[Info]
RXFrequency=222340000
TXFrequency=224940000

Change it to:
[Info]
RXFrequency=224940000
TXFrequency=224940000

Steve N4IRS

On 2/9/21 5:11 PM, Pierre Martel wrote:
https://wiki.brandmeister.network/index.php/Open_DMR_Terminal_Protocol

But still if you ask for an open bridge link you will have it. 

Is that so complicated? Unless you are doing something that is not wanted by the BM group, why try to hide behind a fake repeater connection?

I am doing a link to Brandmeister Canada to Allstarlink and Hamshack Hotline right now, I will follow the rules and on HH I asked for an HHX link (experimental) on Allstarlink they don't have rules to prevent linking to other networks that I know of, So I only requested a Node number and properly identified it. And on Brandmeister I talked to the admin on the Canadian server and he agreed to my project.  Took a whole 30 minute total to deal with this if all the action was put back to back. 

Not a lot of red tape imho. 

If there are rules like that it is because some users don't know what they are doing and create loops between networks. And that causes problems to the stability of the nets. BM is only protecting the networks they worked hard to put in place. 


Pierre
VE2PF



Le mar. 9 févr. 2021 à 16:05, R. H. <ruediger.h@...> a écrit :
Sorry ... little Mistake ... open terminal protocol is that was Brandmeister want

Holen Sie sich Outlook für Android





Re: Brandmeister block DVSwitch

Steve N4IRS
 

True, I don't like everything I have to do, but I sure do what it takes to help extend things. I think this thread has run it's course.

73, Steve N4IRS

On 2/9/21 9:07 PM, Pierre Martel wrote:
There is a saying, if you don't do politics, politics will do with you. :-) Catch 22... We are doomed to have some politics in our life.





Le mar. 9 févr. 2021 à 20:53, Steve N4IRS <szingman@...> a écrit :
I don't see where the multilink come into play. As far as frequency, unless it's a hotspot, the frequencies are not used. The only reason the frequencies need to be adjusted is that BM is leveraging the frequencies selected to protect from a misconfigured hotspot. We are providing the data the protocol needs in the format it expects it in. There is nothing fake about it. I don't like the politics either but I deal in the real world where politics play a part. 

On 2/9/21 8:46 PM, Pierre Martel wrote:
Steve, 
I am with you on this, but the BM team see the MMDVM protocol as a repeater or hotspot client, not as a multilink system. 
And when you put a frequency that is not really in use, for them you are faking it. 

I also don't like all this politics. but I am just a small admin of a small server.. 




Le mar. 9 févr. 2021 à 17:52, Steve N4IRS <szingman@...> a écrit :
It is not a FAKE repeater connection. It is a MMDVM connection. I've made my feelings clear on the subject and as I've said, we will be supporting ODMRTP in the near future for single user configurations. For multi-user bridges we will continue as we are. If someone needs to add a instance of HB3 between MB and BM, so be it. I will post this again.

If you are connecting to BM, make sure your RX and TX frequency are set to a single frequency.

This is the default:
[Info]
RXFrequency=222340000
TXFrequency=224940000

Change it to:
[Info]
RXFrequency=224940000
TXFrequency=224940000

Steve N4IRS

On 2/9/21 5:11 PM, Pierre Martel wrote:
https://wiki.brandmeister.network/index.php/Open_DMR_Terminal_Protocol

But still if you ask for an open bridge link you will have it. 

Is that so complicated? Unless you are doing something that is not wanted by the BM group, why try to hide behind a fake repeater connection?

I am doing a link to Brandmeister Canada to Allstarlink and Hamshack Hotline right now, I will follow the rules and on HH I asked for an HHX link (experimental) on Allstarlink they don't have rules to prevent linking to other networks that I know of, So I only requested a Node number and properly identified it. And on Brandmeister I talked to the admin on the Canadian server and he agreed to my project.  Took a whole 30 minute total to deal with this if all the action was put back to back. 

Not a lot of red tape imho. 

If there are rules like that it is because some users don't know what they are doing and create loops between networks. And that causes problems to the stability of the nets. BM is only protecting the networks they worked hard to put in place. 


Pierre
VE2PF



Le mar. 9 févr. 2021 à 16:05, R. H. <ruediger.h@...> a écrit :
Sorry ... little Mistake ... open terminal protocol is that was Brandmeister want

Holen Sie sich Outlook für Android





Re: Brandmeister block DVSwitch

Pierre Martel
 

There is a saying, if you don't do politics, politics will do with you. :-) Catch 22... We are doomed to have some politics in our life.





Le mar. 9 févr. 2021 à 20:53, Steve N4IRS <szingman@...> a écrit :
I don't see where the multilink come into play. As far as frequency, unless it's a hotspot, the frequencies are not used. The only reason the frequencies need to be adjusted is that BM is leveraging the frequencies selected to protect from a misconfigured hotspot. We are providing the data the protocol needs in the format it expects it in. There is nothing fake about it. I don't like the politics either but I deal in the real world where politics play a part. 

On 2/9/21 8:46 PM, Pierre Martel wrote:
Steve, 
I am with you on this, but the BM team see the MMDVM protocol as a repeater or hotspot client, not as a multilink system. 
And when you put a frequency that is not really in use, for them you are faking it. 

I also don't like all this politics. but I am just a small admin of a small server.. 




Le mar. 9 févr. 2021 à 17:52, Steve N4IRS <szingman@...> a écrit :
It is not a FAKE repeater connection. It is a MMDVM connection. I've made my feelings clear on the subject and as I've said, we will be supporting ODMRTP in the near future for single user configurations. For multi-user bridges we will continue as we are. If someone needs to add a instance of HB3 between MB and BM, so be it. I will post this again.

If you are connecting to BM, make sure your RX and TX frequency are set to a single frequency.

This is the default:
[Info]
RXFrequency=222340000
TXFrequency=224940000

Change it to:
[Info]
RXFrequency=224940000
TXFrequency=224940000

Steve N4IRS

On 2/9/21 5:11 PM, Pierre Martel wrote:
https://wiki.brandmeister.network/index.php/Open_DMR_Terminal_Protocol

But still if you ask for an open bridge link you will have it. 

Is that so complicated? Unless you are doing something that is not wanted by the BM group, why try to hide behind a fake repeater connection?

I am doing a link to Brandmeister Canada to Allstarlink and Hamshack Hotline right now, I will follow the rules and on HH I asked for an HHX link (experimental) on Allstarlink they don't have rules to prevent linking to other networks that I know of, So I only requested a Node number and properly identified it. And on Brandmeister I talked to the admin on the Canadian server and he agreed to my project.  Took a whole 30 minute total to deal with this if all the action was put back to back. 

Not a lot of red tape imho. 

If there are rules like that it is because some users don't know what they are doing and create loops between networks. And that causes problems to the stability of the nets. BM is only protecting the networks they worked hard to put in place. 


Pierre
VE2PF



Le mar. 9 févr. 2021 à 16:05, R. H. <ruediger.h@...> a écrit :
Sorry ... little Mistake ... open terminal protocol is that was Brandmeister want

Holen Sie sich Outlook für Android




Re: Brandmeister block DVSwitch

Steve N4IRS
 

I don't see where the multilink come into play. As far as frequency, unless it's a hotspot, the frequencies are not used. The only reason the frequencies need to be adjusted is that BM is leveraging the frequencies selected to protect from a misconfigured hotspot. We are providing the data the protocol needs in the format it expects it in. There is nothing fake about it. I don't like the politics either but I deal in the real world where politics play a part. 

On 2/9/21 8:46 PM, Pierre Martel wrote:
Steve, 
I am with you on this, but the BM team see the MMDVM protocol as a repeater or hotspot client, not as a multilink system. 
And when you put a frequency that is not really in use, for them you are faking it. 

I also don't like all this politics. but I am just a small admin of a small server.. 




Le mar. 9 févr. 2021 à 17:52, Steve N4IRS <szingman@...> a écrit :
It is not a FAKE repeater connection. It is a MMDVM connection. I've made my feelings clear on the subject and as I've said, we will be supporting ODMRTP in the near future for single user configurations. For multi-user bridges we will continue as we are. If someone needs to add a instance of HB3 between MB and BM, so be it. I will post this again.

If you are connecting to BM, make sure your RX and TX frequency are set to a single frequency.

This is the default:
[Info]
RXFrequency=222340000
TXFrequency=224940000

Change it to:
[Info]
RXFrequency=224940000
TXFrequency=224940000

Steve N4IRS

On 2/9/21 5:11 PM, Pierre Martel wrote:
https://wiki.brandmeister.network/index.php/Open_DMR_Terminal_Protocol

But still if you ask for an open bridge link you will have it. 

Is that so complicated? Unless you are doing something that is not wanted by the BM group, why try to hide behind a fake repeater connection?

I am doing a link to Brandmeister Canada to Allstarlink and Hamshack Hotline right now, I will follow the rules and on HH I asked for an HHX link (experimental) on Allstarlink they don't have rules to prevent linking to other networks that I know of, So I only requested a Node number and properly identified it. And on Brandmeister I talked to the admin on the Canadian server and he agreed to my project.  Took a whole 30 minute total to deal with this if all the action was put back to back. 

Not a lot of red tape imho. 

If there are rules like that it is because some users don't know what they are doing and create loops between networks. And that causes problems to the stability of the nets. BM is only protecting the networks they worked hard to put in place. 


Pierre
VE2PF



Le mar. 9 févr. 2021 à 16:05, R. H. <ruediger.h@...> a écrit :
Sorry ... little Mistake ... open terminal protocol is that was Brandmeister want

Holen Sie sich Outlook für Android




Re: Brandmeister block DVSwitch

Pierre Martel
 

Thanks Jeff, 

I will be looking into this. I must have not read the right info..

Talking about our projects is always helping get them right.




Le mar. 9 févr. 2021 à 17:15, Jeff Lehman, N8ACL via groups.io <n8acl=icloud.com@groups.io> a écrit :
Well if you are linking to Hamshack Hotline, you already messed it up. 

You need to request an RF-Link extension, not an experimental extension. 

Just as a side note…..

Jeff

On Feb 9, 2021, at 5:11 PM, Pierre Martel <petem001@...> wrote:

https://wiki.brandmeister.network/index.php/Open_DMR_Terminal_Protocol

But still if you ask for an open bridge link you will have it. 

Is that so complicated? Unless you are doing something that is not wanted by the BM group, why try to hide behind a fake repeater connection?

I am doing a link to Brandmeister Canada to Allstarlink and Hamshack Hotline right now, I will follow the rules and on HH I asked for an HHX link (experimental) on Allstarlink they don't have rules to prevent linking to other networks that I know of, So I only requested a Node number and properly identified it. And on Brandmeister I talked to the admin on the Canadian server and he agreed to my project.  Took a whole 30 minute total to deal with this if all the action was put back to back. 

Not a lot of red tape imho. 

If there are rules like that it is because some users don't know what they are doing and create loops between networks. And that causes problems to the stability of the nets. BM is only protecting the networks they worked hard to put in place. 


Pierre
VE2PF



Le mar. 9 févr. 2021 à 16:05, R. H. <ruediger.h@...> a écrit :
Sorry ... little Mistake ... open terminal protocol is that was Brandmeister want

Holen Sie sich Outlook für Android





Re: Brandmeister block DVSwitch

Pierre Martel
 

Steve, 
I am with you on this, but the BM team see the MMDVM protocol as a repeater or hotspot client, not as a multilink system. 
And when you put a frequency that is not really in use, for them you are faking it. 

I also don't like all this politics. but I am just a small admin of a small server.. 




Le mar. 9 févr. 2021 à 17:52, Steve N4IRS <szingman@...> a écrit :
It is not a FAKE repeater connection. It is a MMDVM connection. I've made my feelings clear on the subject and as I've said, we will be supporting ODMRTP in the near future for single user configurations. For multi-user bridges we will continue as we are. If someone needs to add a instance of HB3 between MB and BM, so be it. I will post this again.

If you are connecting to BM, make sure your RX and TX frequency are set to a single frequency.

This is the default:
[Info]
RXFrequency=222340000
TXFrequency=224940000

Change it to:
[Info]
RXFrequency=224940000
TXFrequency=224940000

Steve N4IRS

On 2/9/21 5:11 PM, Pierre Martel wrote:
https://wiki.brandmeister.network/index.php/Open_DMR_Terminal_Protocol

But still if you ask for an open bridge link you will have it. 

Is that so complicated? Unless you are doing something that is not wanted by the BM group, why try to hide behind a fake repeater connection?

I am doing a link to Brandmeister Canada to Allstarlink and Hamshack Hotline right now, I will follow the rules and on HH I asked for an HHX link (experimental) on Allstarlink they don't have rules to prevent linking to other networks that I know of, So I only requested a Node number and properly identified it. And on Brandmeister I talked to the admin on the Canadian server and he agreed to my project.  Took a whole 30 minute total to deal with this if all the action was put back to back. 

Not a lot of red tape imho. 

If there are rules like that it is because some users don't know what they are doing and create loops between networks. And that causes problems to the stability of the nets. BM is only protecting the networks they worked hard to put in place. 


Pierre
VE2PF



Le mar. 9 févr. 2021 à 16:05, R. H. <ruediger.h@...> a écrit :
Sorry ... little Mistake ... open terminal protocol is that was Brandmeister want

Holen Sie sich Outlook für Android



Re: Brandmeister block DVSwitch

Steve N4IRS
 

It is not a FAKE repeater connection. It is a MMDVM connection. I've made my feelings clear on the subject and as I've said, we will be supporting ODMRTP in the near future for single user configurations. For multi-user bridges we will continue as we are. If someone needs to add a instance of HB3 between MB and BM, so be it. I will post this again.

If you are connecting to BM, make sure your RX and TX frequency are set to a single frequency.

This is the default:
[Info]
RXFrequency=222340000
TXFrequency=224940000

Change it to:
[Info]
RXFrequency=224940000
TXFrequency=224940000

Steve N4IRS

On 2/9/21 5:11 PM, Pierre Martel wrote:
https://wiki.brandmeister.network/index.php/Open_DMR_Terminal_Protocol

But still if you ask for an open bridge link you will have it. 

Is that so complicated? Unless you are doing something that is not wanted by the BM group, why try to hide behind a fake repeater connection?

I am doing a link to Brandmeister Canada to Allstarlink and Hamshack Hotline right now, I will follow the rules and on HH I asked for an HHX link (experimental) on Allstarlink they don't have rules to prevent linking to other networks that I know of, So I only requested a Node number and properly identified it. And on Brandmeister I talked to the admin on the Canadian server and he agreed to my project.  Took a whole 30 minute total to deal with this if all the action was put back to back. 

Not a lot of red tape imho. 

If there are rules like that it is because some users don't know what they are doing and create loops between networks. And that causes problems to the stability of the nets. BM is only protecting the networks they worked hard to put in place. 


Pierre
VE2PF



Le mar. 9 févr. 2021 à 16:05, R. H. <ruediger.h@...> a écrit :
Sorry ... little Mistake ... open terminal protocol is that was Brandmeister want

Holen Sie sich Outlook für Android



Re: Brandmeister block DVSwitch

Jeff Lehman, N8ACL
 

Well if you are linking to Hamshack Hotline, you already messed it up. 

You need to request an RF-Link extension, not an experimental extension. 

Just as a side note…..

Jeff

On Feb 9, 2021, at 5:11 PM, Pierre Martel <petem001@...> wrote:

https://wiki.brandmeister.network/index.php/Open_DMR_Terminal_Protocol

But still if you ask for an open bridge link you will have it. 

Is that so complicated? Unless you are doing something that is not wanted by the BM group, why try to hide behind a fake repeater connection?

I am doing a link to Brandmeister Canada to Allstarlink and Hamshack Hotline right now, I will follow the rules and on HH I asked for an HHX link (experimental) on Allstarlink they don't have rules to prevent linking to other networks that I know of, So I only requested a Node number and properly identified it. And on Brandmeister I talked to the admin on the Canadian server and he agreed to my project.  Took a whole 30 minute total to deal with this if all the action was put back to back. 

Not a lot of red tape imho. 

If there are rules like that it is because some users don't know what they are doing and create loops between networks. And that causes problems to the stability of the nets. BM is only protecting the networks they worked hard to put in place. 


Pierre
VE2PF



Le mar. 9 févr. 2021 à 16:05, R. H. <ruediger.h@...> a écrit :
Sorry ... little Mistake ... open terminal protocol is that was Brandmeister want

Holen Sie sich Outlook für Android





Re: Brandmeister block DVSwitch

Pierre Martel
 

https://wiki.brandmeister.network/index.php/Open_DMR_Terminal_Protocol

But still if you ask for an open bridge link you will have it. 

Is that so complicated? Unless you are doing something that is not wanted by the BM group, why try to hide behind a fake repeater connection?

I am doing a link to Brandmeister Canada to Allstarlink and Hamshack Hotline right now, I will follow the rules and on HH I asked for an HHX link (experimental) on Allstarlink they don't have rules to prevent linking to other networks that I know of, So I only requested a Node number and properly identified it. And on Brandmeister I talked to the admin on the Canadian server and he agreed to my project.  Took a whole 30 minute total to deal with this if all the action was put back to back. 

Not a lot of red tape imho. 

If there are rules like that it is because some users don't know what they are doing and create loops between networks. And that causes problems to the stability of the nets. BM is only protecting the networks they worked hard to put in place. 


Pierre
VE2PF



Le mar. 9 févr. 2021 à 16:05, R. H. <ruediger.h@...> a écrit :
Sorry ... little Mistake ... open terminal protocol is that was Brandmeister want

Holen Sie sich Outlook für Android


Re: banned DVSwitch

Randy AA6RH
 

On Tue, Feb 9, 2021 at 11:43 AM, Steve N4IRS wrote:
There are a LOT of politics in the discussion of OpenBridge vs HB (MMDVM) I can tell you when we worked with Cort on the Python implementation, it was envisioned as a mult-TG bridge solution. BM has always had a problem with HB. I really don't see a issue with a single reflector mode (P25, NXDN, YSF, ASL) using HB to connect to a Master. It is BM's sandbox and that's the way they want it. As of today, DVSwitch does not support OB nor the BM preferred connection from a Mobile device. In the case of Mobile that may be changing as we complete Simple Terminal Feature Update.
And to amplify what Steve says here, we've been dealing with this for a lot longer over in HBLink (seeing as that was mostly Cort's work that I'm looking after now).

BM can run their network the way they want, and they've been very vocal about how they want connections into their network to function. The fact that they are blacklisting certain peer types is no surprise to me whatsoever.

The good news is that there's no reason really to panic (other than the fact that it will probably take you more than a day to sort this out). If you're interested in continuing to use BM's network, open a support ticket to set up a bridge and specify that it will be OpenBridge.

I get the feeling that they are funneling everyone that direction for a reason, but I don't know exactly what that reason is. What I will say is that once you do get OpenBridge working with them, your connection will probably perform better overall. I'm sure that there will be someone who will contradict that statement, so I will also say that YMMV and to always be on the lookout for a backup plan to the backup plan.

I'll be over the HBLink forum if you need me.

--R 
--
Randy Hall AA6RH (not K7AGE, quit asking) 😁


Re: Brandmeister block DVSwitch

R. H.
 

Sorry ... little Mistake ... open terminal protocol is that was Brandmeister want

Holen Sie sich Outlook für Android


Re: banned DVSwitch

Peter M0NWI
 

Agreed Steve, but I suppose I'm coming from a network to network solution thinking.
MMDVM protocol works well for a more personal to TG solution.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: 09 February 2021 19:43
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] banned DVSwitch
 
There are a LOT of politics in the discussion of OpenBridge vs HB (MMDVM) I can tell you when we worked with Cort on the Python implementation, it was envisioned as a mult-TG bridge solution. BM has always had a problem with HB. I really don't see a issue with a single reflector mode (P25, NXDN, YSF, ASL) using HB to connect to a Master. It is BM's sandbox and that's the way they want it. As of today, DVSwitch does not support OB nor the BM preferred connection from a Mobile device. In the case of Mobile that may be changing as we complete Simple Terminal Feature Update.

For OpenBridge, I suggest people wanting to bridge to BM start reading up on OB. Unlike HB, OB requires you coordinate with the Master to setup your connection. If that Master goes down you can not just move to a different Master. Before I start getting a bunch of flack about why move to OB, I'll say it again, it's BM's sandbox.

Steve N4IRS 

On 2/9/2021 2:29 PM, Peter M0NWI wrote:
Have a Google, it's the network to network protocol, which you can pass concurrent channels of TGs down then split them out using the confbridge rules at you network end.  It's quite efficient and the right way to link. 


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of G4WXN@... <G4WXN@...>
Sent: 09 February 2021 19:18
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] banned DVSwitch
 
What's openbridge?

--
Derek

G4WXN

1121 - 1140 of 9589