开云体育

Hello all, XRF038 is now co-located with XRF021 in the MI datacenter. Last night XRF038 was brought online and Ramesh added to IP to his database. FreeStar/g2_link systems that pull updates from the VA3UV site will have the new IP. The dashboard has some new information for end users to see how they connect to this XRF... check it out at http://44.103.34.19/XRF038_status.html Hoping all the pi-star users will see an update with the new IP very soon. Enjoy D-STAR Terry-KA8SCP

Nice... thanks William. I will post it to the G2-link groups.io support page for others to tap in to. I saw that the cert had expired and found the new ones on the opendstar site but had not yet done anything to update our systems. This is perfect. I’ll check with Brian of the USTRUST and see if he wants to release something like this to the G3 admins if you are ok with sharing this with the larger audience? Terry Sent from an Apple device

I recently revised the Dstar.do page for VE7VIC to address a few questions/concerns we often get with new users... take a look at http://ve7vic.dstargateway.org/Dstar.do Also with the email notification of new registrations pending, when you validate and approve them... most of us send the new registrant an e-mail letting know to do the next steps... send them to a page like http://ve7vic.dstargateway.org/registration.html We had put in the revised g2_lh.tpl to add the narrative at the bottom of the g2_link dashboard... again, take a look at VE7VIC https://ve7vic.dstargateway.org/ Let me know if you have an interest... I can upload them to the Files section of the group page. Terry Terry M Stader KA8SCP WB1GOF Repeaters/D-STAR Admin

FYI Terry M Stader KA8SCP WB1GOF Repeaters/D-STAR Admin Begin forwarded message: -- Terry Stader - KA8SCP D-STAR Gateway & Reflector Admin

Thought this message might be more appropriate to the g2_link group? Terry M Stader KA8SCP WB1GOF Repeaters/D-STAR Admin Begin forwarded message: -- Terry Stader - KA8SCP D-STAR Gateway & Reflector Admin

The following files have been uploaded to the Files area of the [email protected] group. /g2_link_announce.ZIP By: Terry M. Stader Description: Two sh files... one for B and one for C modules. Each one will announce via voice and data what the link status is at the time the command was issued. ZIP'd file contains 2 scripts: announce-b.sh and announce-c.sh. Use a crond file to schedule at the timing you'd like.

From: Ramesh Dhami <Ramesh@...> Sent: Sunday, April 25, 2021 8:52 AM To: undisclosed-recipients: Subject: Pending Retirement of XLX005 .... Introducing XLX405 Hi All: XRF005 will soon be retiring; this could be as soon as April 30th. This email contains some important information to minimize the impact to our long-standing supporters and users of XRF005: If you have a repeater or hotspot that regularly connects to XRF005 Please change your default to XLX405. XLX405 "A" is running the latest XLXD software (supporting D-Extra, D-Plus, and DCS clients). XLX405 "A" is peered with XLX044 A and the rest of the FREE STAR* Hub. The dashboard for XLX405 is accessible here: http://xlx405.va3uv.com Changes to FREE STAR* Callsign Server (For DVTool and DVAPTool Users) With the pending retirement of the XRF005 server, the FREE STAR* Callsign Server has also been moved (the old one on XRF005 is still running during the transition period). The Callsign server is hosted on the same XLX405 server. Users that previously modified their Host file will need to update them as follows: The Windows hosts file can be found here: Windows 95/98/Me c:\windows\hosts Windows NT/2000/XP Pro c:\winnt\system32\drivers\etc\hosts Windows 10 -> c:\windows\system32\drivers\etc\hosts The following entries need to be added to the hosts file; we recommend using WORDPAD. #FREE STAR* callsign server redirect 35.182.9.157 dstarns.dstargateway.org 35.182.9.157 dstarns.opendstar.org ICOM G2/G3 Systems running g2_link We are now building the gwys.txt file (used by g2_link) based on the host files used by Pi-Star. This allows us to provide a much 'richer' gwys file and also ensures consistency. g2_link uses a script (get_gwy_list.sh - depending on your installation, this may either be in the /root/g2_link folder OR in /root/my_scripts) to get the gwys.txt file from my website. Please change this such that the file is now retrieved from the XLX405 server - i.e: Replace: wget http://www.va3uv.com/gwys.txt With: wget http://xlx405.va3uv.com/gwys.txt Save / Exit - you can manually run the script to pull the new gwys file, if you wish, otherwise it will be pulled via the nightly cron. FREE STAR* HUB and YSF Connectivity The new XLXD Software includes a built-in DMR and YSF bridge. This is good since we were able to decommission the old YSFReflector that often needed a manual reset. The downside is that we seem to have lost our former YSF room 'YSF36010'; the new software has us bridged to YSF 17206. We are still trying to get YSF36010 'back' - but are losing hope since the two sides (XLX and YSF seems to be referring us to each other to solve this!). So until further notice, YSF users wanting to connect to the FREE STAR* Hub should connect to YSF 17206. I hope I have not left anything out, please let us know if you have any questions. Between Terry, Denis, and myself, one of us should be able to answer them! Cheers, Ramesh. -- Terry Stader - KA8SCP D-STAR Gateway & Reflector Admin

?Hello all, After the rollout of the new location for getting the g2_link gwys.txt file, we heard back from several of the admins that the list was incomplete. As you may recall, we grabbed data from the Pi-Star host lists at: http://www.pistar.uk/downloads/DExtra_Hosts.txt http://www.pistar.uk/downloads/DCS_Hosts.txt http://www.pistar.uk/downloads/DPlus_Hosts.txt http://www.pistar.uk/downloads/XLXHosts.txt And merged and sorted it to http://xlx405.va3uv.com/gwys.txt It turns out that Pi-Star was not capturing some of the D-STAR gateways. So we have added in an output from a USTRUST Postgres database and have included that in the mix. Today’s file is a culmination of that merge of data. Thanks for those that offered their feedback and assistance. Also... a quick note to g2_link admins... even though there are XLX reflectors listed in the gwys.txt file, g2_link does NOT respond to a prefix of XLX. g2_link will ONLY respond to XRF and DCS prefixes. The use of wXLXyyyz in the cfg file also will not work. We recommend using the XRF (30001) protocol to make link requests to the XLX multimode reflectors. Terry KA8SCP Ramesh VA3UV -- Terry Stader - KA8SCP D-STAR Gateway & Reflector Admin

The GB7NA Repeater in the UK is running with G3. The sysop 'Ernie' believes that there is a provision to set a default reflector and to set a timeout return. However I am doubtful. Would anyone know the answer whether it does or does not please?

FYI Terry M Stader KA8SCP WB1GOF Repeaters/D-STAR Admin Begin forwarded message: From: Ramesh Dhami <Ramesh@...> Date: November 13, 2021 at 12:52:27 PM EST To: Allan Boyd <ve3ajb@...> Cc: "Terry M. Stader - KA8SCP" <ka8scp@...>, denbedard@... Subject: XLX405 Rebuilt ?Hi Al: Seems as though we were seeing hard-drive errors on XLX405 - very odd, since this is (was!) in an AWS DC. Terry is seeing the same on some of his reflectors. What does this tell you abut AWS hard-drives? ;) - or may be the non-commercial customers get the bad ones! Anyway, XLX405 has been moved to a new host in Toronto. Dashboard is here: http://xlx405.va3uv.com Host file on your G3 will update overnight. This reflector also hosts the callsign server for dongle users. NOTE - you will need to update your host file on your PC - see below for new IP: http://www.va3uv.com/dextra.htm Back to my Saturday chores! Ramesh. -- Terry Stader - KA8SCP D-STAR Gateway & Reflector Admin

Hello again... Quite often I get asked if we can connect to XLX reflectors with our repeater. Interesting enough, the answer appears to be probably! I wrote a little script called "xlx351d-a-start.sh": #!/bin/bash # script to automatically connect # A port to XLX351D 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 XLX351D /usr/bin/nc -u -w 1 10.0.0.2 30003 <<EOF lm AXLX351D EOF exit 0 ======================= Made it executable and then ran it. Sure enough it connected. The gateway was registered on the XLX dashboard with the DCS protocol (that is how it is supposed to be if you look at the gwys.txt file). After a minute or so, it times out. g2_link.log file shows: 091922 at 18:24:12:Received command [um A] from [10.0.0.2] 091922 at 18:24:12:cmd=[um], parameter=[A] 091922 at 18:24:18:Received command [lm AXLX351D] from [10.0.0.2] 091922 at 18:24:18:cmd=[lm], parameter=[AXLX351D] 091922 at 18:24:18:sending link request from mod A to link with: [XLX351 ] mod D [45.33.127.97] 091922 at 18:24:18:Connected from: XLX351 091922 at 18:24:21:sending File:[/root/g2_link/linked.dat], mod:[A], RADIO_ID=[LINKED XLX351 D ] 091922 at 18:24:22:finished sending File to mod:[A] 091922 at 18:25:09:Unlinked from [XLX351 ] mod D, TIMEOUT... 091922 at 18:25:12:sending File:[/root/g2_link/unlinked.dat], mod:[A], RADIO_ID=[UNLINKED TIMEOUT ] 091922 at 18:25:13:finished sending File to mod:[A] Since the XLX connection is being made as DCS 30051 UDP connection and other DCS connections stay connected: 091922 at 18:44:30:Received command [lm ADCS351D] from [10.0.0.2] 091922 at 18:44:30:cmd=[lm], parameter=[ADCS351D] 091922 at 18:44:30:sending link request from mod A to link with: [DCS351 ] mod D [45.33.127.97] 091922 at 18:44:30:Connected from: DCS351 091922 at 18:44:33:sending File:[/root/g2_link/linked.dat], mod:[A], RADIO_ID=[LINKED DCS351 D ] 091922 at 18:44:34:finished sending File to mod:[A] Wondering why the XLX version does not? -- Terry Stader - KA8SCP D-STAR Gateway & Reflector Admin

We have a number of new members in the last 2 days. There is not much message traffic, so make sure you read thru the old message, check out the file section and also the wiki. For those of you that have been here awhile, are you still running g2_link? If so, maybe you can identify the gateway/repeater you are running it on? I saw a link to a good explanation of the reflector types and the various gateway software packages on how they access the reflectors. Take a look at https://www.cnharc.org/repeaters/digital-voice/d-star-linking-and-un-linking-on-a-repeater-gateway/ Terry -- Terry Stader - KA8SCP D-STAR Gateway & Reflector Admin

Last Thursday the NT4MC DSTAR gateway computer was interrupted during an update using yum. I have been able to restore services EXCEPT for dsipsvd. Is there a way to restore the dsipsvd functionality other than a total rebuild? Thanks, Jimmy NQ4U

Good morning Rich, On my g2_link system, there is a cron job that runs every morning at 2AM where the gwys.txt as well as the valid_users.txt files are updated. Here they are: ============================= [root@wb1gof my_scripts]# cat /etc/cron.d/update_gwys 5 2 * * * root /root/my_scripts/get_gwy_list.sh > /var/log/get_gwy_list.log 2>&1 ============================= [root@wb1gof my_scripts]# cat get_gwy_list.sh #/bin/bash /root/my_scripts/create_active_users.sh cd /root/g2_link /bin/cp /root/g2_link/gwys.txt /root/g2_link/gwys.txt.bak /bin/rm -rf /root/g2_link/gwys.txt wget http://xlx405.va3uv.com/gwys.txt if [ -f /root/g2_link/gwys.txt ] then /usr/bin/nc -u -w 1 127.0.0.1 30003 <<EOF rfr EOF else /bin/mv /root/g2_link/gwys.txt.bak /root/g2_link/gwys.txt fi exit 0 ============================= [root@wb1gof my_scripts]# cat /root/my_scripts/create_active_users.sh /usr/bin/psql -d dstar_global -f /root/my_scripts/create_active_users.sql -U postgres cp /tmp/valid_users.txt /root/g2_link/valid_users.txt ============================= Hope this answers your question? Terry

Hello, my name is Darrell W8DSB. We recently suddenly lost our DStar admin (sk). I think I am going to be handling any or all of the day to day issue that might come up with the gateway. This repeater is the least used and one of the biggest sites we have. The issue is, we are all interconnected with XLX, DMR and YSF (using HBLINK) but the dstart stack only does real REF reflectors. I read that G2_link can help us connect this repeater stack to our XLX allowing for a wider group to use it. I see from reading other post that I need to request the software link ==> w8dsb@... I assume this will do what is needed to connect our hardware via the internet to our XLX server? Will this connection be static? If so, do I have to run one for each module or just one from the controller to controller? This is a low level project for me so I plan on doing a bunch of reading and trying to get it done before next fall.

Long story, but our old date repeater had a controller failure so we replaced it with a new Icom repeater (dual mode). Our old admin left the state and the replacement admin has been out of ham radio. we had an interim person who replaced the repeat and noted the GatewayServer had some non-standard ports. Due to time constraints and the lack of availability to get at the repeater, he had to beg off the project. So, now it sort of falls on me since no one else in the club is stepping up. The interim person suggested we reinstall the OS and software on the computer. I was able to get the computer from the repeater from the site and set it up at home. The power supply fan was squealing so I replaced that. Now to think about reinstalling the software. I think I have some info on CentOS and Gateway 3.1 software and reviewing that. One thing our members asked for is installing g2_link for the additional reflectors. It seems that I can get some directions here on how to do that once the g3 software is installed, so just starting that ball rolling. Thanks in advance for any help, Eric, KF0S

Just out of curiosity, where does the current g2_link package live these days as documented in /g/g2-link/files/g2_link-v4.0-QA.pdf GitHub is returning blanks. 73, K6EEN

Over the last few weeks, you may have gotten an email asking you to re-verify your subscription to this or other groups.io lists. This is a legit email and if you want to remain active, you should verify it is really you and not a bogus account. This is 开云体育’s way at taking out SPAM. Hopefully everyone is well and getting 2024 off to a good start? Terry -- Terry Stader - KA8SCP D-STAR Gateway & Reflector Admin