Yes, this has been in my list for long time.

#dvs

See your BM status here: http://3102.repeater.net/status/terminal.htm

I would consult: https://docs.docker.com/config/containers/container-networking/ https://docs.docker.com/network/iptables/

All DVSwitch components act as both client and server. On the client side they make outbound connections and docker is just fine NATing the reply from the server. This is why you can connect to FreeDM

Are you using BM? Statewide talk group? use STFU.

Exit the beta

If you are a terminal like DVSM, hUC then use STFU. If you are trying to bridge to a statewide talk group with MB, stop.

Dstar requires callsigns. Your metadata did not resolve to a call. Bad lookup? Empty database?

The error message is returned by your Allstar Node when issuing a RptStatus. Most likely it is because you have misconfigured your node number in Analog_Reflector.json or manager.conf on the Allstar s

The dashboard does log file scraping and if I remember, the solution is to set your STFU log to replace the MMDVM log. I could be wrong though.

Or you do the easy thing: change the file name/path in the ini file to your own custom named csv file.

Change "Screen Scale"

Yes, many routers have problems with "hairpin" routes. https://en.wikipedia.org/wiki/Hairpinning

Do not use SSID, just 7 digit DMR ID

I will look into it.

However, it IS a known issue that ircddbgateway can runaway and use 100%cpu.

This is just an informational message. The message is a result of adding a new event type to several of the modes. Please ignore it. I will fix the message in the next release.

Try this: https://dvswitch.groups.io/g/Mobile/message/969

Did you select USRP ?

So I can reproduce you issue, please tell me the OS version by running uname -a and reporting the results. All tests I have done with FF have worked, so I want to see if I broke something recently.