Here is an idea on this issue. Created a bash script that checks the size of a specified file. If the file size is not zero, it stops a specified service. If the file size is zero, it checks the status of the service, and if the service is stopped, it starts the service. The script also logs actions to a log file.
# Script to check file size and manage service status
# Configuration FILE_PATH="/root/g2_link/RPT_STATUS.txt" ?# Change this to the file you want to check SERVICE_NAME="monlink" ? ? ?# Change this to your service name LOG_FILE="/var/log/monlink_g2_link_check.log" ?# Change this to your desired log file location
# Function to log messages log_message() { ? ? local message="$1" ? ? echo "$(date '+%Y-%m-%d %H:%M:%S') - $message" >> "$LOG_FILE" }
# Check if the file exists if [ ! -f "$FILE_PATH" ]; then ? ? log_message "Error: File '$FILE_PATH' does not exist." ? ? exit 1 fi
# Get the file size FILE_SIZE=$(stat -c%s "$FILE_PATH")
# Check if the file size is not zero if [ "$FILE_SIZE" -ne 0 ]; then ? ? log_message "File size is not zero ($FILE_SIZE bytes). Stopping service '$SERVICE_NAME'." ? ? systemctl stop "$SERVICE_NAME"
? ? if [ $? -eq 0 ]; then ? ? ? ? log_message "Service '$SERVICE_NAME' stopped successfully." ? ? else ? ? ? ? log_message "Error: Failed to stop service '$SERVICE_NAME'." ? ? ? ? exit 1 ? ? fi else ? ? log_message "File size is zero. Checking status of service '$SERVICE_NAME'." ? ? SERVICE_STATUS=$(systemctl is-active "$SERVICE_NAME")
? ? if [ "$SERVICE_STATUS" = "inactive" ]; then ? ? ? ? log_message "Service '$SERVICE_NAME' is stopped. Starting service." ? ? ? ? systemctl start "$SERVICE_NAME"
? ? ? ? if [ $? -eq 0 ]; then ? ? ? ? ? ? log_message "Service '$SERVICE_NAME' started successfully." ? ? ? ? else ? ? ? ? ? ? log_message "Error: Failed to start service '$SERVICE_NAME'." ? ? ? ? ? ? exit 1 ? ? ? ? fi ? ? else ? ? ? ? log_message "Service '$SERVICE_NAME' is already running." ? ? fi fi
exit 0
=========================================
Not sure what is wrong just yet... but when I check the RPT_STATUS.txt file size with an ls -l, it shows 0 but the script says it is not empty?
If g2_link is running with dplus, we want to make sure that a repeater module is not connected to both an REFxxxy reflector at the same time as connected to XRFxxxy. There is a blocking mechanism in place to keep an RF user from connecting to REFxxx or XRFxxx if there is an existing connection to either already in place. But, we noticed in the past that that blocking mechanism is ignored when a command line connection request is made, i.e., monlink will restore an REFxxxy connection when an XRFxxxy connection is already in place. Monlink does not know to check the RPT_STATUS.txt to see if it is empty.
Maybe the easiest way is to suspend monlink while g2_link has an active connection… RPT_STATUS.txt is not zero/0? That might be OK for a single repeater module system… but maybe a multiple module system has a dplus reflector on one module and an XRF/XLX/DCS on the other?
Maybe abandon monlink and use a bash script and cron jobs to do what monlink did for dplus?
Any thoughts?
Terry M Stader KA8SCP WB1GOF Repeaters Proprietor
-- Terry Stader - KA8SCP D-STAR Gateway & Reflector Admin
On Sat, Feb 8, 2025 at 11:15?PM Jim - K6JM via groups.io <jmm@...> wrote:
There's a lot of history behind why an ICOM gateway must use DPlus to link to REF reflectors and g2-link to link to other protocol reflectors. Briefly, g2-link came from an early digital voice developer. He made one kind of big mistake very long ago, and since then, the DPlus developer has pretty much blocked that code from linking directly to DPlus reflectors.
So the add-ons use slightly different syntax. I suppose D-Star hams could ask the DPlus developer to allow direct links from g2-link into DPlus reflectors. I have no idea if such a campaign would be successful. I personally believe no problems would happen if he allowed that.
The only other solution is for repeater owners to switch from ICOM's gateway to an alternate one, such as G4KLX's ircDDBGateway. It supports seamless linking to REF, XRF, DCS and XLX reflectors using the same syntax for all. But, many DStar repeater owners would rather not move away from ICOM software, and their users should be thankful for g2-link.
WAYYYY too many "personality" issues in D-STAR. Too many people that don't play well with others.
And I say that as someone into D-STAR since '11 and an Icom fanboy for many years before that.
*Does* the G4KLX package really support full use of REF reflectors or only the "rogue" instances above REF100? And does it handle OTW user connections in a manner like DPlus?
-- Peter Laws | VE[23]UWY / N5UWY | plaws0 gmail com | Travel by Train!
Quite awhile ago, Ramesh and I played around with an application that went on the PC that the DV Dongle was attached to. That app forwarded the 20001 UDP traffic to 30001 and out to the g2_link gateway.?
Also… there was a client that worked to talk for XRF reflectors using the dongle…?
On Feb 8, 2025, at 9:34?PM, Peter Laws via groups.io <plaws0@...> wrote:
?Got the chance to actually test out the g2_link install I did the other day during Friday's Cannet. ?I still haven't got things set up for automated connection to one of the XRFs a little closer to the center of the Cannet universe. ?But I had no issues hearing the net once I connected to ?XRF044A.
At least OTA from VE2RM.
I couldn't for the life of me figure out why I wasn't hearing anything through my radio when listening to my hotspot, which was connected over the net to VE2RM.
But it's our old friend DPlus that handles hotspots and dvaps and dongles. ?Right.
So the question is, is there a workaround for this? ?Some way, maybe, that we can trick DPlus into believing that the data coming in via the g2_link network connection is actually being received over the air?
In any case, it seems to be working, which is cool.
There's a lot of history behind why an ICOM gateway must use DPlus to link to REF reflectors and g2-link to link to other protocol reflectors. Briefly, g2-link came from an early digital voice developer. He made one kind of big mistake very long ago, and since then, the DPlus developer has pretty much blocked that code from linking directly to DPlus reflectors.
So the add-ons use slightly different syntax. I suppose D-Star hams could ask the DPlus developer to allow direct links from g2-link into DPlus reflectors. I have no idea if such a campaign would be successful. I personally believe no problems would happen if he allowed that.
The only other solution is for repeater owners to switch from ICOM's gateway to an alternate one, such as G4KLX's ircDDBGateway. It supports seamless linking to REF, XRF, DCS and XLX reflectors using the same syntax for all. But, many DStar repeater owners would rather not move away from ICOM software, and their users should be thankful for g2-link.
Got the chance to actually test out the g2_link install I did the other day during Friday's Cannet. I still haven't got things set up for automated connection to one of the XRFs a little closer to the center of the Cannet universe. But I had no issues hearing the net once I connected to XRF044A.
At least OTA from VE2RM.
I couldn't for the life of me figure out why I wasn't hearing anything through my radio when listening to my hotspot, which was connected over the net to VE2RM.
But it's our old friend DPlus that handles hotspots and dvaps and dongles. Right.
So the question is, is there a workaround for this? Some way, maybe, that we can trick DPlus into believing that the data coming in via the g2_link network connection is actually being received over the air?
In any case, it seems to be working, which is cool.
Got the chance to actually test out the g2_link install I did the other day during Friday's Cannet. I still haven't got things set up for automated connection to one of the XRFs a little closer to the center of the Cannet universe. But I had no issues hearing the net once I connected to XRF044A.
At least OTA from VE2RM.
I couldn't for the life of me figure out why I wasn't hearing anything through my radio when listening to my hotspot, which was connected over the net to VE2RM.
But it's our old friend DPlus that handles hotspots and dvaps and dongles. Right.
So the question is, is there a workaround for this? Some way, maybe, that we can trick DPlus into believing that the data coming in via the g2_link network connection is actually being received over the air?
In any case, it seems to be working, which is cool.
On Fri, Feb 7, 2025 at 11:18?PM Terry M. Stader via groups.io <ka8scp@...> wrote:
I sent some script examples and posted the list of commands in a previous message.
Rob captured the essence of the principle commands for lining and unlinking.
Yes he did and I put that in a text file on the GW.
It is critical that you coordinate any monlink scheduling so not to initiate a dplus connection at the same time as a g2_link comm补苍诲… you do not want to cross link a REFxxx with and XRFxxx which is possible at the command line level.
WHO WOULD EVER DO THAT NOT ME CERTAINLY BUT IF IT WAS IT DID HAPPEN WOULD HAVE BEEN BY ACCIDENT. :)
monlink switched us off REF038A at whatever time I had set even though the net was still active (I need to re-re-read the monlink docs - I thought I'd fixed that). So I thought "well, let me try that g2_link stuff like all the cool kids" ... and of course, as you have said many times. monlink (and, really, DPlus, too) knows nothing about g2_link-related stuff.
I caught it reconnecting a couple times before finally updating the schedule in monlink and reloading it (again, I thought monlink picked up changes in the config ... re-re-re-read the docs tomorrow).
Now there is a Cannet-sized hole in the monlink schedule (F, 2055-0000) and I'll add the appropriate scripts to the crontab tomorrow.
Also… g2_link does NOT recognize XLX as a valid reflector type. You have to use the XRF or DCS prefix.
Ah. I think you've mentioned that before, but thanks for repeating it.
LONNGG Cannet tonight. I even checked in it was so long. :-)
Peter
-- Peter Laws | VE[23]UWY / N5UWY | plaws0 gmail com | Travel by Train!
I sent some script examples and posted the list of commands in a previous message.
Rob captured the essence of the principle commands for lining and unlinking.
It is critical that you coordinate any monlink scheduling so not to initiate a dplus connection at the same time as a g2_link comm补苍诲… you do not want to cross link a REFxxx with and XRFxxx which is possible at the command line level.
Also… g2_link does NOT recognize XLX as a valid reflector type. You have to use the XRF or DCS prefix.
Of course, you can also use the URCall setting on your radio to link and unlink as well. The format is similar to Dplus, just use T (terminate) and O (open) instead of U (unlink) and L (link).? For example, if your URCall is set to XRF044AO , assuming your
other settings are correct, will make g2_link attempt to connect to XRF044A on the module it was received.
On Mon, Feb 3, 2025 at 12:06?PM Terry M. Stader via groups.io
<ka8scp@...> wrote:
> For example:
>
> [root@wb1gof my_scripts]# cat xrf221a-c.sh>
> #!/bin/bash
>?# script to automatically connect
> # C port to XRF221A using the g2_link tool
> # disconnect first
> /usr/bin/nc -u -w 1 10.0.0.2 30003 <<EOF
> um C
> EOF
> #
> sleep 3
> # disconnect dplus
> echo "?????? U" >/dstar/tmp/link-c
> #
> sleep 3
> # first connect with netcat to port
> # then connect to XRF221A
> /usr/bin/nc -u -w 1 10.0.0.2 30003 <<EOF
> lm CXRF221A
> EOF
> exit 0
>
Forgot about Cannet tonight.? Started to look at this to construct a
connect script to XLX044A ...? but where are? things like the um and
lm defined.
I figure "um X"? is "unlink module X" and "cm X" the same but connect ...
So I would send "lm BXLX044A" to port 30003 on our IP with netcat and
then um later?? Being sure to adjust monlink's schedule to "leave a
hole" for all the g2_link stuff?
--
Peter Laws | VE[23]UWY / N5UWY | plaws0 gmail com | Travel by Train!
-- Terry Stader - KA8SCP D-STAR Gateway & Reflector Admin
Oh, monlink knows nothing of non-DPlus reflectors.
I'd just like to find the docs that let me know what commands I can
send via netcat and how they relate to the commands I can send over
RF.
I had *meant* to do this before this evening, but alas ....
Didn't realize the RAC pres took a turn at NCS for the net ...
interesting.? No one in the hierarchy of that other national
association to our south is even aware of DV modes.? :-)
On Fri, Feb 7, 2025 at 9:25?PM Robert Gillis via groups.io
<robert@...> wrote:
>
> Hi Peter,
>
> I am listening to the Can-net at the moment (just started about 20 minutes ago), so perhaps I will hear you on here later tonight?
>
> I cant speak much to the coordination with monlink as I dont use it on our repeater, but I can confirm the following commands will work with g2_link:
>
> The following will unlink local module C:
>
> /usr/bin/nc -u -w 1 10.0.0.2 30003 <<EOF
> um C
> EOF
>
> and the following will link the local module C, to XRF044A ,
>
> /usr/bin/nc -u -w 1 10.0.0.2 30003 <<EOF
> lm CXRF044A
> EOF
>
> Of course, you can also use the URCall setting on your radio to link and unlink as well. The format is similar to Dplus, just use T (terminate) and O (open) instead of U (unlink) and L (link).? For example, if your URCall is set to XRF044AO , assuming your
other settings are correct, will make g2_link attempt to connect to XRF044A on the module it was received.
>
> Hope this helps.
>
> Rob,
> VY1RG
>
> ________________________________
> From: [email protected] <[email protected]> on behalf of Peter Laws via groups.io <plaws0@...>
> Sent: February 7, 2025 17:26
> To: [email protected] <[email protected]>
> Subject: Re: [g2-link] timeout ...
>
> On Mon, Feb 3, 2025 at 12:06?PM Terry M. Stader via groups.io
> <ka8scp@...> wrote:
>
> > For example:
> >
> > [root@wb1gof my_scripts]# cat xrf221a-c.sh>
> > #!/bin/bash
> > # script to automatically connect
> > # C port to XRF221A using the g2_link tool
> > # disconnect first
> > /usr/bin/nc -u -w 1 10.0.0.2 30003 <<EOF
> > um C
> > EOF
> > #
> > sleep 3
> > # disconnect dplus
> > echo "?????? U" >/dstar/tmp/link-c
> > #
> > sleep 3
> > # first connect with netcat to port
> > # then connect to XRF221A
> > /usr/bin/nc -u -w 1 10.0.0.2 30003 <<EOF
> > lm CXRF221A
> > EOF
> > exit 0
> >
>
> Forgot about Cannet tonight.? Started to look at this to construct a
> connect script to XLX044A ...? but where are? things like the um and
> lm defined.
>
> I figure "um X"? is "unlink module X" and "cm X" the same but connect ...
>
> So I would send "lm BXLX044A" to port 30003 on our IP with netcat and
> then um later?? Being sure to adjust monlink's schedule to "leave a
> hole" for all the g2_link stuff?
>
>
> --
> Peter Laws | VE[23]UWY / N5UWY | plaws0 gmail com | Travel by Train!
>
>
>
>
>
>
--
Peter Laws | VE[23]UWY / N5UWY | plaws0 gmail com | Travel by Train!
Oh, monlink knows nothing of non-DPlus reflectors.
I'd just like to find the docs that let me know what commands I can send via netcat and how they relate to the commands I can send over RF.
I had *meant* to do this before this evening, but alas ....
Didn't realize the RAC pres took a turn at NCS for the net ... interesting. No one in the hierarchy of that other national association to our south is even aware of DV modes. :-)
Of course, you can also use the URCall setting on your radio to link and unlink as well. The format is similar to Dplus, just use T (terminate) and O (open) instead of U (unlink) and L (link). For example, if your URCall is set to XRF044AO , assuming your other settings are correct, will make g2_link attempt to connect to XRF044A on the module it was received.
On Mon, Feb 3, 2025 at 12:06?PM Terry M. Stader via groups.io <ka8scp@...> wrote:
For example:
[root@wb1gof my_scripts]# cat xrf221a-c.sh> #!/bin/bash # script to automatically connect # C port to XRF221A using the g2_link tool # disconnect first /usr/bin/nc -u -w 1 10.0.0.2 30003 <<EOF um C EOF # sleep 3 # disconnect dplus echo " U" >/dstar/tmp/link-c # sleep 3 # first connect with netcat to port # then connect to XRF221A /usr/bin/nc -u -w 1 10.0.0.2 30003 <<EOF lm CXRF221A EOF exit 0
Forgot about Cannet tonight. Started to look at this to construct a connect script to XLX044A ... but where are things like the um and lm defined.
I figure "um X" is "unlink module X" and "cm X" the same but connect ...
So I would send "lm BXLX044A" to port 30003 on our IP with netcat and then um later? Being sure to adjust monlink's schedule to "leave a hole" for all the g2_link stuff?
-- Peter Laws | VE[23]UWY / N5UWY | plaws0 gmail com | Travel by Train!
-- Peter Laws | VE[23]UWY / N5UWY | plaws0 gmail com | Travel by Train!
Of course, you can also use the URCall setting on your radio to link and unlink as well. The format is similar to Dplus, just use T (terminate) and O (open) instead of U (unlink) and L (link).? For example, if your URCall is set to XRF044AO , assuming your
other settings are correct, will make g2_link attempt to connect to XRF044A on the module it was received.
On Mon, Feb 3, 2025 at 12:06?PM Terry M. Stader via groups.io
<ka8scp@...> wrote:
> For example:
>
> [root@wb1gof my_scripts]# cat xrf221a-c.sh>
> #!/bin/bash
>?# script to automatically connect
> # C port to XRF221A using the g2_link tool
> # disconnect first
> /usr/bin/nc -u -w 1 10.0.0.2 30003 <<EOF
> um C
> EOF
> #
> sleep 3
> # disconnect dplus
> echo "?????? U" >/dstar/tmp/link-c
> #
> sleep 3
> # first connect with netcat to port
> # then connect to XRF221A
> /usr/bin/nc -u -w 1 10.0.0.2 30003 <<EOF
> lm CXRF221A
> EOF
> exit 0
>
Forgot about Cannet tonight.? Started to look at this to construct a
connect script to XLX044A ...? but where are? things like the um and
lm defined.
I figure "um X"? is "unlink module X" and "cm X" the same but connect ...
So I would send "lm BXLX044A" to port 30003 on our IP with netcat and
then um later?? Being sure to adjust monlink's schedule to "leave a
hole" for all the g2_link stuff?
--
Peter Laws | VE[23]UWY / N5UWY | plaws0 gmail com | Travel by Train!
On Mon, Feb 3, 2025 at 12:06?PM Terry M. Stader via groups.io <ka8scp@...> wrote:
For example:
[root@wb1gof my_scripts]# cat xrf221a-c.sh> #!/bin/bash # script to automatically connect # C port to XRF221A using the g2_link tool # disconnect first /usr/bin/nc -u -w 1 10.0.0.2 30003 <<EOF um C EOF # sleep 3 # disconnect dplus echo " U" >/dstar/tmp/link-c # sleep 3 # first connect with netcat to port # then connect to XRF221A /usr/bin/nc -u -w 1 10.0.0.2 30003 <<EOF lm CXRF221A EOF exit 0
Forgot about Cannet tonight. Started to look at this to construct a connect script to XLX044A ... but where are things like the um and lm defined.
I figure "um X" is "unlink module X" and "cm X" the same but connect ...
So I would send "lm BXLX044A" to port 30003 on our IP with netcat and then um later? Being sure to adjust monlink's schedule to "leave a hole" for all the g2_link stuff?
-- Peter Laws | VE[23]UWY / N5UWY | plaws0 gmail com | Travel by Train!
There is a working example tpl in the Files section that has the information you are trying to add. Feel free to modify the example I guess if it doesn’t float your boat.
On Feb 4, 2025, at 7:34?PM, Peter Laws via groups.io <plaws0@...> wrote:
?On Tue, Feb 4, 2025 at 2:24?PM Robert Gillis via groups.io <robert@...> wrote:
Thank you, an oversight on my part for sure.
Bah - no sweat. ?I'm happy to see folks contributing!
From what I can see, admins cannot modify (easily) the DPlus dashboard. ?No so much once I found $G2_LINK/g2_link/g2_lh.tpl
Since I can't edit the DPlus page, I will edit the g2_link page with some instructions for "both sides" (especially "remember to unlink on both sides!").
Peter
-- Peter Laws | VE[23]UWY / N5UWY | plaws0 gmail com | Travel by Train!
-- Terry Stader - KA8SCP D-STAR Gateway & Reflector Admin
On Tue, Feb 4, 2025 at 2:24?PM Robert Gillis via groups.io <robert@...> wrote:
Thank you, an oversight on my part for sure.
Bah - no sweat. I'm happy to see folks contributing!
From what I can see, admins cannot modify (easily) the DPlus dashboard. No so much once I found $G2_LINK/g2_link/g2_lh.tpl
Since I can't edit the DPlus page, I will edit the g2_link page with some instructions for "both sides" (especially "remember to unlink on both sides!").
Peter
-- Peter Laws | VE[23]UWY / N5UWY | plaws0 gmail com | Travel by Train!
I see it is not in Robert’s AlmaLinux version of the instructions… I’ll add it tomorrow and put the updated file in the g2_link file section of groups.io
Terry?
Terry M Stader KA8SCP
WB1GOF Repeaters Proprietor?
On Feb 2, 2025, at 10:02?PM, Terry M. Stader <ka8scp@...> wrote:
?It is there?
========
# personalize the cron.d dashboard file
# make sure to change output location to /var/www/html/
# NOTE: Non-standard gateway IP g2_lh -? reveals option
# example: -a 192.168.1.172
#after cron runs, new g2_link dashboard at https://your_ip_here/fs.html"
=========
Terry M Stader KA8SCP
WB1GOF Repeaters Proprietor?
On Feb 2, 2025, at 9:52?PM, Peter Laws via groups.io <plaws0@...> wrote:
?
Duuuude.? Can we get that added to the readme?? I suspect that a lot of folks have normal IPs since G3(.0) came out and the 10.0.0.silly addresses are mandated any more.
THANK YOU! ?
On Sun, Feb 2, 2025 at 9:41?PM Terry M. Stader via
<ka8scp=[email protected]> wrote:
Are you using the Icom standard 10.0.0.2 IP for the gateway? Otherwise you have to specify the IP in the cron job…
I get the error above when I run this: ?" /root/g2_link/g2_lh -m "B" -o /var/www/html/fs.html -b "VE2RM" -r -t /root/g2_link/g2_lh.tpl VE2RM" manually ... which is likely why I don't see the status page. ?
If you look at the index.html is is frameified as expected, but there is no ?/var/www/html/fs.html .? I touched one in case the program would rather append than create, but nothing.
?
I see nothing in the logs that looks related ...
?
I *did* remember to look at netstat to see what other ports needed to have holes poked and poked them (firewall at the edge - iptables is disabled).
Except for that, it all worked as advertised - thanks to all of who have worked on the project!
?
I am currently thinking about my strategy for Cannet.? Currently, monlink handles switching us from REF069C (our default) to REF038A and back again.? Monlink, as you said, only works with DPlus reflectors so I'll need to cron the Cannet connection.
?
Is XLX044A still the "right" place for us to connect?? Or is there a "more correct" target for the Cannet? ?
?
Peter
?
?
?
On Sun, Feb 2, 2025 at 10:07?PM Terry M. Stader via <ka8scp=[email protected]> wrote:
I see it is not in Robert’s AlmaLinux version of the instructions… I’ll add it tomorrow and put the updated file in the g2_link file section of
?
Terry?
?
Terry M Stader KA8SCP
WB1GOF Repeaters Proprietor?
On Feb 2, 2025, at 10:02?PM, Terry M. Stader <ka8scp@...> wrote:
?It is there?
========
# personalize the cron.d dashboard file
# make sure to change output location to /var/www/html/
# NOTE: Non-standard gateway IP g2_lh -? reveals option
# example: -a 192.168.1.172
?
#after cron runs, new g2_link dashboard at "
=========
?
?
Terry M Stader KA8SCP
WB1GOF Repeaters Proprietor?
On Feb 2, 2025, at 9:52?PM, Peter Laws via <plaws0=[email protected]> wrote:
?
Duuuude.? Can we get that added to the readme?? I suspect that a lot of folks have normal IPs since G3(.0) came out and the 10.0.0.silly addresses are mandated any more.
?
THANK YOU! ?
?
?
On Sun, Feb 2, 2025 at 9:41?PM Terry M. Stader via <ka8scp=[email protected]> wrote:
Are you using the Icom standard 10.0.0.2 IP for the gateway? Otherwise you have to specify the IP in the cron job…
I get the error above when I run this: ?" /root/g2_link/g2_lh -m "B" -o /var/www/html/fs.html -b "VE2RM" -r -t /root/g2_link/g2_lh.tpl VE2RM" manually ... which is likely why I don't see the status page. ?
If you look at the index.html is is frameified as expected, but there is no ?/var/www/html/fs.html .? I touched one in case the program would rather append than create, but nothing.
?
I see nothing in the logs that looks related ...
?
I *did* remember to look at netstat to see what other ports needed to have holes poked and poked them (firewall at the edge - iptables is disabled).
Except for that, it all worked as advertised - thanks to all of who have worked on the project!
I am currently thinking about my strategy for Cannet.? Currently, monlink handles switching us from REF069C (our default) to REF038A and back again.? Monlink, as you said, only works with DPlus reflectors so I'll need to cron the Cannet connection.
Is XLX044A still the "right" place for us to connect?? Or is there a "more correct" target for the Cannet? ?
# NOTE: Non-standard gateway IP g2_lh -? reveals option
# example: -a 192.168.1.172
#after cron runs, new g2_link dashboard at "
=========
Terry M Stader KA8SCP
WB1GOF Repeaters Proprietor?
On Feb 2, 2025, at 9:52?PM, Peter Laws via <plaws0=[email protected]> wrote:
?
Duuuude.? Can we get that added to the readme?? I suspect that a lot of folks have normal IPs since G3(.0) came out and the 10.0.0.silly addresses are mandated any more.
THANK YOU! ?
On Sun, Feb 2, 2025 at 9:41?PM Terry M. Stader via <ka8scp=[email protected]> wrote:
Are you using the Icom standard 10.0.0.2 IP for the gateway? Otherwise you have to specify the IP in the cron job…
I get the error above when I run this: ?" /root/g2_link/g2_lh -m "B" -o /var/www/html/fs.html -b "VE2RM" -r -t /root/g2_link/g2_lh.tpl VE2RM" manually ... which is likely why I don't see the status page. ?
If you look at the index.html is is frameified as expected, but there is no ?/var/www/html/fs.html .? I touched one in case the program would rather append than create, but nothing.
?
I see nothing in the logs that looks related ...
?
I *did* remember to look at netstat to see what other ports needed to have holes poked and poked them (firewall at the edge - iptables is disabled).
I see it is not in Robert’s AlmaLinux version of the instructions… I’ll add it tomorrow and put the updated file in the g2_link file section of groups.io
# NOTE: Non-standard gateway IP g2_lh -? reveals option
# example: -a 192.168.1.172
#after cron runs, new g2_link dashboard at https://your_ip_here/fs.html"
=========
Terry M Stader KA8SCP
WB1GOF Repeaters Proprietor?
On Feb 2, 2025, at 9:52?PM, Peter Laws via groups.io <plaws0@...> wrote:
?
Duuuude.? Can we get that added to the readme?? I suspect that a lot of folks have normal IPs since G3(.0) came out and the 10.0.0.silly addresses are mandated any more.
THANK YOU! ?
On Sun, Feb 2, 2025 at 9:41?PM Terry M. Stader via <ka8scp=[email protected]> wrote:
Are you using the Icom standard 10.0.0.2 IP for the gateway? Otherwise you have to specify the IP in the cron job…
I get the error above when I run this: ?" /root/g2_link/g2_lh -m "B" -o /var/www/html/fs.html -b "VE2RM" -r -t /root/g2_link/g2_lh.tpl VE2RM" manually ... which is likely why I don't see the status page. ?
If you look at the index.html is is frameified as expected, but there is no ?/var/www/html/fs.html .? I touched one in case the program would rather append than create, but nothing.
?
I see nothing in the logs that looks related ...
?
I *did* remember to look at netstat to see what other ports needed to have holes poked and poked them (firewall at the edge - iptables is disabled).
On Feb 2, 2025, at 9:52?PM, Peter Laws via groups.io <plaws0@...> wrote:
?
Duuuude.? Can we get that added to the readme?? I suspect that a lot of folks have normal IPs since G3(.0) came out and the 10.0.0.silly addresses are mandated any more.
THANK YOU! ?
On Sun, Feb 2, 2025 at 9:41?PM Terry M. Stader via <ka8scp=[email protected]> wrote:
Are you using the Icom standard 10.0.0.2 IP for the gateway? Otherwise you have to specify the IP in the cron job…
I get the error above when I run this: ?" /root/g2_link/g2_lh -m "B" -o /var/www/html/fs.html -b "VE2RM" -r -t /root/g2_link/g2_lh.tpl VE2RM" manually ... which is likely why I don't see the status page. ?
If you look at the index.html is is frameified as expected, but there is no ?/var/www/html/fs.html .? I touched one in case the program would rather append than create, but nothing.
?
I see nothing in the logs that looks related ...
?
I *did* remember to look at netstat to see what other ports needed to have holes poked and poked them (firewall at the edge - iptables is disabled).