开云体育

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.