Keyboard Shortcuts
Likes
Search
DStarRepeater QnetGateway
Greetings,
I am looking to switch to this format. I really like you can execute 36 commands. This will really help me out as a repeater owner. I run a lot of commands from the keyboard that would be easier from the radio. But why I am writing this. I run dstarrepeater with split repeater. I run the voting system and have lots of RX sites. Can I still use this with your gateway? We use Starnet a lot also. I can not get it to work anymore in openquad or irc. I am looking a solution. Thanks, Ryan |
Hi Ryan, You may want to look at "Smart Groups" in Qnetgateway which is a newer implementation of the Starnet model. John On Sun, Mar 21, 2021 at 8:38 AM Ryan Collier <kb8pmy@...> wrote: Greetings, --
John D. Hays Kingston, WA K7VE / WRJT-215 ? |
Thanks, the scripting capability is an often overlooked and a powerful feature of QnetGateway. Along with qnremote, it gives the administrator unprecedented control over a repeater system. QnetGateway does not officially support DStarRepeater. Nevertheless, it might be possible to make it work. QnetGateway does support MMDVMHost and as far as I know, the packet exchange between MMDVMHost and ircDDBGateway is identical to the packet exchange between DStarRepeater and ircDDBGateway. This means that if you configure QnetGateway to talk to MMDVMHost, but instead substitute DStarRepeater, it might work. Unfortunately, the qnadmin script will be of limited use since there is no provision within qnadmin to start/stop/monitor DStarRepeater. You still could use qnadmin to administer qngateway and qnrelay. You would either have to modify qnadmin (not recommended unless you are a bash shell programming expert) or handle the DStarRepeater administration separately. The qnrelay program is a simple translator that converts the DSVT packets that qngateway uses for communication to its supported modems to DSRP packet that G4KLX uses for inter-process communication in his programs. Thus, it's qnrelay that will communicate with DStarRepeater. (BTW, DSVT is the format for a DStar packets traveling on the internet. See the actual formats in the QnetTypeDefs.h file in the QnetGateway repo.) I don't know anything about Voting system and how they work, but if your repeater system is based on a modem that QnetGateway natively supports, I would do that instead of using DStarRepeater. You can then take full advantage of qnadmin. The QuadNet IRC routing network supports both STARnet and Smart Groups. Be sure you're using the correct url(s) for our network server as we have recently moved them. The IPv4 IRC routing server is at ircv4.openquad.net and the IPv6 IRC routing server is at ircv6.openquad.net. Of course IRC uses TCP port 9007. Packet routing in IPv4 is on UDP port 40000 while packet routing on IPv6 is on UDP port 9011 (IANA approved!). There are many advantages of Smart Groups over STARnet groups, but unlike STARnet, which can be run as a mini-server as part of ircDDBGateway, the Smart Group Server is independent and not part of QnetGateway. You won't be able to run both QnetGateway and a Smart Group Server on the same server as they both would require exclusive access to UDP 40000 and (if IPv6 is available) UDP 9011. |
Thanks for the information. I will look in to that. I am pretty good at bash. I wrote most of my weather alerts. and all my ping software for the repeater.
Here is my issue this now. I have it running on a different computer. I rerouted the ports to the smart group server ports 4000 and 9007. I get this: Error returned from recv, err=104 IRCReceiver::doRead: recv error IRCClient::Entry: recvQ EOF, restarting IRCClient::Entry state == 6, clearing Gate->Address table. Disconnected from ircDDB Adding KB8PMY P to Smart Group STN093 C Cannot find KB8PMY P in the cache Successfully connected to rr.openquad.net at [107.191.121.105]:9007 IRCClient::Entry IRCProtocol::processQueues failed, restarting IRCClient::Entry state == 6, clearing Gate->Address table. Successfully connected to rr.openquad.net at [107.191.121.105]:9007 IRCDDBApp::setBestServer s-grp1s1 IRCDDBApp::setCurrentNick kc8oc-3 Connecting to ircDDB IRCDDBApp: state=2 choose new 's-'-user IRCDDBApp: state=3 tableID=1 IRCDDBApp: state=3 tableID=0 IRCDDBApp: state=6 initialization completed Connected to ircDDB Every couple seconds. also I keep getting every call in ircddb as not found in cache. I can get my hotspot to use the repeater but I can not get my repeater to use the smart group server ( ie ircddbgateway) DStarrepeater function I change them all manually. split repeater is a function of dstarrepeater. as long as I can get the two to talk together correctly. I can make everything else work. I have 4 RX sites with 2 tx. I don't want to lose that ability. But I can to limited with ircddbgateway. But I am reconsidered about the reconnect issue. I have tried rr and ircv4. same result |
M: 2021-03-21 17:41:29: USER: F4FXL??? NOT FOUND
M: 2021-03-21 17:41:43: USER: F5IHZ??? NOT FOUND M: 2021-03-21 17:41:48: USER: BU2FA??? NOT FOUND M: 2021-03-21 17:41:59: USER: F4FXL??? NOT FOUND M: 2021-03-21 17:42:04: USER: F1TKE??? NOT FOUND M: 2021-03-21 17:42:12: USER: F4FXL??? NOT FOUND M: 2021-03-21 17:42:13: USER: F5IHZ??? NOT FOUND M: 2021-03-21 17:42:19: USER: F1TKE??? NOT FOUND M: 2021-03-21 17:42:26: USER: F4FXL??? NOT FOUND M: 2021-03-21 17:42:40: USER: QNETHF?? NOT FOUND M: 2021-03-21 17:42:40: USER: QNETHF T NOT FOUND M: 2021-03-21 17:42:50: USER: IU0CML?? NOT FOUND M: 2021-03-21 17:42:53: USER: QW1BSB?? NOT FOUND M: 2021-03-21 17:42:53: USER: QW1BSB T NOT FOUND M: 2021-03-21 17:42:53: USER: PISTAR?? NOT FOUND M: 2021-03-21 17:42:53: USER: PISTAR T NOT FOUND M: 2021-03-21 17:42:53: USER: NYCQNS T NOT FOUND M: 2021-03-21 17:42:53: USER: NYCQNS X NOT FOUND M: 2021-03-21 17:42:53: USER: QNHFRX?? NOT FOUND M: 2021-03-21 17:42:53: USER: QNHFRX T NOT FOUND M: 2021-03-21 17:42:55: USER: STN206 A NOT FOUND M: 2021-03-21 17:42:55: USER: STN206 T NOT FOUND M: 2021-03-21 17:43:17: USER: F4FXL??? NOT FOUND |
Colby Ross W1BSB
Your logs you posted indicate your smart group server is still connecting to .? On Sun, Mar 21, 2021 at 13:48 Tom Early <n7tae@...> wrote: is a dummy server, left in place to satisfy nearly 8000 PiStar users that never do DStar routing. It will not respond with any Find command. |
Okay, So I have a few issues. One I don't think MMDVMHost is the same as DStarrepeater. Unless I have something set wrong.
Restarting 'gate2link'... Inactivity from local rptr module B, removing stream id 5223 CQnetDB::UpdateLH [UPDATE LHEARD SET (sfx,module,reflector,lasttime) = ('CLUB','B','Module? ',strftime('%s','now')) WHERE callsign='KB8PMY E';] error: near "(": syntax error Inactivity from local rptr module B, removing stream id 3361 Inactivity from local rptr module B, removing stream id 4459 Then I started qnrelay after this. I get this error riggs498@kd8tuz:~/QnetGateway$ ./qnrelay qn.cfg Reading file qn.cfg module_b = 'mmdvmhost' gateway_tomodemb not found in either the cfg file or the defaults file module_b_internal_ip = '127.0.0.1' module_b_local_port = 20011 module_b_gateway_port = 20010 log_qso not found in either the cfg file or the defaults file! msock=3, gateway=4 DEBUG: ProcessMMDVM: unusual packet len=24 DEBUG: ProcessMMDVM: unusual packet len=24 DEBUG: ProcessMMDVM: unusual packet len=24 Also in the gateway. I get this error when it trys to connect to the ircv4.openquad.net: Connecting to qnlink at gate2link Opening remote port at Connecting to modem at Repeater callsigns: [N8MFN-A] [N8MFN-B] [N8MFN-C] aprs hash code=[16028] for N8MFN? ? starting CIRCDDB Waiting for ircv4.openquad.net connection status of 2 ERROR: '[ircv4.openquad.net]:0' is malformed! ircv4.openquad.net status=0 ^Circv4.openquad.net server is using unknown protocol! Shutting down... IRCClient::Entry: thread terminated at state=0 QnetGateway exiting Ryan |
Colby Ross W1BSB
¿ªÔÆÌåÓýDid you run qnconfig and configure a module as ¡°MMDVMHost¡±? ?Or did you change parameters in the defaults file? ? ? From: [email protected] <[email protected]> On Behalf Of Ryan Collier
Sent: Monday, March 22, 2021 22:42 To: [email protected] Subject: Re: [QnetGateway] DStarRepeater QnetGateway ? Okay, So I have a few issues. One I don't think MMDVMHost is the same as DStarrepeater. Unless I have something set wrong. |
Colby Ross W1BSB
¿ªÔÆÌåÓýWhatever you changed, you are still missing some crucial stuff that all the pieces need to start and talk to each other.? I would suggest setting up qn.cfg for mmdvmhost and changing the parameters with in it (you may need to run qnconfig in expert mode, i.e. ./qnconfig expert to access some of the settings). ?I verified just now on my system that an mmdvmhost module will start without mmdvmhost (qnetgateway starts itself, link and relay). I¡¯m assuming all you really need to change are whatever ports dstarrepeater is listening on, to match, or you could change them in qnconfig to match what you need. ? What parameters exactly did you change? Something¡¯s missing because the pieces aren¡¯t starting. ? ? From: [email protected] <[email protected]> On Behalf Of Ryan Collier
Sent: Monday, March 22, 2021 22:56 To: [email protected] Subject: Re: [QnetGateway] DStarRepeater QnetGateway ? Changed the parameters cause I am not running MMDVMHost. It is reading the packets. I just executed a command. |
Here is what expert gave me:
# Created on Mon Mar 22 23:04:57 EDT 2021 ircddb_login='N8MFN' module_b=mmdvmhost module_b_internal_ip='127.0.0.1' module_b_gateway_port=20010 module_b_local_port=20011 gateway_send_qrgs_maps=true gateway_local_irc_ip='0.0.0.0' aprs_enable=true aprs_host='rotate.aprs.net' aprs_port=14580 aprs_interval=40 link_ref_port=20001 link_xrf_port=30001 link_dcs_port=30051 link_announce=true link_acknowledge=true link_max_dongles=5 file_gwys='/home/riggs498/QnetGateway/gwys.txt' file_dtmf='/tmp' file_status='/home/riggs498/QnwtGateway/rptr_status' file_echotest='/tmp' file_qnvoicefile='/tmp/qnvoice.txt' file_announce_dir='/home/riggs498/QnetGateway/announce' timing_timeout_echo=1 timing_timeout_remote_g2=2 timing_timeout_voicemail=1 timing_timeout_local_rptr=1 timing_play_wait=1 timing_play_delay=19 He is what I did. Same result: riggs498@kd8tuz:~/QnetGateway$ cat qn.cfg ########################################################################################################################## # # IRCDDB - You MUST use a legal callsign for logging into any IRC network # # you must specify you legal Callsign to enable QnetGateway ircddb_login='N8MFN'????????????????? # login callsign for the ircDDB network #ircddb0_host='ircv4.openquad.net'?? # other irc networks include group1-irc.ircddb.net and group2-irc.ircddb.net #ircddb_port=9007??????????????? # not a good idea to change! #ircddb_password='' # not needed for ircv4.openquad.net ########################################################################################################################## # # GATEWAY # # Very few users will need to specify anything in the 'gateway' section! gateway_bool_regen_header=true? # regenerate headers from incoming data gateway_send_qrgs_maps=true???? # send frequency, offset, coordinates and url to irc-server gateway_local_irc_ip='0.0.0.0'? # the local port on the gateway for the IRC tcp socket gateway_external_ip='0.0.0.0'?? # this means accept a connection from any source #gateway_external_port=40000???? # don't change gateway_tolink='gate2link'????? # Unix sockets between qngateway and QnetLink gateway_fromlink='link2gate'??? # all Unix sockets are on the file system, but hidden from view ########################################################################################################################## # # APRS - for tracking users and also this repeater. # aprs_enable=true??????????? # uncomment and set this to 'false' if you don't wany the gateway interacting with APRS aprs_host='rotate.aprs.net' # the APRS network server aprs_port=14580???????????? # and port aprs_interval=40??????????? # keep-alive in minutes #aprs_filter=''????????????? # advanced feature ########################################################################################################################## # # LINK - controls the behaviour of QnetLink (qnlink) # #link_admin=''????????????? # these comma-separated list of users can execute scripts, block dongles, reload the gwys.txt ??????????????????????????? # if empty, everyone has admin privileges. #link_link_unlink=''??????? # if defined, comma-separated list of users that can link and unlink a repeater #link_no_link_unlink=''???? # if defined, comma-separated list of users that cannot link or unlink, it's a blacklist. ??????????????????????????? # if a blacklist is defined and not empty, the link_unlink will not be read link_incoming_ip='0.0.0.0' # incoming ip address of qnlink, '0.0.0.0' means accepts any connection. link_ref_port=20001??????? # port for REF linking, don't change link_xrf_port=30001??????? # port for XRF linking, don't change link_dcs_port=30051??????? # port for DCS linking, don't change link_announce=true???????? # do link, unlink, etc. announcements link_acknowledge=true????? # send text acknowledgment on key-up link_max_dongles=5???????? # maximum number of linked hot-spots ########################################################################################################################## # # Here is an example MMDVM module on 70cm channel B # module_b=mmdvmhost #module_b_link_at_start=''? # For example, set to 'REF001 C' to link module to reflector 1-charlie when the module starts. #module_b_inactivity=0????? # if no activity for this many minutes unlink any linked reflector. Zero means no timer. #module_b_callsign=''?????? # if you operate in a 'restriction mode', use your personal callsign. Usually leave this empty. #module_b_packet_wait=25??? # how many milliseconds to wait on packets in a voicestream #module_b_acknowledge=false # Do you want an ACK back? #module_b_ack_delay=250???? # millisecond delay before acknowledgement #module_b_frequency=0?????? # if you specify here, this frequency will show up on the QuadNet USER GATEWAYS webpage #module_b_offset=0????????? # usually the duplex tx-rx offset, but for dvap, it's a frequency tweak #module_b_range=0?????????? # the range of this repeater, in meters 1609.344 meters is 1.0 miles #module_b_agl=0???????????? # the height above ground level for this repeater's antenna #module_b_latitude=0??????? # you can leave this unspecified for a mobile rig #module_b_longitude=0?????? # like the latitude #module_b_desc1=''????????? # maximum of 20 characters, most special symbols are not allowed #module_b_desc2=''????????? # just like desc1 #module_b_gate2modem1='gate2modem1'???????? # Unix Sockets between a modem and the gateway #module_b_modem2gate1='modem2gate1'???????? # 0 is for A, 1 is for B and 2 is for C #module_b_url='github.com/n7tae/g2_ircddb'? # 80 characters max # MMDVM - Special parameters when: module_b='mmdvm' module_b_internal_ip='127.0.0.1' # where MMDVMHost will find the QnetRelay program module_b_gateway_port=20010??? # which port will QnetRelay be sending on module_b_local_port=20011????? # which port will MMDVMHost be sending on # LOGGING - Control extra logging - useful for debugging # #log_qso=false?? # QSO info goes into the log #log_irc=false?? # IRC debug info #log_dtmf=false? # DTMF debug info ########################################################################################################################## # # DPLUS - Control of dplus (trust system) linking to repeaters and REF reflectors # # The following settings do not affect your ability to use dplus linking to XRF or XLX reflectors! # You must be registered on the DPlus system, see www.dstargateway.org, otherwise authorization will fail, # even if QnetLink reports a successful authorization. #dplus_authorize=false???? # to enable, uncomment and set to true to link to DPlus reflectors and/or repeaters #dplus_ref_login=''??????? # for logging into REF reflectors, if empty, ircddb_login will be used #dplus_use_reflectors=true # set to false if you are not going to link to DPlus reflectors #dplus_use_repeaters=true? # set to false if you are not going to link to DPlus repeaters # any gateways in your gwys.txt file will override any reflectors or repeaters that DPlus authorization returns. ########################################################################################################################## # # FILE - where important QnetGateway files and directories are found. # file_status='/home/riggs498/QnwtGateway/rptr_status' # where repeater status info is passed between services file_dtmf='/tmp'???????????????????????? # where DTMF is decoded file_echotest='/tmp'???????????????????? # echo dat files will end up here file_qnvoicefile='/tmp/qnvoice.txt'????? # where qnvoice will create the play command file_gwys='/home/riggs498/QnetGateway/gwys.txt'????? # where the list of gateways and reflectors (with ports) is. file_announce_dir='/home/riggs498/QnetGateway/announce'?????? # where the *.dat files are for the verbal link, unlink, etc. announcements ########################################################################################################################## # # TIMINGS - for controlling how to deal with timing issues # # most users will not have to override any of these default values timing_timeout_echo=1?????? # seconds before we assume echo has timed out timing_timeout_voicemail=1? # seconds before we assume voicemail has timed out timing_timeout_remote_g2=2? # after this many seconds with no packets, we assume the tx is closed timing_timeout_local_rptr=1 # local repeater timeout, in seconds timing_play_wait=1????????? # seconds before echo or voicemail playback occurs, between 1 and 10 timing_play_delay=19??????? # microseconds between frames playback, if echo sounds bad, adjust this up or down 1 or 2 ms |
Colby Ross W1BSB
¿ªÔÆÌåÓýYou have to reset the defaults file back to its ¡°default¡± state which reverts the mods you made to it. Then use qnconfig expert to make your qn.cfg file. ? You¡¯re replacing mmdvmhost with dstarrepeater, yes?? If that¡¯s the case, configuring an mmdvmhost module without changing any values in the defaults file and using qnconifig to change only what you need should cause it to successfully start qngateway, qnlink, and qnrelay.? My guess is you need to git checkout defaults and keep your qn.cfg file you wrote with qncofig, then uninstall, clean, install and it should start everything. ? Colby ? From: [email protected] <[email protected]> On Behalf Of Ryan Collier
Sent: Monday, March 22, 2021 23:16 To: [email protected] Subject: Re: [QnetGateway] DStarRepeater QnetGateway ? Here is what expert gave me: |
You're getting a lot of nonsense errors because things aren't starting properly. If you don't "make installbase", the all-important defaults file won't be where it's suppose to be and things will go to hell quickly.
Try using the aliases in bash_aliases (cp bash_alises ~/.bash_aliases). While you're troubleshooting you will find these aliases a great time-saver. You'll have to copy these in if you already have a ~/.bash_aliases file. After you "make base" and "make relay", you can use the "start" alias ("start relay"). That will install and start the base programs, qngateway and qnlink and then start qnrelay an automatically tail the qnrelay log. If it isn't already started, star dstarrepeater. Sorry, no alias, you'll have to start this yourself. Use "stop relay" to stop everything and uninstall them. Use "watch <name>" to put a tail on the qn<name> process, "watch gateway" will tail the log of qngateway. This is alot quicker than using the ./qnadmin script. Fun fact: you can start you system and tail a different process log, like "start relay gateway" or "start relay link". The default UDP ports used between qnrelay and starrepeater are the default ports that MMDVMHost uses to talk to ircddbgateway and therefore should be the default ports that dstarrepeater uses to talk to ircddbateway. My expectation is that dstarreapter looks just like MMDVMhost as far as UDP packet exchange is concerned, but if they are not you won't see any qso logging on the QnetGateway side of thing as to try to transmit into dstarrepeater. As long as qngateway, qnlink and qnrelay are all running they, at least, should be happy and should not spew any error messages. I don't anticipate any need to invoke the expert ./qnconfig mode. The default values for expert parameters should be good to go. FYI, qngateway, qnlink and qnrelay don't use UDP ports to talk to each other, they use disk-based UNIX ports that are much faster and more efficient than UDP loopback ports, that's the "gateway_tomodemb" stuff and you shouldn't have to fiddle with them at all. Other than maybe an initial notice that some handshaking is pending early in the startup process, you shouldn't see any errors from these UNIX ports once everything (qnrelay, qngateway and qnlink) is initialized. |
So, I am coming to the conclusion that there is something different from MMDVM and DStarrepeater. It will take my commands. But no matter what I do. I can not get rid of this.
Apr 08 02:12:55 dstarrepeater qnrelay[1119]: DEBUG: ProcessMMDVM: unusual packet len=24 Apr 08 02:13:06 dstarrepeater qnrelay[1119]: DEBUG: ProcessMMDVM: unusual packet len=24 Apr 08 02:13:15 dstarrepeater qnrelay[1119]: DEBUG: ProcessMMDVM: unusual packet len=24 Also I get this every key up in gateway log file: Apr 08 02:24:58 dstarrepeater qngateway[1900]: Inactivity from local rptr module B, removing stream id a1e1 Apr 08 02:25:19 dstarrepeater qngateway[1900]: Inactivity from local rptr module B, removing stream id a6b6 It will not transmit. I will keep trying. But I think I have hit the road block. I can halt the system reboot the system via the HX and RX commands. Thanks for your efforts |
So I am sending I command. I am getting this:
Apr 08 02:37:12 dstarrepeater qnrelay[5157]: DEBUG: ProcessMMDVM: unusual packet len=24 Apr 08 02:37:13 dstarrepeater qnrelay[5157]: Read error on 'tomodemb': Connection reset by peer Apr 08 02:37:13 dstarrepeater qnrelay[5157]: Restarting 'tomodemb'... Apr 08 02:37:13 dstarrepeater qnrelay[5157]: Waiting for tomodemb server to start... Apr 08 02:37:13 dstarrepeater qnrelay[5157]: DEBUG: Run: read zero bytes from 0 Apr 08 02:37:29 dstarrepeater qnrelay[5157]: Read error on 'tomodemb': Connection reset by peer Apr 08 02:37:29 dstarrepeater qnrelay[5157]: Restarting 'tomodemb'... Apr 08 02:37:29 dstarrepeater qnrelay[5157]: Waiting for tomodemb server to start... Apr 08 02:37:29 dstarrepeater qnrelay[5157]: DEBUG: Run: read zero bytes from 0 Apr 08 02:37:29 dstarrepeater qnrelay[5157]: DEBUG: ProcessMMDVM: unusual packet len=24 Apr 08 02:37:39 dstarrepeater qnrelay[5157]: DEBUG: ProcessMMDVM: unusual packet len=24 Apr 08 02:37:45 dstarrepeater qnrelay[5157]: Read error on 'tomodemb': Connection reset by peer Apr 08 02:37:45 dstarrepeater qnrelay[5157]: Restarting 'tomodemb'... Apr 08 02:37:45 dstarrepeater qnrelay[5157]: Waiting for tomodemb server to start... Apr 08 02:37:45 dstarrepeater qnrelay[5157]: DEBUG: Run: read zero bytes from 0 Apr 08 02:37:45 dstarrepeater qnrelay[5157]: DEBUG: ProcessMMDVM: unusual packet len=24 I am taking it there is a configuration issue? |