The local ports are already different -- BM instance local port is 62032, XLX is 62034. I have them both running in console. Traffic passes fine from BM to XLX, but as soon as anyone transmits from D-

This is XLX679 module A. FWIW: I copied the exact configuration over to a machine on my LAN, and it works there. Don't know what the difference is. I have two instances of MMDVM_Bridge running -- one

Right. I wasn't referring directly to the INI file at the time. My machine is on a VPS, so the IP of ETH0 is a public IP address. So, it looks like this. [DMR Network] Enable=1 Address=<Public_IP_Of_T

Currently, I have the address in the DMR Network stanza pointed to the XLX reflector <IP_ADDRESS:62030). I assume this is the network address you're referring to? If so, then the reflector isn't doing

Oh yes, I forgot to mention that the MMDVM_Bridge is in its own directory with different rx and tx ports in DVSwitch.ini to avoid conflict with the existing bridge.

That was actually the first configuration I tried. Same result either with the Interface IP address, or local loopback. I’ll mess with it some more later. The MMDVM_Bridge part looks easy enough once

I downloaded the latest MMDVM_Bridge earlier today. My current issue is getting MMDVM-Bridge connected to XLXD on the same machine. I'm sure I've directly connected a hotspot to the reflector before,

OK. I just tried setting up an instance of MMDVM_Bridge to point to 127.0.0.1 on port 62030 (MMDVM) using the DMRNetwork. I thought XLXD responded to that, but apparently it doesn't, as the connection

Hello: I found an old docc referring to using two instances of MMDVM_Bridge and DMRGateway to bridge DMR to XLX. Is this necessary anymore, or can we now just use two instances of MMDVM_Bridge, since

Cool, that's the piece I was missing. I think I can handle the rest. Thanks.

Hi: Let me explain what this is all about. I have ASL running on a VPS, with MMDVM_Bridge and Analog_Bridge parked on a private ASL node connected to the publicly accessible node. This public node als

So far, the new version of Analog_Bridge, connected to a remote AMBEserver, is working well. I've had it up for a few hours with a reasonable amount of cross-mode traffic, and it hasn't fallen over ye

Mike: I'll probably end up implementing another instance of ASL, but testing that once it's available is easier in the short-term. So, I'll do that, too.

Sounds reasonable. As I am moving soon, I'll set up an identical private node with a second AMBE dongle in another location, then just switch to that for the duration of downtime.

3138495, but not sure that it matters. I have it working in both directions on my VPS, where Analog_Bridge is connecting to a remote AMBE server. The problem with that setup is Analog_Bridge likes to

Hmm... That doesn't make sense to me, because then the TX and RX ports match on both MMDVM_Bridge and Analog_Bridge. TX should go to RX of the other, which is how it is by default. I did try it, which

I forgot to mention that UDP 34001 and 31100 are forwarded through my local NAT to the Pi running DVSwitch.

Hi: In moving my DVSwitch to a local Raspberry Pi 4 rather than running it on the VPS, connecting to a remote AMBEserver, I'm running into a problem. I now have audio going from DMR to USRP, but not t

Here is a full log. There are no entries when transmissions occur from either side of the bridge. I could use the IP address rather than DNS for the remote machine, but I know from experience that DNS

I have installed/configured DVSwitch on my Raspberry Pi 4 and pointed it at the local AMBEserver and remote USRP, but it seems that traffic isn't passing. Does ASL's USRP driver only listen on localho