开云体育

I just added an IC-9700 to the shack and am getting familiar with it.? I currently have ircddbgateway running on a Raspberry Pi which services both a DVAP (running on the same host) as well as an MMDVM/Pi-Star on a different host.? So there is an A module and a B module.

Adding the IC-9700 Terminal Mode to my network breaks things things becuase both the IC-9700 and ircddbgateway want port 40000 forwarded to themselves.? Bad news.? But what if I could have the IC-9700 also be a client of the single ircddbgateway?? Not today, anyway, because ircddbgateway doesn't talk Icom Terminal Mode.

So enter QnetGateway.? Can the IC-9700 be a client of QnetGateway over the ethernet connection?? If that works, then can QnetGateway also support other DVAP/MMDVM clients via IP at the same time?? The ultimate goal for me would be a gateway that can handle my DVAP, an MMDVM client, and a Terminal Mode Client over ethernet, all at the same time.

So, what capabilities exist today and can you forsee that QnetGateway might eventually get me where I want to go?

Thanks and 73,

Dan Srebnick
K2IE

Wow, that's one expensive Terminal Mode device!

First of all, both Jonathan and I support Terminal and Access Point mode via the OPC-2350LU serial-to-USB cable. Of course, I think QnetGateway is a more reliable TAP client.

Reading the 9700 manual, it looks like it supports the data port for TAP modes. If you insist on using the LAN port on the 9700, I would have the same question Jonathan has when you asked him for the same development: Where's the ICOM documentation? The probable answer, ICOM doesn't have it and won't make it available anytime soon, so some reverse engineering is needed.

What now seems like a long time ago, QnetGateway gave up the ability to run different pieces of the package on different computers. All communications between the various modems, the gateway and the link program occur over Unix datagram sockets, not UDP sockets. Unix datagram sockets are file based and so the server and client have to be on the same machine. The one exception is that you should be able to run MMDVMHost on a different machine as QnetGateway, as that communication still via UDP.

Reintroducing IP communication between the gateway and modems is possible. It could be software configurable, but the administration of that begins to look too complicated for both me and QnetGateway users, and it adds code to almost every program in the QnetGateway package that most configurations won't every use. A simpler approach would be to leave QnetGateway alone and develop a simple translator application. This new application would be very much like the CQnetRelay class that would connect to Unix datagram ports at one end and to a UDP (or even better, a TCP) LAN or WAN port at the other end.

Thanks for your thoughts Tom.

So if there was a translator that could take the G3 routing calls that go over the LAN connection and turn them into something that looks like it came from mmdvmhost (or a dvap if that is easier/better), it could then talk to either ircddbgateway or QnetGateway.? That works for me.

Sorry Dan, we're on completely different tracks...

You should be able to use a digital-to-USB cable which essentially turns your 9700 into either the equivalent of a DVDongle (Terminal Mode) or a high-powered hot-spot (Access Point Mode) without having to deal with the issues of handling G3 routing on you LAN that is hard-wired to UDP port 40000.

It's because of this hard-wiring that I really have no interest in reverse engineering G3 comms, even with the example now in the current XLX software. The digital cable is a much better way to go. It talks raw DStar voice stream packets, much like a DVAP or an MMDVM-compatible modem.