开云体育

Thanks, but the exec_?.sh stuff is the original idea of Scott KI4LKF.

Two thinks to remember:

1. You may have to subscribe twice if your local cache doesn't have the IP address of your target route. (Like right after you boot up.)
2. qnremote isn't designed to be run in batch mode. You'll need some sleep between calls to let your system react to the command before you send another.

Here is an untested example that would get me on module C logged into DSTAR2:
-----------
/bin/bash
qnremote c n7tae dstar2
sleep 6
qnremote c n7tae dstar2
-----------
If executed right after you boot up, the first qnremote will get a "Not in cache, please try again" message, then the 2nd will get you subscribed. Please note that if you execute this script and your cache already knows DSTAR2, you will be making an ~200 msec quite transmission into the Array on the second qnremote. If you're already subscribed, you'll make two transmissions into the Array.

Let me look into making QnetGateway more intelligent about logging into a routing target, so that you don't have to "prime the pump". Just what I need, one more item for my inbox...