Unable to connect to Brandmeister using HBlink #hblink


David
 

Hi Steve 
it works .after i make TX/RX are different .for example TX=433800000 ,RX=433500000,it login BM success now


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


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


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@...


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


Steve N4IRS
 
Edited

I think the issue is if you are configured for repeater (dual slot) and have the transmit and receive frequency the same (simplex) BM will not allow the connect.
This is to block misconfigured duplex hotspots.

Steve N4IRS


Matthew 2E0SIP
 

Brandmeister don't allow logins from HBLink and actively drop them, at least on the masters I have tried.


David
 

Hi ve6gcd 
may i know what is that mean ? "As soon as I changed it to the repeater frequency pair in HBlink I was able to get in" ,i have same problem and i sure i set the same password between BM Self card and hblink 
thanks


ve6gcd@...
 

What really changed was the frequency requirement. As soon as I changed it to the repeater frequency pair in HBlink I was able to get in. Thanks guys 73.


ve6gcd@...
 

I already did that, changed password via Self Care and after changing the connection password I obtained the same result. Pretty sure the updated password is correct (otherwise I get an MSTNAK Received message).


@AndrewVK2HAC
 

Also i am advised that if you want to use TG91 it needs to be direct with BM and not via another server/system.


Steve N4IRS
 

Yes it is. I had forgotten to make the service start on reboot, so it was down. It is back up and will now survive a reboot.
Please understand, hblink.dvswitch.org is pretty much just a place to test your connections. There is no traffic.

Steve N4IRS

On 12/6/20 7:36 AM, G4WXN@... wrote:

I have been wondering about this, I currently login to the BM master directly, but want to use
hblink.dvswitch.org

So I get access to all the DMR networks.
Is the hblink.dvswitch.org

Password still the default?

 
Derek

G4WXN


G4WXN@...
 

I have been wondering about this, I currently login to the BM master directly, but want to use
hblink.dvswitch.org

So I get access to all the DMR networks.
Is the hblink.dvswitch.org

Password still the default?

 
Derek

G4WXN


Richard W4JXA
 

A new Brandmister requirement is a password has to be used.
Go to the Brandmister site to set it up.

W4JXA    Richard    73

On Sat, Dec 5, 2020 at 11:33 PM, ve6gcd@...
<ve6gcd@...> wrote:
Hi,

Recently I am no longer able to connect to Brandmeister. Below are the fail logs that I keep on getting:

INFO 2020-12-05 19:24:48,178 (BMR30262) Sending login request to master 158.69.203.89:62031
INFO 2020-12-05 19:24:48,250 (BMR30262) Repeater Login ACK Received with 32bit ID: 3124053916
INFO 2020-12-05 19:24:48,326 (BMR30262) Repeater Authentication Accepted
INFO 2020-12-05 19:24:48,326 (BMR30262) Repeater Configuration Sent
INFO 2020-12-05 19:24:48,398 (BMR30262) MSTCL Recieved
INFO 2020-12-05 19:24:53,176 (BMR30262) Sending login request to master 158.69.203.89:62031
INFO 2020-12-05 19:24:53,248 (BMR30262) Repeater Login ACK Received with 32bit ID: 3124053916
INFO 2020-12-05 19:24:53,321 (BMR30262) Repeater Authentication Accepted
INFO 2020-12-05 19:24:53,321 (BMR30262) Repeater Configuration Sent
INFO 2020-12-05 19:24:53,396 (BMR30262) MSTCL Recieved
INFO 2020-12-05 19:24:58,180 (BMR30262) Sending login request to master 158.69.203.89:62031
INFO 2020-12-05 19:24:58,253 (BMR30262) Repeater Login ACK Received with 32bit ID: 2539204885
INFO 2020-12-05 19:24:58,327 (BMR30262) Repeater Authentication Accepted
INFO 2020-12-05 19:24:58,328 (BMR30262) Repeater Configuration Sent
INFO 2020-12-05 19:24:58,400 (BMR30262) MSTCL Recieved
INFO 2020-12-05 19:25:03,176 (BMR30262) Sending login request to master 158.69.203.89:62031
INFO 2020-12-05 19:25:03,248 (BMR30262) Repeater Login ACK Received with 32bit ID: 2539204885
INFO 2020-12-05 19:25:03,321 (BMR30262) Repeater Authentication Accepted
INFO 2020-12-05 19:25:03,321 (BMR30262) Repeater Configuration Sent
INFO 2020-12-05 19:25:03,393 (BMR30262) MSTCL Recieved
INFO 2020-12-05 19:25:08,179 (BMR30262) Sending login request to master 158.69.203.89:62031
INFO 2020-12-05 19:25:08,251 (BMR30262) Repeater Login ACK Received with 32bit ID: 2539204885
INFO 2020-12-05 19:25:08,324 (BMR30262) Repeater Authentication Accepted
INFO 2020-12-05 19:25:08,324 (BMR30262) Repeater Configuration Sent
INFO 2020-12-05 19:25:08,397 (BMR30262) MSTCL Recieved
INFO 2020-12-05 19:25:13,176 (BMR30262) Sending login request to master 158.69.203.89:62031
INFO 2020-12-05 19:25:13,250 (BMR30262) Repeater Login ACK Received with 32bit ID: 592463761
INFO 2020-12-05 19:25:13,323 (BMR30262) Repeater Authentication Accepted
INFO 2020-12-05 19:25:13,323 (BMR30262) Repeater Configuration Sent
INFO 2020-12-05 19:25:13,396 (BMR30262) MSTCL Recieved

73,
Geoffrey VE6GCD 


ve6gcd@...
 

Hi,

Recently I am no longer able to connect to Brandmeister. Below are the fail logs that I keep on getting:

INFO 2020-12-05 19:24:48,178 (BMR30262) Sending login request to master 158.69.203.89:62031
INFO 2020-12-05 19:24:48,250 (BMR30262) Repeater Login ACK Received with 32bit ID: 3124053916
INFO 2020-12-05 19:24:48,326 (BMR30262) Repeater Authentication Accepted
INFO 2020-12-05 19:24:48,326 (BMR30262) Repeater Configuration Sent
INFO 2020-12-05 19:24:48,398 (BMR30262) MSTCL Recieved
INFO 2020-12-05 19:24:53,176 (BMR30262) Sending login request to master 158.69.203.89:62031
INFO 2020-12-05 19:24:53,248 (BMR30262) Repeater Login ACK Received with 32bit ID: 3124053916
INFO 2020-12-05 19:24:53,321 (BMR30262) Repeater Authentication Accepted
INFO 2020-12-05 19:24:53,321 (BMR30262) Repeater Configuration Sent
INFO 2020-12-05 19:24:53,396 (BMR30262) MSTCL Recieved
INFO 2020-12-05 19:24:58,180 (BMR30262) Sending login request to master 158.69.203.89:62031
INFO 2020-12-05 19:24:58,253 (BMR30262) Repeater Login ACK Received with 32bit ID: 2539204885
INFO 2020-12-05 19:24:58,327 (BMR30262) Repeater Authentication Accepted
INFO 2020-12-05 19:24:58,328 (BMR30262) Repeater Configuration Sent
INFO 2020-12-05 19:24:58,400 (BMR30262) MSTCL Recieved
INFO 2020-12-05 19:25:03,176 (BMR30262) Sending login request to master 158.69.203.89:62031
INFO 2020-12-05 19:25:03,248 (BMR30262) Repeater Login ACK Received with 32bit ID: 2539204885
INFO 2020-12-05 19:25:03,321 (BMR30262) Repeater Authentication Accepted
INFO 2020-12-05 19:25:03,321 (BMR30262) Repeater Configuration Sent
INFO 2020-12-05 19:25:03,393 (BMR30262) MSTCL Recieved
INFO 2020-12-05 19:25:08,179 (BMR30262) Sending login request to master 158.69.203.89:62031
INFO 2020-12-05 19:25:08,251 (BMR30262) Repeater Login ACK Received with 32bit ID: 2539204885
INFO 2020-12-05 19:25:08,324 (BMR30262) Repeater Authentication Accepted
INFO 2020-12-05 19:25:08,324 (BMR30262) Repeater Configuration Sent
INFO 2020-12-05 19:25:08,397 (BMR30262) MSTCL Recieved
INFO 2020-12-05 19:25:13,176 (BMR30262) Sending login request to master 158.69.203.89:62031
INFO 2020-12-05 19:25:13,250 (BMR30262) Repeater Login ACK Received with 32bit ID: 592463761
INFO 2020-12-05 19:25:13,323 (BMR30262) Repeater Authentication Accepted
INFO 2020-12-05 19:25:13,323 (BMR30262) Repeater Configuration Sent
INFO 2020-12-05 19:25:13,396 (BMR30262) MSTCL Recieved

73,
Geoffrey VE6GCD