How do I find the new how to? I know it was posted last month. I remember seeing the post. I did a search for HOW TO and can't seem to find it. I am going to read through it and see if there is

Be sure you are not logged in on two device in the same ID #. If you have appended your ID as-per instructions in the DVswitch how-2. You may also want to go to BM and flush the

I only hear it on the Allstar side and it happens on every keyup. As soon as someone unkeys, the node drops and then keys back up again and says something. Can't figure out what that something is. It

I think what you are referring to is a message on BM side of the DMR. I don't believe it to be any error on your part or that you have control over. ...mike/kb8jnm On

i had that happen the other day, tracked it to someone sneaking in on the default ports. changed 4569 to another port number and secured my firewall better

I have my ASL to DMR server running, but have noticed that after about a day of it being on line, I get some announcement each time someone unkeys. Can't make out what she is saying. I have heard it

Rod, Are you talking about not allowing RF users to flow out over the network, see the sub_acl.py file to create a black or white list, or to stop them using the RF side totally? Sent from

Hi Rod, The MMDVM protocol doesn't contain a "Username" as such, it's password only. Do you mean you want no password at all for connecting clients, or IP authentication? Cheers

Is there a way to have an "authorized user" list in the MMDVM Server? While we offer a publicly available connection for those who are outside our area, we also have several that we use for various

Hi All, With some guidance from the DVSwitch Team I've added a new "LOOSE" option in hblink.cfg for clients. Setting "LOOSE: True" will relax some of the validation performed on packets received

In theory, yes. Not that we have tried. It would require a host that can "see" both reflectors. It would require 2 instances of MMDVM_Bridge. Steve On 06/25/2018 04:39 PM,

Can a P25Reflector be linked to another P25Reflector? Just thinking outside the box here. We have one reflector that's inside the private network and one that's directly connected to the public

To update or add P25Hosts and make them stay, the file you need to edit is /root/P25Hosts.txt. After you edit (and save) the file, run pistar-update and that makes the changes permanent. In

Mike, So D-Star -> DMR works.. For that to work we know that all of the programs involved are running. To trouble shoot the other direction, follow the data. Since the problem is DMR ->

I tried with the apt-get and since I could not resolve the issues so then I tried with the github since that previously worked a while back. The audio works from DSTAR-DMR but not the other way

Mike, Do a apt-get update and a apt-get upgrade. Please report results after retesting Analog_Bridge on Jessie 64 On 06/23/2018 10:31 AM, Mike Swiatkowski via Groups.Io wrote:

It updates the private file too? If so that SUCKS! He should NOT do that! Insert more STRONG words here! On 06/23/2018 11:13 AM, Jim K6JWN wrote:

Thanks for the info, I was successful in getting that piece added to the puzzle! Now, I just need to find a way to have Pi-Star stop updating my P25HostsLocal file every day!😊 Jim, K6JWN

And, just to be clear, you are running Analog_Bridge from the deb (apt-get update, apt-get upgrade) not from the github repo On 06/23/2018 10:31 AM, Mike Swiatkowski via Groups.Io

I'll build a Analog_Bridge on Jessie64 (again?) I thought I did already. In the mean time, if you had one way audio Analog_bridge had to be working. On 06/23/2018 10:31 AM, Mike