|
|
Post by ke0lmx on Jul 19, 2017 5:19:41 GMT -8
Hi All, Other than the host files maintained here, what are the other host file sources that reflector admins should be aware of to submit their URL information to? So far I have: X Reflector Forum - aka xrefl.net directory ar-dns.net - sources from VK4TUX; vk4tux.duckdns.org/OD/DExtra_Hosts.txtSharkRF Openspot - I'm going to post on their forums to learn what they use as a souce. Others? Openstar, Freestar Of these, the only one I know the process for adds/updates is xrefl.net. I reached out to VK4TUX and haven't received a response as of yet. I will add updates here as I get them. Any and all other information is very welcome. Tim KE0LMX |
|
|
|
Post by K6KD on Jul 19, 2017 6:15:40 GMT -8
Tim, On this site: www.va3uv.com/freestar.htm is "contact us at dextra {at} va3uv.com" I don't know if anything is still active with DUTCH*Star, Fred, PA4YBR. There is a website here www.dutch-star.eu but I don't know if it is active. That's about all I know. John K6KD |
|
|
|
Post by ke0lmx on Jul 27, 2017 6:14:52 GMT -8
I have an answer from the SharkRF openSPOT developers: We use the following sources for the REF/XRF connector's server list: dschost2.w6kd.com/DPlus_Hosts.txtxlxapi.rlx.lu/api.php?do=GetReflectorHostnameI checked out the second source, and the file contains the following information, along with the list of hosts: If you find a mismatched entry please sent a mail to: dvc@rlx.lu So, I will send an email to that address and see what happens. Tim KE0LMX |
|
|
|
Post by ke0lmx on Jul 27, 2017 11:23:32 GMT -8
This is rather interesting. The hosts file from xlxapi.rlx.lu/api.php?do=GetReflectorHostname is meant to contain only XLX reflectors. If the openSPOT developers are only using the two listed sources for their device, that leaves the XRF reflectors that are not XLX reflectors out in the cold. I'm going to follow up with the openSPOT developers to see if they are aware of this gap.
Tim KE0LMX
|
|
|
|
Post by K6KD on Jul 27, 2017 11:48:22 GMT -8
This is rather interesting. The hosts file from xlxapi.rlx.lu/api.php?do=GetReflectorHostname is meant to contain only XLX reflectors. If the openSPOT developers are only using the two listed sources for their device, that leaves the XRF reflectors that are not XLX reflectors out in the cold. I'm going to follow up with the openSPOT developers to see if they are aware of this gap. Tim KE0LMX I don't use openSPOT for D-STAR so I can't be sure, but my understanding is they are aware of XRF (non-XLX reflectors) and their script takes that into account. Probably good to advise them of any new XRFs in this category so they can include. John K6KD |
|
|
|
Post by ke0lmx on Jul 28, 2017 11:13:53 GMT -8
They do have a source for XRF: For XRF, we use this source: ar-dns.net/dextraThis of course leads me back to VK4TUX, who doesn't seem to be responding to emails. Tim KE0LMX |
|
dc3ax
New Member
There are three logic states, high, low and some how. The higher the frequency, the more some how...
Posts: 1 
|
Post by dc3ax on Sept 26, 2017 11:21:40 GMT -8
Hi!
I'd like to extend that initial question a bit, cause I'd like to automate things a bit. As anyone could run XRF reflectors, it is hard to track XRF numbers and matching IPs. So building a device, that automatically updates reflectors is hard to build cause of two reasons:
1) You don't want to add another system where you have to register your reflector too
2) You won't like to put all that traffic on a machine that runs on someones else pocket.
So how to keep track of all reflectors and let hundreds of devices read and decode a xrf-IP list one or two times a day? And if this feature is added to the DV4Mini, there will be several 1000 devices doing that.
Ulrich DC3AX
|
|
