g2_link and monlink
2
Here is a challenge… 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
|
Hotspots ...
4
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. -- Peter Laws - VE[23]UWY / N5UWY Admin VE2RM Admin W5TC (ret.)
|
timeout ...
19
timeout... no reply from g2_link ... 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). And yes, g2_link is running. [root@dstar-gw g2_link]# systemctl status g2_link ● g2_link.service - g2_link Service Loaded: loaded (/etc/systemd/system/g2_link.service; enabled; preset: disabled) Active: active (running) since Sun 2025-02-02 19:27:25 EST; 18min ago Main PID: 1541 (g2_link) Tasks: 1 (limit: 48201) Memory: 15.9M CPU: 2.367s CGroup: /system.slice/g2_link.service └─1541 /root/g2_link/g2_link /root/g2_link/g2_link.cfg Feb 02 19:27:25 dstar-gw systemd[1]: Started g2_link Service. -- Peter Laws | VE[23]UWY / N5UWY | plaws0 gmail com | Travel by Train!
|
Cannet
5
Good evening, So the earlier error that I was having with persistent linking turned out to be self induced, the XRF reflector I was trying to connect in a persistent way to was misspelt. My excuse is that the linux terminal font was small and I was having trouble reading it. Grumble grumble.... But I was using the Cannet cron job to connect to XRF044A as the cron job does and 80 to 90 percent of the folks talking to net control were unheard at our end. Is it because we were using an unsanctioned reflector or is this something that I'll have to take another look at on our gateway computer? Anyone have any idea's Hans Oeste/VE7OES SysOp VE7VIC.
|
D-Star Install error
2
Good evening gentlemen, Just thought I'd report in the install of the DStar install on a new computer for VE7VIC. It all went swimmingly and showed no errors in the installation log on the new computer. Except that when a user called in it did not show on the dashboard. So I had a look at the log files in /var/log and found that there was some complaining in dsgwd.log where it was complaining about DNS_MAC as being invalid. Luckily I had made copies of the /opt and /dstar directories before I shutdown the old machine and took that home with me to look at. since it appeard to be complaing about the 10.0.0.1 connection, I looked that up in my backup files and found a completely different MAC address than what was currently in the /opt/products/dstar/dstar_gw/dsgwd/dsgwd.conf file. Putting the 'old' MAC address in appears to have fixed the issue. I'm not enough of a Linux guru to know why this happened but I thought I'd report this as a sticking point. Hans Oeste/VE7OES SysOp for VE7VIC
|
DStar Installation error
Sorry folks for the spam earlier, sent to the wrong group; was meant to go the the dstar-admin group. Again my apologies. That said, I do have an issue with g2_ink. I installed it using the instruction set from Robert Gillis without too much difficulty. But at the end of it I have one issue.. Persistent link doesn't appear to work. I am able to trigger a link to XRF405A on our B module, where it's logged in /var/log/g2_link.log and also in /tmp/persistent_link.log, but after a while the link gets unlinked. ie it's not persistent... I've also got the link request in the /root/g2_link/g2_link/g2_link.cfg file, but get no results. ie doesn't even appear to attempt to create the link Yet it worked on the old system quite handily. Anyone have any suggestions on where I could/should be looking to fix this issue? Thanks! Hans Oeste/VE7OES SysOp VE7VIC
|
Almalinux 9.5 and g3-lh and g3-link ..... I'm nearly done
I see that whoever put up on github the old g2-link/g2-lh has an old version (from my perspective) of g2-lh. I have gotten my almalinux 9.5 and the build setup for these running. my last version of g2-lh ver 2.10 also uses ctemplates and the latest version of ctemplates seems to compile (with a few warnings I have not checked out). In order to change the look of the dashboard as I did I needed to modify the g2-lh which took me to ver 2.10. My last reworked version of g2-link was 3.18 where I had added a LOT of debugging and improved logging. None of that has yet to be put into g2-link v4.00. I am working on this insertion now. mostly copy and paste. I never liked the dplus-style dashboard and when I did my work long ago on g2-lh I "cured" all that. And since ctemplates was a part of it then "my" template, representing the way I changed the look of the dashboard, is what I will be bringing forward. I hope others will either use this or they can edit the template to make it look the way they want and maybe have to recompile g3-lh accordingly. you can see (left side) the template result of that dashboard here on my old G2 system still running. Note this is running g2-lh 2.10 and g2-link 4.00 !! The rework I'm doing is on a replacement server for this D-STAR gateway. https://72.19.163.99/ you will note that this gateway has a dual linker, g2-link and dplus and their dashboards both show. to make things VERY clear on these new linker and dashboard what would you suggest the versions I should call g3-link and g3-lh ??? Maybe 5.x for both? or 1.x indicating starting over for g3?? I'm not a contemporary linux package guy so I have never put these into a package. Once I'm done and tested maybe one of you can assist me in making a package.... regards rich On 10/25/24 2:50 PM, Peter Laws via groups.io wrote: You da man but ... On Fri, Oct 25, 2024 at 4:46 AM Terry M. Stader via groups.io <ka8scp@...> wrote: github.com Terry M Stader KA8SCP WB1GOF Repeaters Proprietor On Oct 24, 2024, at 10:42 PM, Robert Gillis <robert@...> wrote: ? Hi Rich, My apologies for not replying sooner, I only discovered this email tonight (I filter my groups.io email to a separate folder, and I have been quite busy lately and haven't had a chance to go through them until now. Work has a way to get in the way of my hobbies it seems ? ). Have you already got this work done as you describe below? I think rebranding g2_link as g3_link is not a bad idea and would be more reflective that it works with the g3 system. I believe in another email thread in the past you--or perhaps it was someone else--suggested that we advocate for creating a GitHub repository with the source code. I agree it would help with current and future development. While I understand the original developer of g2_link did not want the code shared publicly, which I can (and will) respect, I can't help but wonder if they would consent to having it on a private GitHub repository? or perhaps their views have changed and don't mind making it open source? I have since cleaned up my documentation of typos and made a couple of very minor tweaks for the work I have done. I was planning to re-package and update the file on my website along with re-sending the instructions (again, only minor edits) to this group—but I cant help but wonder if I should start a GitHub repository for the work I have done (with the intent of it becoming a future home for g2_link (er, g3_link?) development. I suspect there would be no concern uploading the code for g2_lh to this repository, as the code for it can be downloaded openly now (and it is complied as part of the g2_link install). Regardless, I would want to track down the original developer of g2_lh to confirm. Thanks, Rob From: [email protected] <[email protected]> on behalf of Rich Painter <painterengr@...> Sent: October 16, 2024 12:36 To: [email protected] <[email protected]> Subject: Re: [g2-link] g2_link + AlmaLinux - almost there! - challenge with g2_lh Rob, I'm just starting my g3 rework for g2-link and g2-lh on almalunux 9. I am preparing a server to go up o
|
Can I change the path (Re: [g2-link] File Notifications
2
#file-notice
I never changed the subject when I replied a couple of weeks ago so folks probably missed it. Anything? :-) On Sat, Dec 28, 2024 at 1:45 PM Peter Laws via groups.io <plaws0@...> wrote: > > On Sat, Dec 28, 2024 at 10:19 AM Group Notification <[email protected]> wrote: > > > > The following items have been added to the Files area of the [email protected] group. > > > > /AlmaLinux_g2link_instructions.txt. > > > > So much work - thanks all, especially VY1RG. > > What I wanted for xmas was someone with packaging skillz (alas I have > none and I don't count that one Solaris pkg I made because the build > script had an option to make it) who would come up with RPM(s) that > would allow installation without having to install the Development > Tools group. Alas, I have given in and there are 81 or so more RPMs > on our system ... :-/ > > I see that the base directory is /root, e.g., > > # Lets create standard directories > cd / > mkdir /root/g2_link > mkdir /root/my_scripts > mkdir /root/alma_temp # create temp working directory for > AlmaLinux specifics > mkdir /root/g2_link_downloads # create temp working directorr for downloads > > With most other things D-STAR installed in /dstar can I change the > "/root" above to "/dstar? Yes, there is stuff in /opt/products and > /opt/dstarmon, but I'm ignoring those for now. > > I see that alma_temp and g2_link_downloads go away per the > instructions but g2_link and my_scripts do not. If I am careful, can > I move g2_link under /dstar and then my_scripts under what would then > be /dstar/g2_link/my_scripts? > > > Peter -- Peter Laws | VE[23]UWY / N5UWY | plaws0 gmail com | Travel by Train!
|
File Notifications
2
#file-notice
The following items have been added to the Files area of the [email protected] group. /AlmaLinux_g2link_instructions.txt By: Terry M. Stader <ka8scp@...> Description: g2_link AlmaLinux installation instructions. The following items have been updated in the Files area of the [email protected] group. //AlmaLinux_g2link_instructions.txt By: Terry M. Stader <ka8scp@...> Description: g2_link AlmaLinux installation instructions. Version G3 0.3b - Robert Gillis - VY1RG The following items have been added to the Files area of the [email protected] group. /g3_icom_setup_doc.txt By: Terry M. Stader <ka8scp@...> Description: # CENTOS 7.x (32/64 bit) installation # Standard ICOM G3 Installations ONLY # # Version G3 0.1 - Terry Stader-KA8SCP based on Ramesh Dhami-VA3UV's v.6 for G2 release
|
g2_link disconnects link
11
Ive followed the recent "recipe" for setting up G2-Link on an Almalinux G3 system. It seems to be almost working, in that I can connect to an XLX reflector but after about a minute it unlinks automatically. Timeout is currently set to 10 minutes (was previously no timeout), but either way, this what I see in the G2-link.log Any clues as to where I should go next? 120924 at 16:44:59:sending link request from mod B to link with: [XLX252 ] mod A [45.77.227.69] 120924 at 16:44:59:Connected from: XLX252 120924 at 16:45:02:sending File:[/root/g2_link/linked.dat], mod:[B], RADIO_ID=[LINKED XLX252 A ] 120924 at 16:45:03:finished sending File to mod:[B] 120924 at 16:45:50:Unlinked from [XLX252 ] mod A, TIMEOUT... 120924 at 16:45:53:sending File:[/root/g2_link/unlinked.dat], mod:[B], RADIO_ID=[UNLINKED TIMEOUT ] 120924 at 16:45:54:finished sending File to mod:[B]
|
Instructions for g2_link 4.00 install on AlmaLinux (updated)
2
Please find my updated notes attached (and copied below). The following was updated Notes are updated for 80char width, allows for easier viewing. Fixed many Typos throughout the document. minor fixes updated in ioClarity download file to address fixes in scripts / cronjobs. -------- -- # This is not a script, but this is the recipe VY1RG used to install g2_link # alongside of dplus on Alma Linux. Most of this document/hard work was done # by others, I simply tweaked a few things to make it work/install on Alma as # described below. # # Thank you to everyone who has contributed before me. ############################### ## FREE STAR* g2_link XRF/DCS Linking Tool Installation ############################### # # Pre-Requisites... # NOTE: This is for G3 version 3.2! # AlmaLinux Installation # Standard ICOM G3 version 3.2 Installations ONLY # # Version G3 0.3b - Robert Gillis - VY1RG, fixed a few typos # Version G3 0.3a - Robert Gillis - VY1RG, fixed a few typos # Version G3 0.3 - Robert Gillis - VY1RG, based on the work of # Terry Stader-KA8SCP, which was based on the work of # Ramesh Dhami-VA3UV's v.6 for G2 release # # Ramesh@... / Terry - ka8scp@... / Robert - robert@... # # Must install all as root ################################ ## Setting up the environment ## ################################ # Install Development Tools" on minimal AlmaLinux via dnf. This is required for # compiling of one of the utilities (g2_lh), that is used to create the # dashboard. dnf group install "Development Tools" -y # also dos2unix & nmap dnf install dos2unix nmap -y # also postfix, if you want to use the email notification script for new user # signups -- This is not related to g2_link, but a handy script if your gateway # registers users for US TRUST dnf install postfix -y # Lets create standard directories cd / mkdir /root/g2_link # Dir for g2_link binaries, etc. mkdir /root/my_scripts # Dir for scripts that interact with g2_link mkdir /root/alma_temp # Temp working directory for AlmaLinux specifics mkdir /root/g2_link_downloads # Temp working directory for downloads # Download what we need to cd /root/g2_link_downloads wget https://ioclarity.ca/ioClarity_g2_link_alma.tgz wget http://www.va3uv.com/hp/free_star_icom.zip wget http://va3uv.com/hp/g2_lh.zip wget https://github.com/OlafvdSpek/ctemplate/archive/refs/tags/ctemplate-2.4.zip # Extract the ioClarity files provided by VY1RG cd /root/alma_temp tar xvf /root/g2_link_downloads/ioClarity_g2_link_alma.tgz # Copy the scripts to the my_scripts directory cp /root/alma_temp/my_scripts/* /root/my_scripts # Extract the core g2_link files cd /root/g2_link unzip /root/g2_link_downloads/free_star_icom.zip ## Extract - Configure - Install cTemplate ## - This is required by g2_lh, which is a prereq for the g2_link dashboard ## - (I could not find a precompiled version fro Alma, so lets make it) cd /root/alma_temp unzip /root/g2_link_downloads/ctemplate-2.4.zip cd ctemplate-ctemplate-2.4/ ./autogen.sh && ./configure make make install ## Extract - Patch - Compile the g2_lh files mkdir /root/alma_temp/g2_lh cd /root/alma_temp/g2_lh unzip /root/g2_link_downloads/g2_lh.zip # Apply VY1RG's 2.04a g2_lh patch # Without this patch, on AlmaLinux with G3 version 3.2, g2_lh will segfault # every now and then, which will then cause g2_link to crash. Your want to # apply this patch g2_lh.cpp /root/alma_temp/oddsAndEnds/g2_lh_204a.patch cp g2_lh.cpp /root/g2_link/g2_lh.cpp # Copy an updated version of g2_link dashboard template to the right place cp /root/alma_temp/oddsAndEnds/g2_lh.tpl /root/g2_link/g2_lh.tpl # Compile g2_lh cd /root/g2_link g++ -g -o g2_lh g2_lh.cpp /usr/local/lib/libctemplate_nothreads.a ########################### ## Configuration ## ########################### # Okay, stage is set, lets configure # Copy and review the scripts in /root/my_scripts cp /root/alma_temp/my_scripts/* /root/my_scripts # These scripts are executed by cronjobs as described below # # Review the above scripts for the ones you may want to use and modify # accordingly. For example, if auto-connecting to cannet, ensure
|
G2-Link Install please?
5
Good Morning All, I’ve recently set up a new Repeater and gateway for Houston, Texas (N5BDJ) on Icom G3 repeater. The gateway is running on AlmaLinux with G3, and I’d like to explore using G2-Link to have new dashboard/Dplus and more important functionality and connect to XLX250. Additionally, we have another repeater running C4FM that I’d like to link to XLX250 through this setup. Could you please provide the necessary files and steps for installation of the G2-Link? Thank you in advance for your assistance! 73 Fred Joly
|
g2_link + AlmaLinux - almost there! - challenge with g2_lh
10
Hi There, so close.... I have been working away getting g2_link running on AlmaLinux alongside DPlus G3 version 3.2, and am getting pretty close. I have g2_link and dtmf_reader converted to systemd services, and have them both running successfully (wahoo). However, it seems I am running into one last hurdle and I am hoping someone with a bit more recent Linux development experience can help me out with. This is something I can tinker with in my spare time, but I don't have much spare time lately. If there are any C++ / Linux development guru's out there that have experience I have no doubt they can figure it out much quicker than I can. The issue I am running into is that the g2_lh program (which is executed frequently to build the dashboard) will sometimes crash, causing g2_link to crash as described below. I have the systemd service I created to restart the service when it crashes, but of course if there was a pre-established link it drops and will need to be reestablished. Here are the details of what is happening: sometimes, when g2_lh executes, it crashes it core-dumps with the following (from /var/messages): Sep 5 09:30:02 vy1rds-gw2 kernel: g2_lh[126886]: segfault at 448001 ip 00007f18eb159755 sp 00007ffc613cd4a8 error 4 in libc.so.6[7f18eb028000+175000] likely on CPU 0 (core 0, socket 0) Sep 5 09:30:02 vy1rds-gw2 kernel: Code: 0f b6 44 07 e0 29 c8 c5 f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 83 fa 01 76 7b 89 f8 09 f0 25 ff 0f 00 00 3d e0 0f 00 00 7f 2b <c5> fe 6f 16 c5 ed 74 17 c5 fd d7 c2 ff c0 c4 e2 68 f5 d0 0f 85 d2 Sep 5 09:30:02 vy1rds-gw2 systemd[1]: Started Process Core Dump (PID 127638/UID 0). Sep 5 09:30:02 vy1rds-gw2 systemd-coredump[127639]: Resource limits disable core dumping for process 126886 (g2_lh). Sep 5 09:30:02 vy1rds-gw2 systemd-coredump[127639]: Process 126886 (g2_lh) of user 0 dumped core. Sep 5 09:30:02 vy1rds-gw2 systemd[1]: systemd-coredump@...: Deactivated successfully. Shortly after, g2_link crashes (from /var/messages) Sep 5 09:30:52 vy1rds-gw2 kernel: g2_link[126542]: segfault at ae15ae9a ip 00000000f7ca84a3 sp 00000000fffc2d0c error 4 in libstdc++.so.6.0.29[f7c78000+123000] likely on CPU 2 (core 0, socket 0) Sep 5 09:30:52 vy1rds-gw2 kernel: Code: 66 90 66 90 66 90 90 f3 0f 1e fb 8b 54 24 04 8b 42 0c 85 c0 74 11 90 89 c2 8b 40 08 85 c0 75 f7 89 d0 c3 8d 74 26 00 8b 42 04 <3b> 50 0c 75 1b 8d b4 26 00 00 00 00 90 89 c2 8b 40 04 39 50 0c 74 Sep 5 09:30:52 vy1rds-gw2 systemd[1]: Started Process Core Dump (PID 127773/UID 0). Sep 5 09:30:52 vy1rds-gw2 systemd-coredump[127774]: Resource limits disable core dumping for process 126542 (g2_link). Sep 5 09:30:52 vy1rds-gw2 systemd-coredump[127774]: Process 126542 (g2_link) of user 0 dumped core. Sep 5 09:30:52 vy1rds-gw2 systemd[1]: systemd-coredump@...: Deactivated successfully. In /var/log/g2_link, this is the error that happens right before the g2_link segfault: 090524 at 09:30:52:call=1NFO timeout, removing 10.0.0.2, users=0 It seems to me, that g2_lh is crashing, which then has the cascading effect into g2_link. While I have the c code for g2_lh which I can try to debug as time permits, I do not have the code for g2_link, so I cant look into that side. It has been a long time since I analyzed core dumps, but I am willing to try. If anyone wants to see the core dumps to analyze, I will happily enable core dumping for these services and send them over for their analysis. Rob, VY1RG
|
G2-Links
4
We have had G2_link and Dplus running on K2BWK for several years. Something that has been bugging me is that Links don't show up on the G2 page but do on the DPlus page. Is that the way it is supposed to be or do I have something configured wrong. 73 Steve KD2OM Admin K2BWK
|
Instructions for g2_link 4.00 install on AlmaLinux
8
Hi g2_link admins, As you have seen by some recent posts of mine, I have been working on getting g2_link working alongside of the new dplus G3 version 3.2 on an AlmaLinux install. I think I worked out all the kinks and I documented the install by creating the attached "recipe". These instructions should work for other admins as well assuming they have a working dplus G3 version 3.2 system running on AlmaLinux. Please note: My attached instructions does not document the multiple options for dashboards, it just documents what I used on VY1RDS. I do not used the supplied "my_scripts" or "cron" that was on va3uv's website, I used slightly modified versions as described in the next bullet point. For the specific bits that are different than previous installs (some described below), I created a new tar file and place it on my website for download. This is included in the attached documentation. These files include: modified crontab entries, disabled by default except the update_gwys one. systemd services for use in AlmaLinux slightly modified "my_scripts", and additional specific scripts I created for email notifications when new users register (work in progress, but mostly works), as well as a backup script that backups up g2_link config, dplus, and ircddb3 (if installed) some customizations used on the vy1rds dashboard patch file for g2_lh, to stop it from crashing (as per my last email, I still need to investigate why the condition comes up that was causing it to crash to begin with) Please feel free to pick my work apart, reuse any or all of it, and/or re-incorporate any bits and pieces of this recipe or my tar file in official documentation for g2_link (assuming it actually works on other gateway installs--it should). I will be following this recipe on a backup gateway I will be building shortly, so if I notice any errors at that time I will update and resend. Feedback welcome. Enjoy, Rob, VY1RDS
|
XLX reflectors - X shell script option
2
While messaging with another D-STAR admin, about the coexistence of dplus and g2_link and how it used to be with a single command structure. Oh well. It did give me an idea.... dplus supports using 0-9 and A-Z in the 7th position and X in the 8th spot to execute a shell script. So maybe we can make it easier for users to use dplus to change to an XRF/DCS reflector? I created a test script, exec-U.sh in the /dstar/scripts directory, made it executable with the chmod +x command: =========================== #!/bin/bash # script to automatically connect # A port connect to DCS351D using the g2_link tool # disconnect first /usr/bin/nc -u -w 1 10.0.0.2 30003 <<EOF um A EOF # sleep 3 # disconnect dplus echo " U" >/dstar/tmp/link-a # sleep 3 # first connect with netcat to port # then connect to DCS351D /usr/bin/nc -u -w 1 10.0.0.2 30003 <<EOF lm ADCS351D EOF exit 0 ===================== I then added a new entry in to the DV memory of my ID-51A with a NAME of whatever you want and then the CALL SIGN:______UX (6 spaces, the U and then an X) Transmitted to the repeater: ==> dplus.log <== User update (KA8SCP ) rpt (WB1GOF C) 2022/09/22 12:51:16.303 Remote client forward start streamid 3932 2022/09/22 12:51:16.312 rpt2 (WB1GOF G) rpt1 (WB1GOF C) urcall ( UX) mycall (KA8SCP /ID51) Exec start streamid 3932 2022/09/22 12:51:16.312 rpt2 (WB1GOF G) rpt1 (WB1GOF C) urcall ( UX) mycall (KA8SCP /ID51) user message (Terry - Westford MA ) mycall (KA8SCP ) streamid 3932 Stream end streamid 3932 cnt 45 missed 0 elapsed 00:01 2022/09/22 12:51:17.165 exec file /dstar/scripts/exec-U.sh submitted ==> g2_link.log <== 092222 at 12:51:17:Received command [um A] from [10.0.0.2] 092222 at 12:51:17:cmd=[um], parameter=[A] 092222 at 12:51:17:Unlinking from [DCS351 ] mod D 092222 at 12:51:20:sending File:[/root/g2_link/unlinked.dat], mod:[A], RADIO_ID=[UNLINKED ] ==> dplus.log <== Reading link file /dstar/tmp/link-a for 'A' streamid 2e4d 2022/09/22 12:51:20.464 Reflector/Gateway unlink request streamid 2e4d 2022/09/22 12:51:20.464 rpt2 (WB1GOF G) rpt1 (WB1GOF A) urcall ( U) mycall (WB1GOF / ) playfile /dstar/dv/alreadyunlinked.dvtool to A Adding message >Not Linked < to /dstar/tmp/play-a.dvmsg playfile mod 0 tvs/u 1663865481/465050 tvps/u 0/699660 timediff 1713137214 Reading file /dstar/tmp/play-a.dvtool to 'A' streamid 2b71 2022/09/22 12:51:21.465 Read msg file for playback rpt2 (WB1GOF A) rpt1 (WB1GOF G) urcall (CQCQCQ ) mycall (WB1GOF /RPTR) Finished reading file /dstar/tmp/play-a.dvtool to 'A' streamid 2b71 2022/09/22 12:51:21.465 Play file recall to module A stream 2b71 ==> g2_link.log <== 092222 at 12:51:21:finished sending File to mod:[A] 092222 at 12:51:23:Received command [lm ADCS351D] from [10.0.0.2] 092222 at 12:51:23:cmd=[lm], parameter=[ADCS351D] 092222 at 12:51:23:sending link request from mod A to link with: [DCS351 ] mod D [45.33.127.97] ==> dplus.log <== OK ==> g2_link.log <== 092222 at 12:51:23:Connected from: DCS351 092222 at 12:51:26:sending File:[/root/g2_link/linked.dat], mod:[A], RADIO_ID=[LINKED DCS351 D ] 092222 at 12:51:27:finished sending File to mod:[A] ================================================ Still working on trying to figure out why an XLX reflector request times out. -- Terry Stader - KA8SCP D-STAR Gateway & Reflector Admin
|
g2_link and alma - success
2
Hi There, I haven't seen too much out there about people successfully installing g2_link alongside a new AlmaLinux install, but I wanted to share that I successfully upgraded our local repeater (VY1RDS) this evening to AlmaLinux, the latest iCom gateway/dplus software, ircddb addon--and, just now, I had a working g2_link manually running with it as well I verified quickly by linking/unlinking to XRF reflectors, and verified I was getting though to the reflector. I used the same binary package that I was using on CentOS. Over the next week, I plan to convert the services from the old format to systemd, and make things automatic (again, I was just running the g2_link manually this evening with a few script modifications) as well as make sure I can get the FreeStar dashboard up and running, etc. I hope to have this all done before mid-September, but if I do not get around to it (that day job of mine and kids sure do take up a lot of my time), I will put this work on pause until early October as I am away the last two weeks of September with no communications. Before I work on converting the services over / documenting everything that I did to get g2_link working (which didn't involve too much modification) I wanted to verify that no one else has already done / shared this? Based on my preliminary searching, I have not found anything along these lines. Rob, VY1RG
|
Status of g2_link
7
So ... VA3UV. Has he given up the G2_link project? If yes, then where does that leave us? I do note that it's G2_link and not G3_link, so if the "G" relates to the Icom bits, now G3.2, does this mean it's pretty old? I don't have the software (I know - I haven't asked The Right Guy - it's fine) so don't know what it consists of. If it's scripts, we can probably make do. If it's binaries and we have no source ... Peter -- Peter Laws | VE[23]UWY / N5UWY | plaws0 gmail com | Travel by Train!
|
Alma and g2_link
8
Good day everyone. With the release of G3.2 supporting Alma 9 as Icom moves away from the EOL of Centos 7, it looks like we need to address the future of g2_link. I am not a “coder”. I can look at code and read it well enough, but I do not know where to begin in a migration from Centos 7 to Alma 9 and g2_link. Is there anyone in the group that has some knowledge in this vein? Or even knows someone who would take a look at the task? Any thoughts? Terry KA8SCP -- Terry Stader - KA8SCP D-STAR Gateway & Reflector Admin
|
g2_link.service
2
Did anyone come up with a AlmaLinux version of the init.d “service” file for g2_link? Terry -- Terry Stader - KA8SCP D-STAR Gateway & Reflector Admin
|
1 - 20 of 47