REF/XRF/DCS Listing - Source of Truth?

Help with D-Star related issues
VK4TUX
Posts: 57
Joined: Tue Dec 25, 2018 12:50 am

Re: REF/XRF/DCS Listing - Source of Truth?

Post by VK4TUX » Sat Mar 16, 2019 10:48 pm

k2dls wrote:
Fri Mar 15, 2019 8:56 pm
So I'm running 4.0 RC3...

I set xlxEnabled to 1 in ircddbgateway's config. I restarted the ircddbgateway service.

How can I connect to XLX020A, for example? It is listed in /usr/local/etc/XLXHosts.txt. I tried via text entry from the dropdown on the admin console, but it has no effect. Nor does XLX020AL in the URCALL field on the radio.
For the initial load set make the system rw with rpi-rw , then
sudo service ircddbgateway restart (systemd understands service commands)

What happens is the xlx host file entries take priority overwriting the DCS REF and XRF hostfiles ;'

M: 2019-03-16 21:47:43: Downloading XLX reflector list from http://xlxapi.rlx.lu/api.php?do=GetReflectorHostname
M: 2019-03-16 21:47:43: Starting the APRS Writer thread
M: 2019-03-16 21:47:43: Starting the D-RATS Server thread for VK4TUX
M: 2019-03-16 21:47:43: Starting the D-RATS Server thread for VK4TUX
M: 2019-03-16 21:47:43: Starting the D-RATS Server thread for VK4TUX
M: 2019-03-16 21:47:44: Received login banner : # aprsc 2.1.4-g408ed49

M: 2019-03-16 21:47:44: Response from APRS server: # logresp VK4TUX-G verified, server T2QLD

M: 2019-03-16 21:47:44: Connected to the APRS server
M: 2019-03-16 21:47:45: Truncating /home/odroid/Links.log
M: 2019-03-16 21:47:45: Truncating /home/odroid/STARnet.log
M: 2019-03-16 21:47:45: Allocated UDP ports 30001-30007 to DExtra
M: 2019-03-16 21:47:45: Allocated UDP ports 20001-20007 to D-Plus
M: 2019-03-16 21:47:45: Allocated UDP ports 30051-30057 to DCS
M: 2019-03-16 21:47:45: Starting the ircDDB Gateway thread
M: 2019-03-16 21:50:26: Loaded 2196 of 2196 D-Plus reflectors
M: 2019-03-16 21:53:32: Loaded 2196 of 2196 D-Plus reflectors
E: 2019-03-16 21:53:57: Cannot find address for host xrf052.dip.jp
E: 2019-03-16 21:55:05: Cannot find address for host xrf412.dip.jp
E: 2019-03-16 21:55:30: Cannot find address for host xrf608.dip.jp
M: 2019-03-16 21:56:00: Loaded 435 of 438 DExtra reflectors from
E: 2019-03-16 21:56:31: Cannot find address for host xrf052.dip.jp
E: 2019-03-16 21:57:51: Cannot find address for host hamradio.dip.jp
M: 2019-03-16 21:58:38: Loaded 436 of 438 DExtra reflectors
M: 2019-03-16 21:58:38: Locking DCS000 to 23.111.174.198
M: 2019-03-16 21:58:40: Locking DCS005 to 87.117.229.174
M: 2019-03-16 21:58:40: Locking DCS006 to 146.168.196.187
M: 2019-03-16 21:58:41: Locking DCS010 to 85.197.129.86
M: 2019-03-16 21:58:42: Locking DCS012 to 194.38.140.205
M: 2019-03-16 21:58:42: Locking DCS014 to 110.232.113.108
E: 2019-03-16 21:58:54: Cannot find address for host xlx028.org
M: 2019-03-16 21:58:57: Loaded 372 of 373 DCS reflectors
M: 2019-03-16 21:58:57: Locking DCS000 to 23.111.174.198
M: 2019-03-16 21:58:59: Locking DCS005 to 87.117.229.174
M: 2019-03-16 21:58:59: Locking DCS006 to 146.168.196.187
M: 2019-03-16 21:59:01: Locking DCS010 to 85.197.129.86
M: 2019-03-16 21:59:01: Locking DCS012 to 194.38.140.205
M: 2019-03-16 21:59:01: Locking DCS014 to 110.232.113.108
E: 2019-03-16 21:59:11: Cannot find address for host xlx028.org
M: 2019-03-16 21:59:13: Loaded 372 of 373 DCS reflectors
M: 2019-03-16 21:59:13: Reading /tmp/XLX_Hosts_2M2x4d
M: 2019-03-16 21:59:13: Loaded 1080 of 1080 XLX reflectors from /tmp/XLX_Hosts_2M2x4d

If pistar adds a rw capability to the host file folder at ircddbgateway startup duration or downloads the file in a separate process prior written to the /tmp, or otherwise redefine path to suit pstar in source by the pistar author, then you should be ok.

DCS020ML as you tried before will now link your reflector.

M1DNS
Posts: 203
Joined: Thu Apr 05, 2018 5:30 am

Re: REF/XRF/DCS Listing - Source of Truth?

Post by M1DNS » Sat Mar 16, 2019 11:45 pm

Ur getting a little cloudy there buddy I mention on one occasion he was away from home, when someone was trying to gain his attention ... I can't recall mentioning he was sick. Just that he wasn't around currently... but that comment was made abt. 6-8 months ago. But that presumption was made a couple weeks after he was back at home. and anyways is that such a great fuck up that it merits a mention as a get back at ya?

So, as to getting things wrong.. I'd look back over ur incorrect references but, AHH yes.. that's right... each time ur shown to be wrong you return to delete ur posts One of the things in being a group mod is you get to view the log files for the actions of each user. So when someone returns to edit or remove their comments those actions are logged... And if a moderator chooses he could reverse that action, doing so in the name of clarity. No one wants to read a disconjoined thread, right?

Now, U have yourself a great day, over there.


Andrew M1DNS, (Mod)





Andrew M1DNS.
Pi-star Admin Team.

VK4TUX
Posts: 57
Joined: Tue Dec 25, 2018 12:50 am

Re: REF/XRF/DCS Listing - Source of Truth?

Post by VK4TUX » Sun Mar 17, 2019 2:50 am

I notice you didn't mention your YSF2P25 transcoding rant on FB, where you would not admit you were wrong as usual.

F*** comments have no place here, you should clean up your grammar.

Anyhow F4FXL Geoff was the guy that added the XLX features to ircDDBgateway, based on DCS protocol.
I will have a chat to Geoff about retaining the original host files and keeping the xlx dstar hostfile import as XLX entries
for XLX link capability, without effecting the the DCS|XRF|REF functionality.

VK4TUX
Posts: 57
Joined: Tue Dec 25, 2018 12:50 am

Re: REF/XRF/DCS Listing - Source of Truth?

Post by VK4TUX » Sun Mar 17, 2019 6:27 am

Dan I had a chat to Geoff, and he indicated he will request merge into latest ircddbgateway
for the XLX linking feature, so hopefully it shows up in pistar in the near future ;

https://github.com/F4FXL/OpenDV/tree/NewXLX

M1DNS
Posts: 203
Joined: Thu Apr 05, 2018 5:30 am

Re: REF/XRF/DCS Listing - Source of Truth?

Post by M1DNS » Sun Mar 17, 2019 8:48 am

VK4TUX wrote:I notice you didn't mention your YSF2P25 transcoding rant on FB, where you would not admit you were wrong as usual.

F*** comments have no place here, you should clean up your grammar.

Anyhow F4FXL Geoff was the guy that added the XLX features to ircDDBgateway, based on DCS protocol.
I will have a chat to Geoff about retaining the original host files and keeping the xlx dstar hostfile import as XLX entries
for XLX link capability, without effecting the the DCS|XRF|REF functionality.
I still stand by that comment

YSF (DN) to p25 ambe to imbe would need transcoding.

But agn that was a very long time ago where transcoding was in its infancy and I don't mind being wrong. I don't always fully understand some of the projects that surround MMDVM, My posts are still there for others to read if they want, as i haven't chosen to delete them. ImageImage and if they do, they'll see it wasn't a rant but more someone in disagreement decided that the topic needed to be made into a arguement. But as said that was way back.. water under the bridge etc.







Andrew M1DNS, (Mod)


Andrew M1DNS.
Pi-star Admin Team.

M1DNS
Posts: 203
Joined: Thu Apr 05, 2018 5:30 am

Re: REF/XRF/DCS Listing - Source of Truth?

Post by M1DNS » Sun Mar 17, 2019 11:48 am


VK4TUX wrote:
Anyhow F4FXL Geoff was the guy that added the XLX features to ircDDBgateway, based on DCS protocol.
I will have a chat to Geoff about retaining the original host files and keeping the xlx dstar hostfile import as XLX entries
for XLX link capability, without effecting the the DCS|XRF|REF functionality.

No real need as pistar already pulls info from XLX.
And distributes it the way Andy (the creator of pistar) considers applicable.
But if it gives you a sense of importance, carry on. Image but please don't do this in the name of pistar unless Andy is ok with that.

But regardless, Any changes that are made, will eventually find themselves added by him anyway.

----
But as mentioned numerous times all over the PS groups...
Advising users edit, change or mod the file system can have repurcusions elsewhere as Dan saw above. But if followed the way as intended it'll work in its native form.

The understanding we (at pistar) have is...
Hey, It's ur install to do with as you choose.
But if it breaks, you'll need to know how to fix it.

Andrew M1DNS, (Mod)



Andrew M1DNS.
Pi-star Admin Team.

k2dls
Posts: 31
Joined: Mon Aug 20, 2018 5:24 pm

Re: REF/XRF/DCS Listing - Source of Truth?

Post by k2dls » Sun Mar 17, 2019 1:12 pm

VK4TUX wrote:
Sun Mar 17, 2019 6:27 am
Dan I had a chat to Geoff, and he indicated he will request merge into latest ircddbgateway
for the XLX linking feature, so hopefully it shows up in pistar in the near future ;

https://github.com/F4FXL/OpenDV/tree/NewXLX
Should that happen, this would be a useful feature. It could spell the end of pure XRF
reflectors as the auto registration method is better than waiting to get added to various
lists.

I do have to compliment NO9S who maintains the lists used by the OpenSpot. I emailed
him on Saturday to have XRF020 added to their list and it was done within 2 hours. But
all the different lists with no specific wait times is not helping the hobby. We need to do
away with these lists and go to a DNS based system with auto registration, similar to
dynamic DNS.

M1DNS
Posts: 203
Joined: Thu Apr 05, 2018 5:30 am

Re: REF/XRF/DCS Listing - Source of Truth?

Post by M1DNS » Sun Mar 17, 2019 1:17 pm

Dan.

Here's how I see it working for you currently.

If you want to link to ur xreflector. radio should read.
XRF020AL.

If you want to link to ur XLX. DCS020AL

DExtra host file will have an address for original low no dextra reflectors.
No.s that don't have an XLX alternative. Or aren't XLX replacements.

DCS hosts will have entries for XLX as that's the preferred protocol.

Any XLX that's known to be either a replacement for an original xrfd or be a new XLX that doesn't conflict with an actual xrfd 'low no' reflector will have entries in DExtra, DPlus and DCS hosts to support links on all protocols for XLX.

I do agree having the ability to filter all as posted in amongst the qrm might be an easier ( maybe even better ) solution, but it isn't native here. yet.

given ur A modules on both reflectors are bridged this should give you an ability for ur users to link with either. (Personal preference, I'll always go for the XLX connection, but that's just my preference. )

We now need to ensure the correct IP addresses is in the dextra host file.

Andrew M1DNS, (Mod)

Andrew M1DNS.
Pi-star Admin Team.

M1DNS
Posts: 203
Joined: Thu Apr 05, 2018 5:30 am

Re: REF/XRF/DCS Listing - Source of Truth?

Post by M1DNS » Sun Mar 17, 2019 1:21 pm


k2dls wrote: We need to do
away with these lists and go to a DNS based system with auto registration, similar to
dynamic DNS.

Agreed to a point, unfortunately it's been tried before and the hosts of said lists often make demands of those that choose to use them. Bulldozing their way into groups and then demand to have a say in what gets done within that project, and get pissy when their ideas are debuted.

And can become a fine line in what an open system is... It's not always someone creates something for betterment, but to dictate and show how clever they are... For the glory of it.. such people often reside in fragile circles, I've seen 'em come and go over the yrs. And some are still at it Image

It needs to be done, similar to a wiki feed... where anyone (within reason) is free to update the list or make any needed changes, and should never be down to one individual or one specific admin group.

Andrew M1DNS, (Mod)





Andrew M1DNS.
Pi-star Admin Team.

k2dls
Posts: 31
Joined: Mon Aug 20, 2018 5:24 pm

Re: REF/XRF/DCS Listing - Source of Truth?

Post by k2dls » Sun Mar 17, 2019 2:23 pm

That is why I like the autoregistration idea ...you get there first, it is yours. It takes away any opportunity
for favoritism, cliquishness, and other human weaknesses. This is where XLX gets it right.

We should also not reuse the same number for different resource across DCS, REF, XRF, XLX or whatever
may come along next. So, maybe we switch to a 7 digit number for the reflector resource (sound
familiar?) and have the back end figure out what the number represents and how to best get there.

So maybe to get to your favorite reflector you put 1234567L in your radio, the software queries the DNS,
it comes back with TXT records for the types of connections supported, your Pi-Star is configured with
an order of precedence to try them, such as DCS first, then XRF, then REF...and it just works!

This is a substantial change in the way of doing things, but would result in a more open and transparent
result.

BTW, may I please have an estimate on when my requested change to DExtra_Hosts.txt might be
addressed? ;)

73

Post Reply