About 10 weeks ago, I put a very crude method of insuring that the gateways were all linked to REF034C, so that we had a fully-connected network of repeaters for the NEFL-DStar Network – and I do mean VERY CRUDE. Every hour, on the half, I issued a link command to connect to REF034C (same as issuing REF034CL in the URCALL field, if you were doing it on the RF side).

Crude, but it worked – if the gateway was already connected to ANYTHING, it would simply respond-back with “Link Already Established”. If the link was idle, it would connect to REF034C and respond with “Link Established”.

There was a downside – every hour, on the half – you would usually hear “Link Already Established” – quite annoying. Okay – it’s functional, but certainly not elegant (hey – I TOLD YOU I was a Linux knucklhead..!!).

It’s only been a couple of weeks since Jason Price (W4LTL) graciously took over the management of the D-Star Gateways for us. It has been a big relief, since he is a Unix/Linux professional by trade, as well as being a sponge to all things D-Star.

Well, Jason has changed all of that. Wednesday evening, he developed a method of actually checking for the link status – then if idle, it would link to the default REF034C – if active, it would just terminate QUIETLY. He tested it late Wednesday evening and has it working now.

Following is the email exchange from that night..  KUDOS to Jason… this is GREAT STUFF..!!!!

Above: “Linker” – explanation of how it works (click to enlarge)