开云体育

Hi Tom, well done with releasing this, I'll get playing with it this week. I'll let you know how I get on! 73 Stefan MI0PYN

Hi Tom, I have a question about the gwys.txt file dowloaded from VA3UV using the get_gwy_list.sh script. Is there some way that this file could be updated at source? There are some omissions, and I'd like to check how the list is compiled. For example, DCS049 is omitted, as is GB7NY (a Multimode DV repeater in Northern Ireland for which I am the keeper). 73 Stefan MI0PYN

A new version has been merged into the master branch. This introduces a newly designed remote command, qnremote (QnetRemote) that will send any URCall into QnetGateway you want to send. There was a bug in DTMF preventing it from working and that has been fixed. For more details, see the new DTMF+REMOTE.README file. Please note that DTMF is not enabled by default, you have to install it. IMPORTANT: Several files have been renamed, so be sure to do a "make clean" and an "sudo make uninstall" before you do a "git pull"! Then you can do a "make -j<X>" and an "sudo make install". Tom N7TAE

Hi Tom, In the link section of the qn.cfg file, there is an option to set Callsigns that are permitted to link and unlink reflectors, which is a list of callsigns. Are there any plans to allow wildcards to be used here? Also, will there ever be an option to invert the list, so that specific callsigns can be barred from linking/unlinking reflectors, but all others can still carry out these operations? 73 Stefan MI0PYN

To compile and run QnetGateway on a CentOS 7 machine (such as may currently be running an Icom G3 gateway), it is necessary to do some additional steps, as the g++ version installed by default on CentOS 7 is a little too old. There is probably a cleaner way of doing this, but the below worked for me. You will need to compile the correct version of GCC from source following these instructions. All commands run as root, and note the compilation of GCC will take some time, depending on how many cores you have available: yum -y install unzip git libconfig-devel wget automake libmpc-devel mpfr-devel gmp-devel curl ftp://ftp.mirrorservice.org/sites/sourceware.org/pub/gcc/releases/gcc-4.9.2/gcc-4.9.2.tar.bz2 -O tar xvfj gcc-4.9.2.tar.bz2 cd gcc-4.9.2 ./configure --disable-multilib --enable-languages=c,c++ make -j make install * Make sure /usr/local/bin is in the system path. cp /usr/local/lib64/libstdc++.so.6.0.20 /lib64/ rm -f /lib64/libstdc++.so.6 ln -s /lib64/libstdc++.so.6.0.20 /lib64/libstdc++.so.6 Then follow the normal compile and install instructions. The above was done on a server running in Openstack, so I was not able to verify full operation, but I hope to be able to do this on an Icom G3 server very soon. [root@qnetgateway-test ~]# systemctl status qngateway.service ● qngateway.service - QnetGateway Loaded: loaded (/usr/lib/systemd/system/qngateway.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2018-04-27 09:16:56 UTC; 11min ago Main PID: 1286 (qngateway) CGroup: /system.slice/qngateway.service └─1286 /usr/local/bin/qngateway /usr/local/etc/qn.cfg Apr 27 09:17:11 qnetgateway-test.localdomain qngateway[1286]: g2=4, srv=5, MAX+1=6 Apr 27 09:17:11 qnetgateway-test.localdomain qngateway[1286]: APRS beacon thread started Apr 27 09:17:11 qnetgateway-test.localdomain qngateway[1286]: get_irc_data thread started Apr 27 09:17:11 qnetgateway-test.localdomain qngateway[1286]: Inactivity from local rptr band 2, removing stream id 3fa0 Apr 27 09:17:11 qnetgateway-test.localdomain qngateway[1286]: Trying to connect to APRS... Apr 27 09:17:11 qnetgateway-test.localdomain qngateway[1286]: Waiting for up to 15 seconds for APRS_HOST Apr 27 09:17:12 qnetgateway-test.localdomain qngateway[1286]: IRCDDBApp: state=3 tableID=0 Apr 27 09:17:12 qnetgateway-test.localdomain qngateway[1286]: Connected to APRS rotate.aprs.net:14580 Apr 27 09:17:15 qnetgateway-test.localdomain qngateway[1286]: IRCDDBApp: state=6 initialization completed Apr 27 09:18:01 qnetgateway-test.localdomain qngateway[1286]: irc status=7, probable connect... [root@qnetgateway-test ~]# It would be awesome if someone else were able to test this too in case I've missed something. The plan is to replace the Icom gateway software for the repeater in question, but still keep the callsign registration part. Originally we'd planned to put ircDDBGateway on there, but I think this will work better. 73, Stefan MI0PYN

A new release of QnetGateway has been merged into the master branch. As before, I have renamed some source code, so it's safest to do a "make clean" and "make uninstall" before you do a "git pull". This new release has replaced QnetLinkAudioTest with QnetVoice (executable "qnvoice"). QnetVoice pulls most parameters it need from the qn.cfg file. See the new DTMF+REMOTE+VOICE.README for more info about QnetVoice. Another new feature is a new link config variable called "no_link_unlink" which is a blacklist for linking and unlinking. If the blacklist is defined, "link_unlink" will NOT be read, even if "no_link_unlink" is defined, but empty. 73 Tom N7TAE

Hi Tom, Is there a block diagram which shows what each service does and how they connect to each other, and using what ports. That would be a useful addition to the docs. 73, Stefan MI0PYN

I don't know if anybody noticed, but we now have a wiki. Sorry, but it reads more like a marketing brochure than a wiki, and I will try to improve this when I get some more time to work on it. Tom N7TAE

Hi Tom, You're probably starting to get sick of my messages, but I was wondering whether you were aware of the differences and/or similarities of the packets an Icom Repeater controller forwards to the gateway to those an MMDVM repeater/hotspot would send? I am trying to work out whether QnetGateway would require qnrelay if it were to be run as the gateway software for an Icom D-Star repeater's dsgwd. Any hints would be helpful :-) 73, Stefan MI0PYN

Is there any interest in me sharing an extremely simple web page Python script which displays the node callsign, frequency, IP address and linked reflector? It could be bundled as part of the installer using a PR against the main repo, it only uses Python3 and modules in the stdlib and provides a visual reminder of what reflector the hotspot is connected to. I have plans to expand it to include some additional stuff, but I wrote it just to display in a web page for when I'm only half paying attention to the radio at work. Kindest regards, Stefan MI0PYN

I found some old legacy code in QnetGateway that was preventing routing to some group modules. This has been fixed and is available in the github repository. Tom N7TAE

I have updated the QnetGateway Makefile in two important areas. I have added new targets, "mmdvm", "dvap", and "dvrptr" so that if you are building an MMDVMHost based system, type "make mmdvm" to compile only the files that are needed for the install target. Likewise, type "make dvap" or "make dvrptr" to compile only the files that are needed for the installdvap or installdvrptr target. This will speed up the compilation of the QnetGateway program, especially for single core boards like the Raspberry Pi Zero. Please note that "make" (without a target) will still build all programs. The files qn.cfg, gwys.txt and optionally MMDVM.qn are now installed as symbolic links in the $(BINDIR) installation directory. This will eliminate problems where you either edit the wrong file, or accidentally install an older copy over a newer copy when reinstalling. You also don't need to use root access to update these files. Tom N7TAE

QnetGateway now supports the Icom Repeater. Consider this an "alpha" release because we have only tested it on a single module repeater. We would be happy to work with anyone that would like to try out QnetGateway on a multi-module Icom Repeater. QnetGateway is an alternative to G4KLX-bases software and is fully functional with REF, XRF and DCS linking, customizable DTMF parsing and remote control (which can easily be scripted with cron jobs). And of course, QnetGateway fully supports routing! It's very easy to build and configure and has a tiny "footprint" compared to other ircDDB Gateway systems. Please note that QnetGateway does not yet support the 23cm Data-only module. #YouHaveAChoice

I have done a major overhaul of QnetLink. I managed to find and fix a couple of small bugs along the way. I've been using it for several days without any problems and have merged it into the master branch.

Can I use the Raspberry Pi 3 for the gateway on Dstar ID-RP2C Controller. It seems that I needed two NICs cards, PI star has only one. N0MIS

Functionally, I thought I had a good idea. Now I think I am looking at the impossible. Bash scripts do not control the radio - they issue Unix commands. Are the commands from the radio to QuadNet digitized - as in passed through the Vocoder? Or are they character data strings that could be passed to QuadNet?

I have been trying DTMF control with QnetGateway in Itap mode in a mobile environment today. It appears that I can not stay linked for more than a few minutes. REF001C, REF030C, XRF757A, DCS307D. I would send the logs for qnetgateway, qnlink and qnitap but I can not seem to locate them. On a side issue, I was trying to have the RPi 3B+ hooked to the ID-4100a and expected to switch back and forth on the ID-4100 between Normal mode and Terminal Mode. It "appeared" that I needed to reboot the RPi when going from Normal mode to the Terminal Mode on the ID-4100. Is my perception based in any reality?

Hello, I was able to set up the IP address for the 2nd NIC, as shown below "enp4s0". Ping Gateway 172.16.0.20 and controller 172.16.0.1 all okay. But failed qngateway.service shown below. Anyone could provide guidance. Thanks. root@nolyn78dell:/home/nolyn1978/QnetGateway# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 18:0f:76:cc:18:fa brd ff:ff:ff:ff:ff:ff inet 172.16.0.20/24 brd 172.16.0.255 scope global enp4s0 valid_lft forever preferred_lft forever inet6 fe80::2007:6e18:1a5f:56c9/64 scope link valid_lft forever preferred_lft forever 3: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 14:fe:b5:df:c6:c2 brd ff:ff:ff:ff:ff:ff inet 192.168.1.170/24 brd 192.168.1.255 scope global dynamic enp0s25 valid_lft 86186sec preferred_lft 86186sec inet6 fe80::16fe:b5ff:fedf:c6c2/64 scope link valid_lft forever preferred_lft forever root@nolyn78dell:/home/nolyn1978/QnetGateway# systemctl status qngateway ● qngateway.service - QnetGateway Loaded: loaded (/lib/systemd/system/qngateway.service; enabled; vendor preset: enabled) Active: failed (Result: signal) since Sat 2018-09-08 21:33:44 PDT; 6min ago Process: 1409 ExecStart=/usr/local/bin/qngateway /usr/local/etc/qn.cfg (code=killed, signal=SEGV) Main PID: 1409 (code=killed, signal=SEGV) Sep 08 21:33:44 nolyn78dell systemd[1]: qngateway.service: Main process exited, code=killed, status=11/SEGV Sep 08 21:33:44 nolyn78dell systemd[1]: qngateway.service: Unit entered failed state. Sep 08 21:33:44 nolyn78dell systemd[1]: qngateway.service: Failed with result 'signal'. Sep 08 21:33:44 nolyn78dell systemd[1]: qngateway.service: Service hold-off time over, scheduling restart. Sep 08 21:33:44 nolyn78dell systemd[1]: Stopped QnetGateway. Sep 08 21:33:44 nolyn78dell systemd[1]: qngateway.service: Start request repeated too quickly. Sep 08 21:33:44 nolyn78dell systemd[1]: Failed to start QnetGateway. Sep 08 21:33:44 nolyn78dell systemd[1]: qngateway.service: Unit entered failed state. Sep 08 21:33:44 nolyn78dell systemd[1]: qngateway.service: Failed with result 'signal'.

Hi Colby, Others from the group want to try to link their hotpot to the repeater. I provided the instruction to them to add the repeater call sign and update the DPlus host file , just like what I did. Do I need to configure any on the QnetGateway for them to link their hotspot to the repeater? Thanks.