#160

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.

#161

开云体育

Hans, glad you found the initial issue. We’ve all done fat-fingered entries!

Regarding the Cannet… I did not tune in last night… I was working with another large regional net.?

There are multiple access points to that net these days. XRF/XLX044A is the “hub” and should be able to hear all traffic. Sometimes we will see a misconfigured user who is heard locally but not network wide.?

Below is a “map” of that network that Ramesh and I maintain. I recently (well, a year now) linked this network to a DPlus reflector, REF038A, to give non-g2_link/dextra (read stock Icom systems) machines access to the net.?

I like to tell people… to check the end to end of this… connect D-STAR to REF038A and listen on DMR BM TG 302050. You might have to kerchunk a couple of times to wake up all the nodes.

I know it does not specifically answer the “why” of your issue…. but you can try a couple connection points to see if it addresses the issue.

Terry

Show quoted text

On Feb 1, 2025, at 12:08?AM, Hans Oeste via groups.io <oeste.hanspeter@...> wrote:

?
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.

--
Terry Stader - KA8SCP
D-STAR Gateway & Reflector Admin

FreeStar_network.pdf

#162

On Sat, Feb 1, 2025 at 10:15?AM Terry M. Stader via groups.io
<ka8scp@...> wrote:

Hans, glad you found the initial issue. We’ve all done fat-fingered entries!

Regarding the Cannet… I did not tune in last night… I was working with another large regional net.

There are multiple access points to that net these days. XRF/XLX044A is the “hub” and should be able to hear all traffic. Sometimes we will see a misconfigured user who is heard locally but not network wide.

Below is a “map” of that network that Ramesh and I maintain. I recently (well, a year now) linked this network to a DPlus reflector, REF038A, to give non-g2_link/dextra (read stock Icom systems) machines access to the net.

I like to tell people… to check the end to end of this… connect D-STAR to REF038A and listen on DMR BM TG 302050. You might have to kerchunk a couple of times to wake up all the nodes.
1) thanks for REF038 - VE2RM has been Cannetting that way for some time.

2) thanks for the map!  I see we are far out in the uncharted
backwaters of the unfashionable end of the Cannet Galaxy  ...

Which brings up two questions.

Q1 - We currently use monlink to manage reflector connections.  VE2RM
is connected to REF069C by default, but switches to REF069B at drive
times durning the week and REF038A (thanks again, Terry) for Cannet.
Will monlink handle linking to XRF/XLX/etc reflectors?

Q2 - I need to get on the stick and get g2_link going.  Before our
gateway gave up a few years ago, we had that and it was well used so
as the "D-STAR guy" I need to get that going again.  I know you all
have been working and testing and fixing (thanks, all) but what is the
current "entry point" for an admin that wants to install that on a
gateway running Alma 9 / G3.2?

Peter


--
Peter Laws - VE[23]UWY / N5UWY
Admin VE2RM
Admin W5TC (ret.)

#163

笔别迟别谤…

A1 - monlink does NOT work with g2_link it only looks at the dplus.log. I will confirm that g2_link will connect to a DCS/XRF reflector when an existing REF reflector is in place. RF users cannot make a XRF/DCS connection when an REF connection exists because there is a “block” file. So be careful you don’t command line execute simultaneous connections. Audio paths won’t work… 20001 versus 30001/30051.

A2 - The command sequence for installing g2_link for 3.2 is in the Files section here.

Terry M Stader KA8SCP

Show quoted text

On Feb 1, 2025, at 1:15?PM, Peter Laws via groups.io <plaws0@...> wrote:

?On Sat, Feb 1, 2025 at 10:15?AM Terry M. Stader via groups.io
<ka8scp@...> wrote:

Hans, glad you found the initial issue. We’ve all done fat-fingered entries!

Regarding the Cannet… I did not tune in last night… I was working with another large regional net.

There are multiple access points to that net these days. XRF/XLX044A is the “hub” and should be able to hear all traffic. Sometimes we will see a misconfigured user who is heard locally but not network wide.

Below is a “map” of that network that Ramesh and I maintain. I recently (well, a year now) linked this network to a DPlus reflector, REF038A, to give non-g2_link/dextra (read stock Icom systems) machines access to the net.

I like to tell people… to check the end to end of this… connect D-STAR to REF038A and listen on DMR BM TG 302050. You might have to kerchunk a couple of times to wake up all the nodes.
1) thanks for REF038 - VE2RM has been Cannetting that way for some time.

2) thanks for the map!  I see we are far out in the uncharted
backwaters of the unfashionable end of the Cannet Galaxy  ...

Which brings up two questions.

Q1 - We currently use monlink to manage reflector connections.  VE2RM
is connected to REF069C by default, but switches to REF069B at drive
times durning the week and REF038A (thanks again, Terry) for Cannet.
Will monlink handle linking to XRF/XLX/etc reflectors?

Q2 - I need to get on the stick and get g2_link going.  Before our
gateway gave up a few years ago, we had that and it was well used so
as the "D-STAR guy" I need to get that going again.  I know you all
have been working and testing and fixing (thanks, all) but what is the
current "entry point" for an admin that wants to install that on a
gateway running Alma 9 / G3.2?

Peter


--
Peter Laws - VE[23]UWY / N5UWY
Admin VE2RM
Admin W5TC (ret.)

-- 
Terry Stader - KA8SCP
D-STAR Gateway & Reflector Admin

#164

On Sat, Feb 1, 2025 at 3:11?PM Terry M. Stader via groups.io
<ka8scp@...> wrote:

笔别迟别谤…

A1 - monlink does NOT work with g2_link it only looks at the dplus.log. I will confirm that g2_link will connect to a DCS/XRF reflector when an existing REF reflector is in place. RF users cannot make a XRF/DCS connection when an REF connection exists because there is a “block” file. So be careful you don’t command line execute simultaneous connections. Audio paths won’t work… 20001 versus 30001/30051.Booo.  Maybe I'll poke at WB4FAY and see if he's interested in
updating.  I'd hate to mix cron jobs and monlink but ...  probably
do-able.


A2 - The command sequence for installing g2_link for 3.2 is in the Files section here.Thank you.  I've looked at this at least three times already but I'm
actually more determined this time.  I don't like the fact that it's
in /root .. I looked at changing all instances of /root in the
not-script script to /dstar/g2_link (even if /dstar itself isn't
strictly canon).  I finally wgot the tarball and see that I would need
to update things like crontabs, etc, as well ... so likely not going
to do that.

May I suggest that if development on this continues (and I hope it
does!) that a future version installs somewhere less unique?  /dstar
or maybe /opt/g2_link?

Anyway, here I go.

Peter


-- 
Peter Laws | VE[23]UWY / N5UWY | plaws0 gmail com | Travel by Train!