You are correct with your design. Not sure what "address" needs to be different.. but each would require it's own node entry in your ASL config and then you would need to link those ASL nodes together

#analog_bridge

I was referring to the USRP address. One address set for each node.

#analog_bridge

Maybe it's just a matter of what you and I are calling thing? I read "address" as an IP Address which does not need to be unique at all. All that needs to happen is each mode has an ASL node which lis

#analog_bridge

Port address, not IP. As same with each P25 NXDN DMR etc service instance that is on the same server. A separate PORT ADDRESS will be needed for each instance of a service running on the same server.

#analog_bridge

If only it were so. In the diagram below (if I understand it) you have NXDN, DMR and YSFn all enabled. That's fine but NXDN is going to need to point it's TX and RX UDP ports at another mode (or Analo

#analog_bridge

You're typing "port address" when you mean port number. I think that's why you are confusing JJ et al. Assuming they're all running on the same host, they will all use the localhost IP ADDRESS (127.0.

#analog_bridge

Having a hard time locating & install & setting up MMDVM_Bridge, Analog_bridge to do allstarlink, d-star, dmr, p25 linking but haven't seen any for Debian. I am at a loss to completing the 2-year proj

#mmdvm_bridge #hblink #analog_bridge

<https://dvswitch.groups.io/g/allstarlink/files/ASL%20to%20DMR%20Bridge.pdf>

#mmdvm_bridge #hblink #analog_bridge

Steve, is this also help with the install and setup of the d-star side of this?

#mmdvm_bridge #hblink #analog_bridge

also, the install will be on a separate server. the asl on a raspberry pie and the others are on a Debian system. so how would i make this work?

#mmdvm_bridge #hblink #analog_bridge

Are you linking this to a BM TG? you can use MMDVM_Bridge to link this to the BM with your id+2 and then map it to the TG in selfcare. do the same for ASL link on your raspberry pi. Alec N1AJW

#mmdvm_bridge #hblink #analog_bridge

Alec, Trying to do a new install & setup between my Allstarlink, D-star, P25 to start with then possibly a bridge to Fusion & BM TG once I get the others working good. As I stated previously, I have t

#mmdvm_bridge #hblink #analog_bridge

I would suggest you follow the howto on one machine to learn before you attempt multi-hosts. Setup DMR as the howto shows before attempting other modes. Steve N4IRS

#mmdvm_bridge #hblink #analog_bridge

Steve, I understand, but as ARM os (AllstarLink Node) is difficult to install software on. I am running my D-Star & P25 Reflectors on my Debian machine. Currently, I don't use DMR and don't care for i

#mmdvm_bridge #hblink #analog_bridge

There is no big secret. Nobody is hiding anything. Why do you think this forum exists? If you learn to setup DMR the flow will become clearer. Have you tried to follow the howto on a x86 system? I als

#mmdvm_bridge #hblink #analog_bridge

Steve, sorry for seeming rough. I'm just getting frustrated with it. Steven installed the dvswitch on my all-star node but never told me how to start the services and get it all up and running on the

#mmdvm_bridge #hblink #analog_bridge

You get this is a technical 'hobby', that we're all here to forward that hobby, Steve and Mike, with Cort too have for me anyway, given an amazing amount of time and effort, and others have stood up a

#mmdvm_bridge #hblink #analog_bridge

Peter, Thanks for the insight. But I have been Building, coding many of projects in the commercial and ham world in Linux, Mac & windows for about almost 11 years now just not a lot with the Arm OS an

#mmdvm_bridge #hblink #analog_bridge

ARM OS? You mean Linux on ARM?

#mmdvm_bridge #hblink #analog_bridge

Steve, It's hard to work with os on a pi with ARM that Hamvoip all-star uses that nothing installs like regular vers of Linux do. All most everything has to be manually installed, piece by piece. That

#mmdvm_bridge #hblink #analog_bridge